From: javier.martinez@collabora.co.uk (Javier Martinez Canillas)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/1] ARM: OMAP2+: enable devtmpfs and devtmpfs automount
Date: Tue, 27 Nov 2012 10:20:37 +0100 [thread overview]
Message-ID: <50B485E5.1050401@collabora.co.uk> (raw)
In-Reply-To: <50B47B17.2040608@ti.com>
On 11/27/2012 09:34 AM, Sekhar Nori wrote:
> On 11/21/2012 6:56 PM, Javier Martinez Canillas wrote:
>> Since udev-182, udev no longer creates device nodes under /dev
>
> Nit: Looks like this happened from udev-176 onward.
>
> http://permalink.gmane.org/gmane.linux.hotplug.devel/17230
>
> Whoever is taking the patch can _probably_ fix it up while applying.
>
Hi Sekhar,
Thanks for clarifying this, I read that it was udev-182 from the Linux from
scratch documentation:
http://www.linuxfromscratch.org/lfs/view/jh/chapter07/udev.html
>> and this has to be managed by the kernel devtmpfs filesystem.
>>
>> This means that a kernel built with the current OMAP2+ config
>> will not boot on a system with a recent udev.
>
>> Also, it is good to have /dev automatically mounted since some
>> non-initramfs based setups assumes this and don't manually mount it.
>
> For curiosity sake, any examples of such setups? I am using fedora 17 on
> DaVinci and that doesn't seem to need it. Anyway, agreed that its better
> to keep it enabled.
>
> Thanks,
> Sekhar
>
I'm using an IGEPv2 (TI OMAP3 DM3735) with an openembedded build and the oe udev
init script from the recipe I use seems to assume this.
Best regards,
Javier
next prev parent reply other threads:[~2012-11-27 9:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-21 13:26 [PATCH 1/1] ARM: OMAP2+: enable devtmpfs and devtmpfs automount Javier Martinez Canillas
2012-11-27 8:34 ` Sekhar Nori
2012-11-27 9:20 ` Javier Martinez Canillas [this message]
2012-12-14 18:10 ` Tony Lindgren
2012-12-14 18:16 ` Javier Martinez Canillas
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=50B485E5.1050401@collabora.co.uk \
--to=javier.martinez@collabora.co.uk \
--cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox