linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: hotplugging on an embedded system under 2.6.17(-rcX)
Date: Wed, 07 Jun 2006 12:21:24 +0000	[thread overview]
Message-ID: <1149682884.12235.76.camel@pim.off.vrfy.org> (raw)
In-Reply-To: <Pine.LNX.4.63.0606061132450.1760@pcgl.dsa-ac.de>

On Wed, 2006-06-07 at 14:08 +0200, Guennadi Liakhovetski wrote:
> On Wed, 7 Jun 2006, Kay Sievers wrote:
> 
> > On Wed, 2006-06-07 at 12:06 +0200, Guennadi Liakhovetski wrote:
> >>
> >> That's approximately what I've done now - disabled the default mounting of
> >> tmpfs on the top of /dev
> >
> > But you are not using /dev from flash, right?
> 
> Emn, which flash? It's not NOR-flash in this case, it's on CF... In other 
> setups we do have /dev in NOR-flash. Is it bad? We even did ext2 rw in NOR 
> as /dev - rw because you have to be able to "write" to it, ext2 because it 
> will anyway not be written TO the flash. Now with udev creating new nodes
> dynamically we wouldn't do that of course.

Well, I would always use a tmpfs filesystem on /dev, so you always start
with a well defined setup. As long as we don't have a unionfs we can
overlay over /dev, it's the safest to copy your few initial device nodes
to tmpfs and let udev mess around with it from that point. Udev also
stores temporary files in /dev/.udev may be a bit faster on tmpfs.

> >> and "synthesizing" nodes, left the static initial
> >> device nodes alone, disabled /proc/sys/kernel/hotplug, started udev to let
> >> it handle further hotplug events - seems to work quite good so far! I'll
> >> test benchmark it further, but so far it looks really good!
> >
> > Sounds good.
> 
> Yeah... Only I cannot repeat it... I mean, I have one experimantal system, 
> where it works. And another "clean" system (near to the final 
> configuration) where I cannot get it to work - I cannot get udevd to load 
> modules there... under /dev/.udev/failed I get:

You have the RUN+="/sbin/modprobe $env{MODALIAS}" rules like this,
right?
  http://www.kernel.org/git/?p=linux/hotplug/udev.git;a=blob;hb=HEAD;f=etc/udev/debian/hotplug.rules

Kay



_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

  parent reply	other threads:[~2006-06-07 12:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-06  9:56 hotplugging on an embedded system under 2.6.17(-rcX) Guennadi Liakhovetski
2006-06-07  3:46 ` Greg KH
2006-06-07  8:28 ` Guennadi Liakhovetski
2006-06-07  9:50 ` Kay Sievers
2006-06-07 10:06 ` Guennadi Liakhovetski
2006-06-07 10:27 ` Kay Sievers
2006-06-07 12:08 ` Guennadi Liakhovetski
2006-06-07 12:21 ` Kay Sievers [this message]
2006-06-07 12:41 ` Guennadi Liakhovetski
2006-06-07 13:49 ` Guennadi Liakhovetski

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=1149682884.12235.76.camel@pim.off.vrfy.org \
    --to=kay.sievers@vrfy.org \
    --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).