From: "Stefan Fröberg" <stefan.froberg@petroprogram.com>
To: buildroot@busybox.net
Subject: [Buildroot] editing device_table_dev.txt
Date: Thu, 21 Feb 2013 12:32:27 +0200 [thread overview]
Message-ID: <5125F7BB.50403@petroprogram.com> (raw)
In-Reply-To: <20130221102315.GB12155@sapphire.tkos.co.il>
21.2.2013 12:23, Baruch Siach kirjoitti:
> Hi Stefan,
>
> On Thu, Feb 21, 2013 at 12:21:00PM +0200, Stefan Fr?berg wrote:
>> 21.2.2013 12:14, Stefan Fr?berg kirjoitti:
>>> 21.2.2013 1:37, John Stile kirjoitti:
>>>> I need a better way to auto-populate /dev, using buildroot-2011.11, with
>>>> 2.6.30 kernel, but it seems not matter what I do, /dev/ is not populated
>>>> automaticly.
>>>>
>>>> My config looks like this:
>>>>
>>>> BR2_ROOTFS_DEVICE_CREATION_STATIC=y
>>>> # BR2_ROOTFS_DEVICE_CREATION_DYNAMIC_DEVTMPFS is not set
>>>> # BR2_ROOTFS_DEVICE_CREATION_DYNAMIC_MDEV is not set
>>>> # BR2_ROOTFS_DEVICE_CREATION_DYNAMIC_UDEV is not set
>>>> BR2_ROOTFS_DEVICE_TABLE="target/generic/device_table.txt target/generic/device_table_dev.txt"
>>>> BR2_ROOTFS_STATIC_DEVICE_TABLE="target/generic/device_table_dev.txt"
>>>> # BR2_ROOTFS_SKELETON_DEFAULT is not set
>>>> BR2_ROOTFS_SKELETON_CUSTOM=y
>>>> BR2_ROOTFS_SKELETON_CUSTOM_PATH="fs/skeletonMiLON"
>>>> BR2_ROOTFS_POST_BUILD_SCRIPT="$(TOPDIR)/board/atmel/at91sam9g20ek/post-build/post-build-scripts.bash"
>>>>
>>>> To use hwclock I had to create dev/rtc0.
>>>> Although my kernel argument contains mtdparts, the mtd* and mtdblock*
>>>> devices are not created.
>>>> There are others too.
>>>>
>>>> What should my config look like in order to auto-populate /dev?
>>>>
>>> Well, if you don't want to manually create your device nodes then there
>>> are several ways to autopopulate /dev
>>>
>>> Maybe the simplest would be just let the kernel handle it by mounting
>>> /dev with tmpfs
>>> So selecting BR2_ROOTFS_DEVICE_CREATION_DYNAMIC_DEVTMPFS=y is the
>>> correct option.
>>>
>>> Also kernel .config file should also have CONFIG_DEVTMPFS and DEVTMPFS
>>> as 'y'.
>> Sorry, that should have been CONFIG_DEVTMPFS=y and CONFIG_DEVTMPFS_MOUNT=y
> Kernel version 2.6.30 is too old for that.
>
> baruch
>
It is ?
Damn, then the only options are mdev and udev.
Stefan
next prev parent reply other threads:[~2013-02-21 10:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-20 23:37 [Buildroot] editing device_table_dev.txt John Stile
2013-02-21 10:14 ` Stefan Fröberg
2013-02-21 10:21 ` Stefan Fröberg
2013-02-21 10:23 ` Baruch Siach
2013-02-21 10:32 ` Stefan Fröberg [this message]
2013-02-21 22:57 ` Arnout Vandecappelle
2013-02-21 23:07 ` Stefan Fröberg
2013-02-21 23:24 ` Arnout Vandecappelle
2013-02-21 23:32 ` Stefan Fröberg
2013-02-23 9:30 ` Arnout Vandecappelle
2013-02-23 11:18 ` Stefan Fröberg
2013-02-24 17:26 ` Thomas Petazzoni
2013-02-24 18:11 ` Peter Korsgaard
2013-02-24 17:24 ` Thomas Petazzoni
2013-02-21 23:14 ` Arnout Vandecappelle
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=5125F7BB.50403@petroprogram.com \
--to=stefan.froberg@petroprogram.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox