From mboxrd@z Thu Jan  1 00:00:00 1970
From: Greg KH <greg@kroah.com>
Date: Tue, 28 Dec 2010 18:45:36 +0000
Subject: Re: PCI/USB Vendor and model from database
Message-Id: <20101228184536.GA11878@kroah.com>
List-Id: <linux-hotplug.vger.kernel.org>
References: <AANLkTi=1GzSurOXcFwBJUXfXBch24QB3cRh+0qo1a1Fp@mail.gmail.com>
In-Reply-To: <AANLkTi=1GzSurOXcFwBJUXfXBch24QB3cRh+0qo1a1Fp@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
To: linux-hotplug@vger.kernel.org

On Tue, Dec 28, 2010 at 02:14:38PM +0100, Jos=E9 F=E9lix Onta=F1=F3n wrote:
> Hi, everybody!
>=20
> Maybe this is kinda silly question but, I wonder why isn't
> "ID_VENDOR_FROM_DATABASE / ID_MODEL_FROM_DATABASE"-like properties
> imported by default using the pretty /lib/udev/usb-db and
> /lib/udev/pci-db commands for every founded pci/usb device?
>=20
> I mean, by adding this simple rules:
>=20
> SUBSYSTEMS=3D"usb", IMPORT{program}=3D"usb-db %p"
> SUBSYSTEMS=3D"pci", IMPORT{program}=3D"pci-db %p"
>=20
> I think this properties are very useful for apps that discover
> hardware through udev, so they will not have to reinvent the wheel by
> finding vendor/product names by themselves. Don't you think?

That would slow down every device being found, for no real user at this
time, right?

How hard is it to use libpci for the userspace program to find this
information, if it really needs it?  That way, you also don't have to
have the database at early boot time, which keeps things simpler.

thanks,

greg k-h