From: Yuri Bushmelev <jay4mail@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: makedevs vs. device_table-minimal.txt
Date: Thu, 24 Jun 2010 12:30:18 +0400 [thread overview]
Message-ID: <201006241230.18165.jay4mail@gmail.com> (raw)
In-Reply-To: <AANLkTilEWkJxX-05BU-UBnOIP9jgP3vtf8K7jA5-A9Q6@mail.gmail.com>
Hello!
> after commit 66aa4ed9410ba1d652e40571f48a985337e56a26
> (device_table-minimal.txt: fix input device nodes path. Input event
> device nodes are usually under /dev/input.) in /dev of my rootfs I
> don't have any event device node.
>
> Any obvious reason why makedevs would fail to create /dev/input/eventX ?
Please note that this is linux-kexecboot initramfs, not common image rootfs.
We have no device manager (udev/mdev) there.
And (as I understand image.bbclass) there is no possibility to create
directory in rootfs from recipe before makedevs call.
--
Yuri Bushmelev
next prev parent reply other threads:[~2010-06-24 8:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-24 7:54 makedevs vs. device_table-minimal.txt Andrea Adami
2010-06-24 8:30 ` Yuri Bushmelev [this message]
2010-06-24 8:53 ` Andrea Adami
2010-06-24 9:29 ` Koen Kooi
2010-06-24 9:51 ` Andrea Adami
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=201006241230.18165.jay4mail@gmail.com \
--to=jay4mail@gmail.com \
--cc=openembedded-devel@lists.openembedded.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