From: Mike Frysinger <vapier.adi@gmail.com>
To: Greg KH <greg@kroah.com>
Cc: linux-embedded@vger.kernel.org, busybox@busybox.net,
libdc1394-devel@lists.sourceforge.net,
linux-hotplug@vger.kernel.org,
Paul Chavent <paul.chavent@fnac.net>,
linux1394-devel@lists.sourceforge.net
Subject: Re: /dev/fw major not constant (embedded mdev devtmpfs ieee1394)
Date: Thu, 21 Jan 2010 16:21:26 -0500 [thread overview]
Message-ID: <8bd0f97a1001211321t4aea0ee0q8e0e253be2eff65a@mail.gmail.com> (raw)
In-Reply-To: <20100121205711.GA29455@kroah.com>
On Thu, Jan 21, 2010 at 15:57, Greg KH wrote:
> On Thu, Jan 21, 2010 at 09:56:10PM +0100, Paul Chavent wrote:
>> 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.
>
> Why, is udev somehow not "lightweight"?
in comparison, it is absolutely not
-mike
------------------------------------------------------------------------------
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
next prev parent reply other threads:[~2010-01-21 21:21 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 [this message]
2010-01-21 21:26 ` Greg KH
2010-01-21 20:59 ` Grant Likely
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=8bd0f97a1001211321t4aea0ee0q8e0e253be2eff65a@mail.gmail.com \
--to=vapier.adi@gmail.com \
--cc=busybox@busybox.net \
--cc=greg@kroah.com \
--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).