Date: Sun, 28 May 2000 07:16:02 -0700 From: Peter Wemm <peter@netplex.com.au> To: Doug Rabson <dfr@nlsystems.com> Cc: Dennis <dennis@etinc.com>, John Hay <jhay@mikom.csir.co.za>, hackers@FreeBSD.ORG Subject: Re: 4.0 - Isa devices not being probed Message-ID: <20000528141602.E46F71CE2@overcee.netplex.com.au> In-Reply-To: Message from Doug Rabson <dfr@nlsystems.com> of "Sat, 27 May 2000 20:47:50 BST." <Pine.BSF.4.21.0005272046210.73457-100000@salmon.nlsystems.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Doug Rabson wrote: > On Sat, 27 May 2000, Dennis wrote: > > At 09:54 AM 5/27/00 +0200, John Hay wrote: > > >> In message <200005261723.NAA16495@etinc.com> Dennis writes: > > >> : My 4.0 system doesnt probe ISA devices on my system. > > >> : > > >> : Whats the trick? Is there a config requirement with old-style drivers? > > >> > > >> They probe great for me. what, specifically, isn't probing? > > > > > >He is probably talking about their own driver. In that case you have to > > >add it to /sys/i386/isa/isa_compat.* or bite the bullet and new-busify > > >it. [..] > > isa_compat.h? LOL...what college freshman thought of that? Is it really > > that difficult to have the prefix_probe() function called based on the > > config file? > > This is just a list of drivers using the legacy apis. Since no new drivers > will be using those apis, this file will gradualy disappear and certainly > no new drivers will be added to it. We originally did it that way to avoid having to do a massive driver API change at the cutover. Since all the important drivers are converted and there are not that many left I took some time and redid it to use a similar approach that we used on the PCI driver shims. Now the isa_compat.h table is gone, but a minor driver API change is required to support it. Cheers, -Peter 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?20000528141602.E46F71CE2>