From: Will Wagner <will_wagner@carallon.com>
To: buildroot@busybox.net
Subject: [Buildroot] Question about using mdev for /dev management
Date: Mon, 05 Dec 2011 18:45:29 +0000 [thread overview]
Message-ID: <4EDD1149.8060104@carallon.com> (raw)
Hi All,
I am using buildroot 2011.11 and looking at using mdev for /dev management.
This works but I have a couple of questions about it.
Firstly it replaces $(TARGET_DIR)/init with fs/cpio/init which attempts
to mount devtmpfs. My kernel doesn't support this (it's too old) and I'd
rather not get this trace in the boot (it worries other developers). I
assume that for mdev we could not replace init but instead make sure
that /dev/console (and possibly /dev/null?) exist?
The other small issue I have is that mdev fails to spot one of the
kernel devices (as the driver doesn't have a sysfs entry) so it needs
adding manually. I do that by adding an entry to BR2_ROOTFS_DEVICE_TABLE
which works fine, but doesn't seem ideal as I thought device entries
were meant to be set in BR2_ROOTFS_STATIC_DEVICE_TABLE, but that is not
offered unless static devices used. Is there a better way to do this or
should I just leave it as is?
Thanks
Will
--
------------------------------------------------------------------------
Will Wagner will_wagner at carallon.com
Development Manager Office Tel: +44 (0)20 7371 2032
Carallon Ltd, Studio G20, Shepherds Building, Rockley Rd, London W14 0DA
------------------------------------------------------------------------
next reply other threads:[~2011-12-05 18:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-05 18:45 Will Wagner [this message]
2011-12-13 8:39 ` [Buildroot] Question about using mdev for /dev management Arnout Vandecappelle
2011-12-13 13:39 ` Thomas Petazzoni
2011-12-13 14:58 ` Michael S. Zick
2011-12-13 15:24 ` Michael S. Zick
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=4EDD1149.8060104@carallon.com \
--to=will_wagner@carallon.com \
--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 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.