From: Sean Perry <shaleh@speakeasy.net>
To: buildroot@busybox.net
Subject: [Buildroot] efficient usb plug in notification
Date: Thu, 07 Aug 2008 19:04:44 -0700 [thread overview]
Message-ID: <489BA9BC.7080300@speakeasy.net> (raw)
In-Reply-To: <2590773a0808062026p25ed61c7v23377da3849ad661@mail.gmail.com>
Christopher Taylor wrote:
>> You can replace /sbin/hotplug with a shell script/program of your choice.
>> This gets called by the kernel for every plug event. Just have your version
>> of hotplug react to the plug events you care about. Then you "just" need to
>> figure out how to interact between the hotplug script and your user space
>> libraries, programs, etc.
>>
>
> Given the power concerns that we have, this may be the best idea.
> I'll have to look into what's passed to the hotplug script/program and
> see if we can get all the information from that. Thanx so much for
> this tip!
>
> I'm moderately familiar with udev/dbus/hal but I have some
> reservations about using them due to the extra cycles taken up.
>
> This hotplyg approach seems promising for power conscious platforms
> assuming it provides enough information. A named pipe to our
> application should solve this problem.
>
Everything comes in via the environment, so look there. Should have
everything you need.
mdev just adds a /dev/$node and then calls a script with
$MDEV=/dev/$node. Definitely not enough info and it depends on the
device actually have an entry in /dev -- the usb devices I use do not.
I had our custom hotplug script call mdev when it is done so all of the
device nodes get created correctly.
next prev parent reply other threads:[~2008-08-08 2:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-06 17:19 [Buildroot] efficient usb plug in notification shaleh at speakeasy.net
2008-08-07 3:26 ` Christopher Taylor
2008-08-08 2:04 ` Sean Perry [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-08-06 15:10 Christopher Taylor
2008-08-06 15:18 ` sjhill at realitydiluted.com
2008-08-07 3:23 ` Christopher Taylor
2008-08-07 7:44 ` Hinko Kocevar
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=489BA9BC.7080300@speakeasy.net \
--to=shaleh@speakeasy.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox