From: Sven Neumann <s.neumann@raumfeld.com>
To: buildroot@busybox.net
Subject: [Buildroot] $udevroot
Date: Thu, 11 Aug 2011 19:32:50 +0200 [thread overview]
Message-ID: <1313083971.12036.10.camel@bender> (raw)
In-Reply-To: <4E43EE96.1020405@visionsystems.de>
On Thu, 2011-08-11 at 17:00 +0200, Yegor Yefremov wrote:
> > we are facing some problems with device nodes since the udev update. Now
> > I am trying to understand how the whole device management works
> > nowadays.
>
> What problems are you facing?
Well, I went with the default of using a static device table and
obviously I need to add some device files that are otherwise missing.
But I'll now to try to use udev instead.
Thanks,
Sven
next prev parent reply other threads:[~2011-08-11 17:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-11 14:32 [Buildroot] $udevroot Sven Neumann
2011-08-11 15:00 ` Yegor Yefremov
2011-08-11 17:32 ` Sven Neumann [this message]
2011-08-11 23:10 ` Diego Iastrubni
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=1313083971.12036.10.camel@bender \
--to=s.neumann@raumfeld.com \
--cc=buildroot@busybox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.