From owner-freebsd-hackers@FreeBSD.ORG Fri Jan 9 13:25: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 8480C16A4CE for ; Fri, 9 Jan 2004 13:25:44 -0800 (PST) Received: from smtp.mho.com (smtp.mho.net [64.58.4.6]) by mx1.FreeBSD.org (Postfix) with SMTP id 40B6F43D41 for ; Fri, 9 Jan 2004 13:25:42 -0800 (PST) (envelope-from scottl@freebsd.org) Received: (qmail 35089 invoked by uid 1002); 9 Jan 2004 21:25:39 -0000 Received: from unknown (HELO freebsd.org) (64.58.1.252) by smtp.mho.net with SMTP; 9 Jan 2004 21:25:39 -0000 Message-ID: <3FFF1BEE.9090400@freebsd.org> Date: Fri, 09 Jan 2004 14:23:58 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.5) Gecko/20031103 X-Accept-Language: en-us, en MIME-Version: 1.0 To: =?ISO-8859-1?Q?Dag-Erling_Sm=F8rgrav?= References: <200401091400.40550.doconnor@gsoft.com.au> <3FFE5211.5040606@freebsd.org> <20040109.075929.90380697.imp@bsdimp.com> <20040109210153.GP25474@server.vk2pj.dyndns.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit cc: hackers@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:25:44 -0000 Dag-Erling Smørgrav wrote: > Peter Jeremy writes: > >>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. > > > yes, we need something like > > struct pci_device_info { > uint32_t pciid; > char brand[64]; > char model[64]; > } my_supported_devices[] = { > { 0x12345678, "Acme", "Nutcracker 2000" } > }; > > which is placed in a separate ELF section so we can extract it from > the module. > > except it needs to be flexible enough to support other buses than PCI > (SBUS, USB...) > > DES Yeah, this is a good suggestion, the only problem being in making it flexible enough to not be a burden on the drivers. Many drivers keep one or more flag elements in their tables to flag hardware than needs special attention. I'm sure that there are also countless other pieces of state that drivers would want to associate with a table like this. Scott