[Buildroot] efficient usb plug in notification

[Buildroot] efficient usb plug in notification

[Christopher Taylor]

I'm trying to see what my best options are of getting USB plugin
notifications in user-space in a buildroot/uClibc env.

Since this is an embedded platform, I'm really concerned about
efficiency of the mechanisms and I'm not sure how efficient udev +
dbus + hal is. Does anyone have any thoughts on this and what some
reasonable alternatives are within the buildroot chain?

-Chris

[Buildroot] efficient usb plug in notification

[sjhill at realitydiluted.com]

> I'm trying to see what my best options are of getting USB plugin
> notifications in user-space in a buildroot/uClibc env.
> 
Is this for USB storage devices only, or all types of USB devices?

> Since this is an embedded platform, I'm really concerned about
> efficiency of the mechanisms and I'm not sure how efficient udev +
> dbus + hal is. Does anyone have any thoughts on this and what some
> reasonable alternatives are within the buildroot chain?
> 
I used 'udev' in all my embedded platforms. I did the original work
of getting dbus and hal into buildroot, but it was a royal pain. If
you are just doing USB storage devices, look at the usbmount package.
It works great and I can certainly help you with that if you hit any
snags.

-Steve

[Buildroot] efficient usb plug in notification

[Christopher Taylor]

Thank y ou so much for your reply

On Wed, Aug 6, 2008 at 11:18 AM,  <sjhill@realitydiluted.com> wrote:
>> I'm trying to see what my best options are of getting USB plugin
>> notifications in user-space in a buildroot/uClibc env.
>>
> Is this for USB storage devices only, or all types of USB devices?

Well I have two different projects. One is USB devices in general and
it's VERY power conscious and the other is just USB storage and it's
not that big of a deal.


> I used 'udev' in all my embedded platforms. I did the original work
> of getting dbus and hal into buildroot, but it was a royal pain. If
> you are just doing USB storage devices, look at the usbmount package.
> It works great and I can certainly help you with that if you hit any
> snags.

Is power consumption/battery life  an issue on any of the projects you
used the udev/dbus/hal combination and were you able to quantify their
effect on power usage?

Thank you very much for your suggestion, I may post again if I run
into any snags.

IN getting dbus and hal into buildroot, did you get it into the
toolchain or is it that you were able to get it into the fs role
inside buildroot.  Either one deserves kudos.

-Chris

[Buildroot] efficient usb plug in notification

[Hinko Kocevar]

Christopher Taylor wrote:
> I'm trying to see what my best options are of getting USB plugin
> notifications in user-space in a buildroot/uClibc env.
> 
> Since this is an embedded platform, I'm really concerned about
> efficiency of the mechanisms and I'm not sure how efficient udev +
> dbus + hal is. Does anyone have any thoughts on this and what some
> reasonable alternatives are within the buildroot chain?
> 

There is a mdev applet in busybox - a smaller version of udev. It works 
similar to hotplug. I haven't used it extensively but it is not hard 
to use, plus everything is in the buildroot already;)

See http://wildanm.wordpress.com/2007/08/21/mdev-mini-udev-in-busybox.

HTH,
Hinko

-- 
?ETRTA POT, d.o.o., Kranj
Planina 3
4000 Kranj
Slovenia, Europe
Tel. +386 (0) 4 280 66 03
E-mail: hinko.kocevar at cetrtapot.si
Http: www.cetrtapot.si

[Buildroot] efficient usb plug in notification

[shaleh at speakeasy.net]

An HTML attachment was scrubbed...
URL: http://busybox.net/lists/buildroot/attachments/20080806/078ceab5/attachment.htm 

[Buildroot] efficient usb plug in notification

[Christopher Taylor]

> 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.

Thanx everyone for sharing your experience!

-Chris

[Buildroot] efficient usb plug in notification

[Sean Perry]

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.