Date: Mon, 3 Apr 2000 19:22:46 +0400 From: Nikolai Saoukh <nms@otdel-1.org> To: Warner Losh <imp@village.org> Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Reserving Resources Message-ID: <20000403192246.C55382@Draculina.otdel-1.org> In-Reply-To: <200004031511.JAA61348@harmony.village.org>; from imp@village.org on Mon, Apr 03, 2000 at 09:11:10AM -0600 References: <20000403190741.A55382@Draculina.otdel-1.org> <20000403104318.A53697@Draculina.otdel-1.org> <Pine.BSF.4.20.0004022113120.604-100000@localhost> <200004022029.OAA54341@harmony.village.org> <20000403104318.A53697@Draculina.otdel-1.org> <200004031430.IAA60992@harmony.village.org> <20000403190741.A55382@Draculina.otdel-1.org> <200004031511.JAA61348@harmony.village.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Apr 03, 2000 at 09:11:10AM -0600, Warner Losh wrote: > You can't always disable PNP devices. More accurately, the devices > reported by PNPBIOS are defined to be hard wired and always active. > You cannot turn them off or relocate their resources. They likely > should be probed first rather than last like they are now, with > changes made to those drivers taht don't yet support PNP. However, > since the isa bus isn't guaranteed to exist until later in the boot > process, this may have some problems. Well, create a automagic device 'known' and attach all known devices from PNPBIOS to it. Now _all_ pnp devices got their resources (even if there is no driver for it) and attached to 'unknown' driver. Any kldloaded driver later does not see the device. Simple remove of 'unknown' driver from src/sys/isa/isa_common.c makes device free and visible, but resources allocated to it at boot time lost forever. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000403192246.C55382>