Date: Fri, 09 Jan 2004 22:06:31 +0100 From: des@des.no (Dag-Erling =?iso-8859-1?q?Sm=F8rgrav?=) To: Peter Jeremy <peterjeremy@optushome.com.au> Cc: scottl@freebsd.org Subject: Re: Discussion on the future of floppies in 5.x and 6.x Message-ID: <xzpoetckf1k.fsf@dwp.des.no> In-Reply-To: <20040109210153.GP25474@server.vk2pj.dyndns.org> (Peter Jeremy's message of "Sat, 10 Jan 2004 08:01:54 %2B1100") 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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
--
Dag-Erling Smørgrav - des@des.no
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?xzpoetckf1k.fsf>