From owner-freebsd-hackers Mon Apr 3 8:30:32 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 973B537B6DB for ; Mon, 3 Apr 2000 08:30:26 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id JAA88296; Mon, 3 Apr 2000 09:30:23 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id JAA61538; Mon, 3 Apr 2000 09:29:45 -0600 (MDT) Message-Id: <200004031529.JAA61538@harmony.village.org> To: Nikolai Saoukh Subject: Re: Reserving Resources Cc: freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Mon, 03 Apr 2000 19:22:46 +0400." <20000403192246.C55382@Draculina.otdel-1.org> References: <20000403192246.C55382@Draculina.otdel-1.org> <20000403190741.A55382@Draculina.otdel-1.org> <20000403104318.A53697@Draculina.otdel-1.org> <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> Date: Mon, 03 Apr 2000 09:29:45 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000403192246.C55382@Draculina.otdel-1.org> Nikolai Saoukh writes: : 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. That's why the mechanism needs to be known to the bus, so that it can release the approrpiate resources. I think that others have commented that the BUS_PROBE_NOMATCH method for the bus might be the best one to deal with this sort of thing. If we can live with the reasonable (imhoo) restriction that the newly loaded device driver must support plug and play identifiers, then we can likely just reprobe the devices identifiers that weren't really attached at another point in the boot process. I think that Doug is working on something similar to this. The bottom line is that a loaded device must have a shot at those devices that were attached simply to reserve the resources. Your expectation that you should be able to get the resources is a reasonable one. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message