Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] editing device_table_dev.txt
Date: Sun, 24 Feb 2013 18:24:16 +0100	[thread overview]
Message-ID: <20130224182416.64b51c7b@skate> (raw)
In-Reply-To: <5125F7BB.50403@petroprogram.com>

Dear Stefan Fr?berg,

On Thu, 21 Feb 2013 12:32:27 +0200, Stefan Fr?berg wrote:

> >>> 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.

No, because our mdev/udev handling makes the assumption that devtmpfs
support is enabled in the kernel.

Contrary to what Arnout says, I don't think devtmpfs support is
*mandatory* to get mdev to work. But in Buildroot, we've decided to
support only mdev on top of devtmpfs.

From linux/linux.mk:

        $(if $(BR2_ROOTFS_DEVICE_CREATION_STATIC),,
                $(call KCONFIG_ENABLE_OPT,CONFIG_DEVTMPFS,$(@D)/.config)
                $(call KCONFIG_ENABLE_OPT,CONFIG_DEVTMPFS_MOUNT,$(@D)/.config))

So whenever we're not using the "static" method, we enable DEVTMPFS +
DEVTMPFS_MOUNT.

So if you're using a kernel < 2.6.32 (I think that's the kernel release
in which devtmpfs was introduced), then your only choice is to use the
static method. Obviously, another better solution is to upgrade the
kernel version you're using. The .config posted by John Stile
originally mentions a board/atmel/at91sam9g20ek/ directory, which seems
to indicate John is using the AT91SAM9G20 SoC. This SoC is perfectly
well supported by mainline kernel versions, so there should normally be
no reason to stick with the old 2.6.30.

Best regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  parent reply	other threads:[~2013-02-24 17:24 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
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 [this message]
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=20130224182416.64b51c7b@skate \
    --to=thomas.petazzoni@free-electrons.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