From owner-freebsd-current Wed Dec 8 19:25:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from rina.r.dl.itc.u-tokyo.ac.jp (rina.r.dl.itc.u-tokyo.ac.jp [133.11.199.247]) by hub.freebsd.org (Postfix) with ESMTP id C7336152FA; Wed, 8 Dec 1999 19:25:42 -0800 (PST) (envelope-from tanimura@r.dl.itc.u-tokyo.ac.jp) Received: from rina.r.dl.itc.u-tokyo.ac.jp (localhost [127.0.0.1]) by rina.r.dl.itc.u-tokyo.ac.jp (8.9.3+3.2W/3.7W-r-0.1-19990829) with ESMTP id MAA09252; Thu, 9 Dec 1999 12:25:34 +0900 (JST) Date: Thu, 09 Dec 1999 12:25:33 +0900 Message-ID: <14415.8493.971538.78435L@rina.r.dl.itc.u-tokyo.ac.jp> From: Seigo Tanimura To: caa@columbus.rr.com Cc: msmith@FreeBSD.ORG, tanimura@r.dl.itc.u-tokyo.ac.jp, schuerge@wjpserver.CS.Uni-SB.DE, fn@radio-do.de, freebsd-current@FreeBSD.ORG Subject: Re: AWE64 problems In-Reply-To: In your message of "Wed, 8 Dec 1999 08:54:15 -0500" <19991208085415.A534@midgard.dhs.org> References: <19991208000746.A1622@midgard.dhs.org> <199912080513.VAA07525@mass.cdrom.com> <19991208085415.A534@midgard.dhs.org> Cc: Seigo Tanimura User-Agent: Wanderlust/1.0.3 (Notorious) SEMI/1.13.4 (Terai) FLIM/1.12.7 (=?ISO-8859-4?Q?Y=FEzaki?=) MULE XEmacs/21.1 (patch 8) (Bryce Canyon) (i386--freebsd) Organization: Digital Library Research Division, Information Techinology Centre, The University of Tokyo MIME-Version: 1.0 (generated by SEMI 1.13.4 - "Terai") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [snipped some part] >> > > On Tue, 7 Dec 1999 23:00:02 +0100 (MET), >> > > Thomas Schuerger said: >> > > >> > > >> --- sbc.c.orig Mon Dec 6 19:26:31 1999 >> > > >> +++ sbc.c Tue Dec 7 22:15:25 1999 >> > > >> @@ -110,7 +110,7 @@ >> > > >> if (error) >> > > >> return error; >> > > >> else >> > > >> - return -100; >> > > >> + return -1; >> > > >> } >> > > >> >> > > >> static int On Wed, 8 Dec 1999 08:54:15 -0500, "Charles Anderson" said: Charles> So then what is -1 and why does it work when -100 doesn't? (I tried it) sys/kern/subr_bus.c:device_probe_child() receives the value returned by DEVICE_PROBE(child dev). If the value is zero, no further probes occur. The device then gets attached in sys/kern/subr_bus.c: device_probe_and_attach(). If the returned value is less than zero, device_probe_child() continues probing other possible drivers. For ISA devices, the unknown driver implemented in sys/isa/isa_common.c is always probed if no other drivers probe the device successfully. The DEVICE_PROBE() for any ISA devices with the unknown driver returns -100, so it is, say, the likelyhood of the unknown driver to the device. To say the truth, a driver other than the unknown might get to probe the device in this case, depending on the order to enumerate the possible drivers in device_probe_child() using {first,next}_matching_driver(). -- Seigo Tanimura To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message