From owner-freebsd-hackers@FreeBSD.ORG  Fri Jan  9 13:06:57 2004
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
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 A83B516A4CE; Fri,  9 Jan 2004 13:06:57 -0800 (PST)
Received: from smtp.des.no (flood.des.no [217.116.83.31])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 4D04143D58; Fri,  9 Jan 2004 13:06:40 -0800 (PST)
	(envelope-from des@des.no)
Received: by smtp.des.no (Pony Express, from userid 666)
	id 104C55314; Fri,  9 Jan 2004 22:06:39 +0100 (CET)
Received: from dwp.des.no (des.no [80.203.228.37])
	by smtp.des.no (Pony Express) with ESMTP
	id D8B8D5308; Fri,  9 Jan 2004 22:06:31 +0100 (CET)
Received: by dwp.des.no (Postfix, from userid 2602)
	id 6EB3F33C9A; Fri,  9 Jan 2004 22:06:31 +0100 (CET)
To: Peter Jeremy <peterjeremy@optushome.com.au>
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>
From: des@des.no (Dag-Erling =?iso-8859-1?q?Sm=F8rgrav?=)
Date: Fri, 09 Jan 2004 22:06:31 +0100
In-Reply-To: <20040109210153.GP25474@server.vk2pj.dyndns.org> (Peter
 Jeremy's message of "Sat, 10 Jan 2004 08:01:54 +1100")
Message-ID: <xzpoetckf1k.fsf@dwp.des.no>
User-Agent: Gnus/5.090024 (Oort Gnus v0.24) Emacs/21.3 (berkeley-unix)
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	flood.des.no
X-Spam-Level: 
X-Spam-Status: No, hits=0.1 required=5.0 tests=RCVD_IN_SORBS autolearn=no 
	version=2.60
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
	<freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Jan 2004 21:06:57 -0000

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[] =3D {
        { 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
--=20
Dag-Erling Sm=F8rgrav - des@des.no