linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tom Gundersen <teg@jklm.no>
To: linux-hotplug@vger.kernel.org
Subject: Re: systemd-183
Date: Thu, 31 May 2012 21:45:32 +0000	[thread overview]
Message-ID: <CAG-2HqUORSNVzSbvSecUL+924HOtHXs3CwYKLU5H4Spn+4w75A@mail.gmail.com> (raw)
In-Reply-To: <4FBE8DC4.1070202@gmail.com>

On Thu, May 31, 2012 at 9:57 PM, Kay Sievers <kay@vrfy.org> wrote:
> It's probably not worth to put too much effort into it. We are about
> to make a more generic query-able hardware database with pre-compiled
> efficient lookup interfaces. It will provide additional key/value
> pairs that further classify devices we care about. All this will go
> far beyond the human readable strings the ids files provide.
>
> Just saying, pretty soon, the ids files will no longer directly read
> by udev. We will see how all that will look like when we get there.

That makes a lot of sense. Hopefully it will be similar to the hwids
package from a packaging point of view (i.e. a standalone db that can
be shipped independently from any libs/tools).

Cheers,

Tom

      parent reply	other threads:[~2012-05-31 21:45 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-24 19:36 systemd-183 Bruce Dubbs
2012-05-27  0:54 ` systemd-183 William Hubbs
2012-05-27  3:19 ` systemd-183 Karl O. Pinc
2012-05-27  3:38 ` systemd-183 Bruce Dubbs
2012-05-27  4:06 ` systemd-183 Karl O. Pinc
2012-05-27 11:34 ` systemd-183 Kay Sievers
2012-05-27 12:17 ` systemd-183 Karl O. Pinc
2012-05-31 17:35 ` systemd-183 William Hubbs
2012-05-31 19:33 ` systemd-183 Bruce Dubbs
2012-05-31 19:46 ` systemd-183 Tom Gundersen
2012-05-31 19:57 ` systemd-183 Kay Sievers
2012-05-31 20:15 ` systemd-183 Kay Sievers
2012-05-31 20:30 ` systemd-183 Bruce Dubbs
2012-05-31 20:52 ` systemd-183 Kay Sievers
2012-05-31 21:45 ` Tom Gundersen [this message]

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=CAG-2HqUORSNVzSbvSecUL+924HOtHXs3CwYKLU5H4Spn+4w75A@mail.gmail.com \
    --to=teg@jklm.no \
    --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 read-only IMAP folder(s) and NNTP newsgroup(s).