From owner-freebsd-hackers@FreeBSD.ORG Fri Jan 9 13:02:44 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 98B3016A4CE; Fri, 9 Jan 2004 13:02:44 -0800 (PST) Received: from server.vk2pj.dyndns.org (c211-30-75-229.belrs2.nsw.optusnet.com.au [211.30.75.229]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3F8F143D6E; Fri, 9 Jan 2004 13:02:18 -0800 (PST) (envelope-from peterjeremy@optushome.com.au) Received: from server.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1])i09L1s7B058309; Sat, 10 Jan 2004 08:01:54 +1100 (EST) (envelope-from peter@server.vk2pj.dyndns.org) Received: (from peter@localhost) by server.vk2pj.dyndns.org (8.12.10/8.12.10/Submit) id i09L1sVZ058308; Sat, 10 Jan 2004 08:01:54 +1100 (EST) (envelope-from peter) Date: Sat, 10 Jan 2004 08:01:54 +1100 From: Peter Jeremy To: Dag-Erling =?iso-8859-1?Q?Sm=F8rgrav?= Message-ID: <20040109210153.GP25474@server.vk2pj.dyndns.org> References: <200401091400.40550.doconnor@gsoft.com.au> <3FFE5211.5040606@freebsd.org> <20040109.075929.90380697.imp@bsdimp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.4.1i cc: hackers@freebsd.org cc: scottl@freebsd.org Subject: Re: Discussion on the future of floppies in 5.x and 6.x X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Jan 2004 21:02:44 -0000 On Fri, Jan 09, 2004 at 04:38:11PM +0100, Dag-Erling Smørgrav wrote: >"M. Warner Losh" 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