From: Paul Chavent <paul.chavent@fnac.net>
To: linux-hotplug@vger.kernel.org
Subject: /dev/fw major not constant (embedded mdev devtmpfs ieee1394)
Date: Thu, 21 Jan 2010 20:56:10 +0000 [thread overview]
Message-ID: <4B58BF6A.6070303@fnac.net> (raw)
Hi.
I'am working on an embedded gnu/linux system that allow to capture an ieee1394 stream.
The system is compound of a kernel, a basic initrd (libc,libgcc,busybox,libdc1394,...) and my app.
I use the new firewire stack.
As my system is very minimalist, i tought to create the nodes in /dev at the moment of building my initrd.
But when i needed to modify my kernel configuration, it has changed the major number of /dev/fw*.
It's not really important for the definitive system (it will be freeze), but i wonder how to solve this issue for my future works ?
I don't need hotplug, i just need to fill /dev at startup (coldplug). The target is an embedded device, so it should be easy to build/configure/install, and lightweight.
For those reasons i don't want to use udev.
I tried mdev (i run mdev -s in my startup script) from busybox. The problem is that mdev only look in /sys/class for filling /dev (i have notified their mailing list http://lists.busybox.net/pipermail/busybox/2010-January/071384.html).
The linux ieee1394 wiki people give me some idea (http://marc.info/?t\x126390679500003&r=1&w=2) :
- maintain a local patch for making the major constant
- use devtmpfs
I prefer to try devtmpfs, but i would like to have your opinion on how would you do for me ?
Thank for your reading.
Paul.
next reply other threads:[~2010-01-21 20:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-21 20:56 Paul Chavent [this message]
2010-01-21 20:57 ` /dev/fw major not constant (embedded mdev devtmpfs ieee1394) Greg KH
2010-01-21 20:59 ` Grant Likely
2010-01-21 21:21 ` Mike Frysinger
2010-01-21 21:26 ` Greg KH
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=4B58BF6A.6070303@fnac.net \
--to=paul.chavent@fnac.net \
--cc=linux-hotplug@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).