Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/systemd: Optionally disable hwdb
Date: Mon, 13 Jun 2016 22:00:03 +0200	[thread overview]
Message-ID: <20160613200003.GA3786@free.fr> (raw)
In-Reply-To: <b8499799-7f77-e90f-65aa-29cae92d53d5@grinn-global.com>

Marcin, All,

On 2016-06-13 11:20 +0200, Marcin Niestroj spake thusly:
> On 08.06.2016 22:19, Yann E. MORIN wrote:
> >On 2016-04-15 12:46 +0200, Marcin Niestroj spake thusly:
> >>By default hwdb files are installed in /usr/lib/udev/hwdb.d
> >>Currently they take about ~5MB. After first boot, systemd-hwdb tool
> >>parses them and creates a binary in /etc/udev/hwdb.bin, which takes
> >>another ~6.5MB.
> >>
> >>In case of initramfs images, hwdb parsing is done every boot. This adds
> >>about 2-3 seconds to boot time in case of rootfs on SDHC class 10
> >>card (benchmarked with am335x board). NAND boot takes even longer.
[--SNIP--]
> >Yet, I'd like to know what would be the impact of not having hwdb
> >support at runtime. Care to shed some light, please?
> 
> HWDB is mainly a database of device classes and vendors (for PCI, SDIO,
> USB). This is helpfull during development, because tools like lsusb are
> able to show vendor and usb class for each device. However we don't
> need this in production most of the time.
> Additionally there are some files for input devices, like mouse,
> keyboard and pointstick. In keyboard files for example there are
> defined some special keys, like play/pause, volumeup etc.

OK, thanks for the info, definitively usefull.

So, it seems this is not systematically needed on production systems,
but mostly a "debugging" aid in most cases. And for those that need it,
it's still an option.

However, people that do need it and that are working either on a
read-only filesystem or a transient one (initramfs) would need a mean
to avoid building this hwdb at every boot... That would be so cool...

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2016-06-13 20:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-15 10:46 [Buildroot] [PATCH] package/systemd: Optionally disable hwdb Marcin Niestroj
2016-04-15 20:53 ` Peter Seiderer
2016-04-18  8:25   ` Marcin Niestroj
2016-06-07 14:37 ` Marcin Niestroj
2016-06-08 20:19 ` Yann E. MORIN
2016-06-13  9:20   ` Marcin Niestroj
2016-06-13 20:00     ` Yann E. MORIN [this message]
2016-06-15 21:19 ` Thomas Petazzoni

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=20160613200003.GA3786@free.fr \
    --to=yann.morin.1998@free.fr \
    --cc=buildroot@busybox.net \
    /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