Date: Fri, 09 Jan 2004 14:23:58 -0700 From: Scott Long <scottl@freebsd.org> To: =?ISO-8859-1?Q?Dag-Erling_Sm=F8rgrav?= <des@des.no> Cc: hackers@freebsd.org Subject: Re: Discussion on the future of floppies in 5.x and 6.x Message-ID: <3FFF1BEE.9090400@freebsd.org> In-Reply-To: <xzpoetckf1k.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> <20040109210153.GP25474@server.vk2pj.dyndns.org> <xzpoetckf1k.fsf@dwp.des.no>
next in thread | previous in thread | raw e-mail | index | archive | help
Dag-Erling Smørgrav wrote:
> Peter Jeremy <peterjeremy@optushome.com.au> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3FFF1BEE.9090400>