Hotplug

View: New views
4 Messages — Rating Filter:   Alert me  

Hotplug

by azdes :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

I have seen discussion that hotplug support was going to be included in libusb 2.0. Is there a timetable for hotplug?
 
It is very much needed in our applications. We are using a combination of a udev script and C++ app at the moment and communicating via sockets to a Java app.
 
I would much rather just give libusb a callback for a specific device and have that callback notified when the unit is unplugged. And have a "general" callback that would be called when a new device is plugged in. Is this the way the hotplug is planned?
 
Thanks.
 
-- Phil
 

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Libusb-devel mailing list
Libusb-devel@...
https://lists.sourceforge.net/lists/listinfo/libusb-devel

Re: Hotplug

by Mike Lewis :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

It might be worth checking out OpenUSB. It already supports hotplugging in just the way you mentioned.

--Mike Lewis
"Be who you are and say how you because those mind don't matter and those who matter don't mind." -- Dr. Suess

-----Original Message-----
From: <Philip.Joslin@...>
Date: Wed, 4 Nov 2009 14:26:03
To: <libusb-devel@...>
Subject: [Libusb-devel] Hotplug

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july


------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Libusb-devel mailing list
Libusb-devel@...
https://lists.sourceforge.net/lists/listinfo/libusb-devel

Re: Hotplug

by Daniel Drake-2 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Philip.Joslin@... wrote:
> I have seen discussion that hotplug support was going to be included in
> libusb 2.0. Is there a timetable for hotplug?

I think we'll include it in the near future.

I've just started to work on a libudev-based implementation. This means
it will require a fairly modern Linux platform.

I'll design it so that adding a dbus-based hotplug backend will be
possible in future. Then it could listen for events from HAL on older
platforms, covering a larger userbase.

Which platform setup will you be running on? Does it have libudev? (just
a quick ls in /lib or /usr/lib should a be good enough answer)

I guess we also have some embedded users interested in this
functionality too, who probably don't have udev (or perhaps simply don't
yet have a modern version with libudev), or are Linux 2.4 users, in
which case adding a "plan C" backend may also be appropriate too: one
that creates a thread that watches for changes in the usbfs directories.
Then we should have everything covered...

> I would much rather just give libusb a callback for a specific device
> and have that callback notified when the unit is unplugged. And have a
> "general" callback that would be called when a new device is plugged in.
> Is this the way the hotplug is planned?

More or less - lets see what I come up with :)

Daniel


------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Libusb-devel mailing list
Libusb-devel@...
https://lists.sourceforge.net/lists/listinfo/libusb-devel

Re: Hotplug

by azdes :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

I am running Debian etch and lenny. I don't see libudev in either /lib
or /usr/lib. (I see libudev0 in the Synaptic package manager, but I have
not downloaded it and there is no additional version info on it).

When you get going on this, please keep me informed. I would be happy to
provide some testing and feedback.

Thanks again.

-- Phil

-----Original Message-----
From: Daniel Drake [mailto:dan@...]
Sent: Sunday, November 15, 2009 6:57 AM
To: Philip Joslin - C10554
Cc: libusb-devel@...
Subject: Re: [Libusb-devel] Hotplug

Philip.Joslin@... wrote:
> I have seen discussion that hotplug support was going to be included
> in libusb 2.0. Is there a timetable for hotplug?

I think we'll include it in the near future.

I've just started to work on a libudev-based implementation. This means
it will require a fairly modern Linux platform.

I'll design it so that adding a dbus-based hotplug backend will be
possible in future. Then it could listen for events from HAL on older
platforms, covering a larger userbase.

Which platform setup will you be running on? Does it have libudev? (just
a quick ls in /lib or /usr/lib should a be good enough answer)

I guess we also have some embedded users interested in this
functionality too, who probably don't have udev (or perhaps simply don't
yet have a modern version with libudev), or are Linux 2.4 users, in
which case adding a "plan C" backend may also be appropriate too: one
that creates a thread that watches for changes in the usbfs directories.

Then we should have everything covered...

> I would much rather just give libusb a callback for a specific device
> and have that callback notified when the unit is unplugged. And have a

> "general" callback that would be called when a new device is plugged
in.
> Is this the way the hotplug is planned?

More or less - lets see what I come up with :)

Daniel


------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Libusb-devel mailing list
Libusb-devel@...
https://lists.sourceforge.net/lists/listinfo/libusb-devel