linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: PCI/USB Vendor and model from database
Date: Tue, 28 Dec 2010 18:45:36 +0000	[thread overview]
Message-ID: <20101228184536.GA11878@kroah.com> (raw)
In-Reply-To: <AANLkTi=1GzSurOXcFwBJUXfXBch24QB3cRh+0qo1a1Fp@mail.gmail.com>

On Tue, Dec 28, 2010 at 02:14:38PM +0100, José Félix Ontañón wrote:
> Hi, everybody!
> 
> 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?
> 
> I mean, by adding this simple rules:
> 
> SUBSYSTEMS="usb", IMPORT{program}="usb-db %p"
> SUBSYSTEMS="pci", IMPORT{program}="pci-db %p"
> 
> 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

  reply	other threads:[~2010-12-28 18:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-28 13:14 PCI/USB Vendor and model from database José Félix Ontañón
2010-12-28 18:45 ` Greg KH [this message]
2010-12-28 23:58 ` Lennart Poettering
2010-12-29  0:18 ` Scott James Remnant
2010-12-29 16:08 ` José Félix Ontañón
2010-12-29 16:16 ` Greg KH
2010-12-29 16:34 ` Kay Sievers
2010-12-29 23:09 ` José Félix Ontañón
2010-12-30  0:08 ` José Félix Ontañón

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20101228184536.GA11878@kroah.com \
    --to=greg@kroah.com \
    --cc=linux-hotplug@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).