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
On Sat, Aug 6, 2011 at 5:57 AM, Charles Romestant <cromest...@gmail.com>wrote:
> THank you for your reply Xiaofan,
>
> I see what you say, but reading the last message in that thread you can see
> that they talk about :
>
> "Older version (10.5.6) -- this was the reference I used when adding the
> ability to unsuspend a device (this feature was not present in libusb 0.1):
> "
>
> I am wondering if this hability to "unsuspend a device" is available in
> pyUSB.
> Looking into it, have not found it yet. Will keep looking and will post
> updates
>
>
> On Sat, Aug 6, 2011 at 3:48 AM, Xiaofan Chen <xiaof...@gmail.com> wrote:
>
>> On Sat, Aug 6, 2011 at 9:11 AM, Charles Romestant <cromest...@gmail.com>
>> wrote:
>> > Hello,
>> > I'm playing around with pyUSB on a macbook pro, in order to be able to
>> play
>> > around with the IR port.
>> >
>> > Unless I click on any of the buttons on the remote control (thus I
>> suppose
>> > activating the device).
>> > then the set_configuration works perfectly.
>> > Is there a way to get around this? ( and not just probe until the
>> control
>> > has been clicked).
>>
>> I think that is a limitation of Mac OS X (but I do not have a Mac) if it
>> is true that Mac OS X's USB Prober does not probe suspended device.
>> libusb under Mac OS X use the logic of USB Prober as the base and
>> thus the behavior will be the same. pyusb is on top of libusb.
>> http://libusb.6.n5.nabble.com/OSX-critical-bug-td4576409.html
>>
>>
>> --
>> 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
>>
>
>
>
> --
> Merci de penser à l'environnement avant d'imprimer cet e-mail
> Please think about the environment before you print this e-mail
> Por favor piense en el medio ambiente antes de imprimir este e-mail
>
>
>
> Lic. Charles M. Romestant F.
>
>
>
>
--
Merci de penser à l'environnement avant d'imprimer cet e-mail
Please think about the environment before you print this e-mail
Por favor piense en el medio ambiente antes de imprimir este e-mail
Lic. Charles M. Romestant F.
------------------------------------------------------------------------------
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
