Re: [Bitpim-devel] libusb / Darwin

[Roger B. <ro...@ro...>]

>> It is having byte ordering issues.  Those should be 1004 and 6000.
> 
>   Well, yes and now... The Mac is big endian, and it's using a format of
> %04X to print it out, so I think it's really just a visual thing.

Nope.  It means that whatever returned an int/short didn't do the necessary
byte swapping under the hood they should have.

>   in the _openusb() method of commport.py, I had to insert the following
> call:
> 
>           usb.UpdateLists()

UpdateLists is called automatically on import of the usb module.  It
should also be called before each round of auto-probes although I
don't know if that is coded.

It is also unfortunately an unsafe function to call due to the
way libusb works.  Effectively all pointers become invalidated
as they can be rejigged around.
 
Roger