linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Accessing usb devices with USBDEVFS
Date: Mon, 01 May 2006 16:57:39 +0000	[thread overview]
Message-ID: <20060501165739.GA9729@kroah.com> (raw)
In-Reply-To: <44525468.5030106@ist-traffic.com>

On Mon, May 01, 2006 at 11:39:11AM -0400, Danny Budik wrote:
> Kay Sievers wrote:
> >On Fri, Apr 28, 2006 at 01:44:08PM -0400, Danny Budik wrote:
> >  
> >>I have a question that may or may not be related to hotplugging. I have 
> >>noticed that when I plug in a USB device, it takes about 5 seconds for 
> >>it to show up in /proc/bus/usb/001/xxx. I am using HAL to recognize when 
> >>a USB device is plugged in and USBDEVFS to communicate with my device.
> >>
> >>When I plug it in, dbus/HAL instantly recognizes it and sends me a 
> >>message.  But when I make the function call to open it (using fopen on 
> >>the file above) I get an error that the device is not found. In fact, it 
> >>takes about 5 seconds for the device to show up in the /proc/bus/usb/ 
> >>directory so I have to place a sleep(5) line in my C code before I am 
> >>able to open the device.
> >>
> >>My test machine is a PIII 733 with FC4, latest kernel, so it is a 
> >>relatively slow machine. Is there a way to predict the time that it 
> >>takes for the device to be accessible with USBDEVFS so that I don't have 
> >>to hardcode the sleep statement?
> >>    
> >
> >Recent systems don't use /proc for usb access anymore and real device
> >nodes in /dev/bus/usb instead. HAL sends "usbraw" device anouncements with
> >"linux.device_file" as a property when the device is created.
> >
> >Kay
> So is there a way then to read from the /dev/bus/usb? Like I mentioned 
> in the parent post, I am just using fopen, and the functions provided in 
> usbdevice_fs.h and usb.h to read data from the usb device. The device is 
> a proprietary sensor that my company makes. Is there a 
> manual/documentation about how to do this the more "modern" way?

No, that's still the correct way.  If you use libusb, none of your code
changes at all.   If you are using "raw" usbfs, then just open a
different file.

Hope this helps,

greg k-h


-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x120709&bid&3057&dat\x121642
_______________________________________________
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-05-01 16:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-28 17:44 Accessing usb devices with USBDEVFS Danny Budik
2006-04-28 21:14 ` Greg KH
2006-04-29 13:06 ` Kay Sievers
2006-05-01 15:39 ` Danny Budik
2006-05-01 16:57 ` Greg KH [this message]
2006-05-01 19:00 ` Danny Budik
2006-05-01 19:06 ` Greg KH
2006-05-01 19:09 ` Kay Sievers
2006-05-05 20:45 ` Danny Budik
2006-05-05 21:02 ` Greg KH

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=20060501165739.GA9729@kroah.com \
    --to=greg@kroah.com \
    --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).