From: Gary Thomas <gary@mlbassoc.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: eudev hwdb?
Date: Wed, 27 Apr 2016 11:22:03 +0200 [thread overview]
Message-ID: <572084BB.5090307@mlbassoc.com> (raw)
In-Reply-To: <CAJTo0LbHvD417+AkLhM8153DhbpBAE9TTeGMbuEDr+BV0CJAbA@mail.gmail.com>
On 2016-04-27 10:59, Burton, Ross wrote:
>
> On 27 April 2016 at 09:48, Gary Thomas <gary@mlbassoc.com <mailto:gary@mlbassoc.com>> wrote:
>
> Is there any way to not have both the hwdb.bin (which I assume
> is a binary version of the hardware databases) and /etc/udev/hwdb.d?
> Perhaps there is some way to only use one?
>
> Or maybe there is a better choice, such as mdev? I'm not sure about
> this (no experience) but my system needs to handle plug&play devices
> which the current eudev does well. It's just a huge "price" to pay.
>
>
> You could not install hwdb at all, it's a recommends so you can BAD_RECOMMENDS it away. It's certainly possible to wipe
> away the source files for hwdb if you don't care about extending them at runtime but nobody has done that yet: a rootfs
> postproccess hook could delete it and confirm that everything works fine.
Can you explain a bit more? - BAD_RECOMMENDS doesn't seem to be documented.
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2016-04-27 9:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-27 8:48 eudev hwdb? Gary Thomas
2016-04-27 8:59 ` Burton, Ross
2016-04-27 9:22 ` Gary Thomas [this message]
2016-04-27 9:23 ` Burton, Ross
2016-04-27 9:52 ` Gary Thomas
2016-04-27 9:01 ` Yegor Yefremov
2016-04-27 9:43 ` Martin Jansa
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=572084BB.5090307@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=ross.burton@intel.com \
--cc=yocto@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.