Date: Sat, 10 Jan 2004 08:01:54 +1100 From: Peter Jeremy <peterjeremy@optushome.com.au> To: Dag-Erling =?iso-8859-1?Q?Sm=F8rgrav?= <des@des.no> Cc: scottl@freebsd.org Subject: Re: Discussion on the future of floppies in 5.x and 6.x Message-ID: <20040109210153.GP25474@server.vk2pj.dyndns.org> In-Reply-To: <xzpad4xxhcs.fsf@dwp.des.no> References: <200401091400.40550.doconnor@gsoft.com.au> <3FFE5211.5040606@freebsd.org> <xzp1xq91oei.fsf@dwp.des.no> <20040109.075929.90380697.imp@bsdimp.com> <xzpad4xxhcs.fsf@dwp.des.no>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Jan 09, 2004 at 04:38:11PM +0100, Dag-Erling Smørgrav wrote: >"M. Warner Losh" <imp@bsdimp.com> writes: >> des@des.no (Dag-Erling Smørgrav) writes: >> : 2) use pciconf -l (or direct access to /dev/pci) to retrieve the PCI >> : IDs of unclaimed devices, look them up in a list of supported PCI >> : devices, and load the appropriate module. >> There's some ongoing work to make this easier to do. There are some >> issues with doing this, but nothing that can't be overcome. Every PCI >> driver in the tree will likely need to change in some form to make >> this happen, however. > >Not necessarily; one could, as a temporary measure, create and >maintain the list of supported PCI IDs manually. These sort of 'temporary measures' have a nasty habit of becoming permanent - witness sysinstall itself. Having to keep two lists of PCI IDs in sync manually is a maintenance nightmare. The (conceptually) simplest approach would be for all drivers to advertise the PCI IDs that they can support (together with a priority) in a manner that would allow such a list to be generated automatically. This would be fairly trivial for the PCI drivers that already scan a table of PCI IDs, but would be a nuisance for the drivers that have the PCI IDs wired into the probe code. Peter
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040109210153.GP25474>