On Sat, Aug 6, 2011 at 1:19 PM, Charles Romestant <cromest...@gmail.com> wrote: > I was just playing with the USB prober, and rightly so, there is little less > information than the name given in the probe, even with the "probe suspended > device" option activated. > Then again, after clicking on any button on the control, the probe is > successful in giving all the info wanted. > I think that unless there is a way to activate the device programaticaly > ,through the HUB maybe, I'll have to rely on looping until there is no > error... > What is not congruent with this is that in python I am able to get some info > correctly before setting the configuration, and the device being inactive. > (you can see a output here http://pastebin.com/nht9n9zL) > I'm still baffled by this, will keep researching
I think this makes sense and it is consistent with the USB Prober behavior. I believe pyusb need the dev.set_configuration() call to be able to do real I/O. But before that, you can get some basic information which is similar to what you get from USB Prober, even when the device is suspended. But I am not familiar with Mac OS X myself. And this particular issue has nothing to do with pyusb but rather libusb-1.0 on Mac OS X. You may want to ask in the libsub mailing list. BTW, you may want to check out the latest libusb-1.0 git version for Mac OS X and it might help. http://git.libusb.org/?p=libusb-darwin.git;a=summary;js=1 -- Xiaofan ------------------------------------------------------------------------------ BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1 _______________________________________________ pyusb-users mailing list pyusb-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/pyusb-users
