From: Nuno S. <ns...@ed...> - 2009-08-31 11:23:31
|
Hi, I've looked the API in search of handling of connection and disconnection of devices but couldn't find anything. What are the mechanism available to detect such ocorrences? Thanks, Nuno |
From: Daniel D. <ds...@ge...> - 2009-09-01 18:33:23
|
Nuno Santos wrote: > Hi, > > I've looked the API in search of handling of connection and > disconnection of devices but couldn't find anything. > > What are the mechanism available to detect such ocorrences? If you've opened and are using a device, most functions return a special error code when the device goes away. Notification for connection and disconnection is planned for libusb-1.1. I expect the implementation will use some combination of udev, HAL, and DeviceKit. Daniel |
From: <Phi...@mi...> - 2009-09-01 18:56:12
|
I currently use a udev rules file which in turn calls a bash script to keep a "tools" file up-to-date on which devices are currently plugged in. The bash script in turn invokes a small C++ app that acts as a socket client and attempts to write plug and unplug information to a socket (server). If the server is not there, no harm done. I then have an application (in java) which acts as that server when it's up and running, accepting unsolicited updates from that C++ client. The java app then can act upon these plug and unplug "notifications". I pass through the socket a unique identifier (supplied by the bash script), the vid, serial number, and major and minor system numbers (supplied by the OS). The uid, serial number, and minor system number are all unique (with the uid and minor number being sequential in nature for plug and "re-plug" events). Although it's a bit "Rube Goldberg" in nature, it does work well on Linux. (The same scheme can be emulated in Windows if one does not want to change the java app code.) -----Original Message----- From: Daniel Drake [mailto:ds...@ge...] Sent: Tuesday, September 01, 2009 11:31 AM To: Nuno Santos Cc: lib...@li... Subject: Re: [Libusb-devel] Handling connect and disconnect of device Nuno Santos wrote: > Hi, > > I've looked the API in search of handling of connection and > disconnection of devices but couldn't find anything. > > What are the mechanism available to detect such ocorrences? If you've opened and are using a device, most functions return a special error code when the device goes away. Notification for connection and disconnection is planned for libusb-1.1. I expect the implementation will use some combination of udev, HAL, and DeviceKit. 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 Lib...@li... https://lists.sourceforge.net/lists/listinfo/libusb-devel |
From: Nuno S. <ns...@ed...> - 2009-09-02 08:29:41
|
Hi Daniel, Thanks. That would be enough. Regards, Nuno Daniel Drake escreveu: > Nuno Santos wrote: >> Hi, >> >> I've looked the API in search of handling of connection and >> disconnection of devices but couldn't find anything. >> >> What are the mechanism available to detect such ocorrences? > > If you've opened and are using a device, most functions return a > special error code when the device goes away. > > Notification for connection and disconnection is planned for > libusb-1.1. I expect the implementation will use some combination of > udev, HAL, and DeviceKit. > > Daniel > |
From: Eberhard F. <e....@wa...> - 2009-09-02 12:39:07
|
Hi, On 1. September 2009 20:31:26 Daniel Drake wrote: > Nuno Santos wrote: > > Hi, > > > > I've looked the API in search of handling of connection and > > disconnection of devices but couldn't find anything. > > > > What are the mechanism available to detect such ocorrences? > > Notification for connection and disconnection is planned for libusb-1.1. > I expect the implementation will use some combination of udev, HAL, and > DeviceKit. > > Daniel Isn't that what inotify on Linux was invented for? Here is a short article about it: http://www.linuxjournal.com/article/8478 Works well with libusb. Simply create a watch for changes in the directroy where your device appears when plugged in and check the list of devices that interest your application. Eberhard |
From: Peter S. <pe...@st...> - 2009-09-05 12:40:40
|
Daniel Drake wrote: > I expect the implementation will use some combination of udev, HAL, > and DeviceKit. Eberhard Fahle wrote: > Isn't that what inotify on Linux was invented for? I would certainly prefer using inotify over udev+HAL+DeviceKit. //Peter |
From: Michael L. <mil...@gm...> - 2009-09-03 15:43:49
|
On Mon, Aug 31, 2009 at 7:23 AM, Nuno Santos<ns...@ed...> wrote: > Hi, > > I've looked the API in search of handling of connection and > disconnection of devices but couldn't find anything. > > What are the mechanism available to detect such ocorrences? > It might be worth noting that OpenUSB already has interfaces for handling device connects and disconnects. It is a very well tested feature. --Mike |