From owner-freebsd-arch  Sat Sep  9 12:10: 8 2000
Delivered-To: freebsd-arch@freebsd.org
Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147])
	by hub.freebsd.org (Postfix) with ESMTP
	id 436D537B422; Sat,  9 Sep 2000 12:10:03 -0700 (PDT)
Received: from critter (localhost [127.0.0.1])
	by critter.freebsd.dk (8.11.0/8.9.3) with ESMTP id e89JA1N89356;
	Sat, 9 Sep 2000 21:10:02 +0200 (CEST)
	(envelope-from phk@critter.freebsd.dk)
To: arch@freebsd.org, smp@freebsd.org
Subject: Device probing...
From: Poul-Henning Kamp <phk@freebsd.org>
Date: Sat, 09 Sep 2000 21:10:01 +0200
Message-ID: <89354.968526601@critter>
Sender: owner-freebsd-arch@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


I would really like to se us move all the device probe/attach code
to run in "normal context", ie enable interrupts before we probe
everything.

The main argument for this is the drivers can then use the full
complement of kernel infrastructure and interrupts during probe
attach.

Drivers needs to be able to function in this environment anyway
if they support removeable devices (pccard, usb, etc).

Are there reasons to not do this I have overlooked ?

--
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD coreteam member | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-arch" in the body of the message