From: Grant Likely <grant.likely@secretlab.ca>
To: Paul Chavent <paul.chavent@fnac.net>
Cc: linux-embedded@vger.kernel.org, linux-hotplug@vger.kernel.org,
linux1394-devel@lists.sourceforge.net, busybox@busybox.net,
libdc1394-devel@lists.sourceforge.net
Subject: Re: /dev/fw major not constant (embedded mdev devtmpfs ieee1394)
Date: Thu, 21 Jan 2010 13:59:31 -0700 [thread overview]
Message-ID: <fa686aa41001211259v6e1c3e41mf1e94949e5597dea@mail.gmail.com> (raw)
In-Reply-To: <4B58BF6A.6070303@fnac.net>
On Thu, Jan 21, 2010 at 1:56 PM, Paul Chavent <paul.chavent@fnac.net> wrote:
> Hi.
>
> I'am working on an embedded gnu/linux system that allow to capture an
> ieee1394 stream.
[...]
> But when i needed to modify my kernel configuration, it has changed the
> major number of /dev/fw*.
[...]
> The linux ieee1394 wiki people give me some idea
> (http://marc.info/?t=126390679500003&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 ?
devtmpfs is probably your best bet as that is what it is designed for.
You can also run a trivial script at boot to read /proc/devices and
create the device nodes as described in chapter 3, page 47 of LDD3:
http://lwn.net/images/pdf/LDD3/ch03.pdf
g.
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
prev parent reply other threads:[~2010-01-21 20:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-21 20:56 /dev/fw major not constant (embedded mdev devtmpfs ieee1394) Paul Chavent
2010-01-21 20:57 ` Greg KH
2010-01-21 21:21 ` Mike Frysinger
2010-01-21 21:26 ` Greg KH
2010-01-21 20:59 ` Grant Likely [this message]
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=fa686aa41001211259v6e1c3e41mf1e94949e5597dea@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=busybox@busybox.net \
--cc=libdc1394-devel@lists.sourceforge.net \
--cc=linux-embedded@vger.kernel.org \
--cc=linux-hotplug@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=paul.chavent@fnac.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;
as well as URLs for NNTP newsgroup(s).