Re: [Bitpim-devel] libusb

[Steven P. <n9...@n9...>]

On Dec 9, 2003, at 11:54 PM, Roger Binns wrote:
> That is your phone.  The libusb api has you claiming the
> interfaces seperately from the device as a whole.  On Linux
> you can't claim an interface if there is a device driver
> attached, but the acm driver only attaches to interface
> 0 & 1  (interrupt and data for the modem) and leaves the
> diagnostics interface (2) seperate.  I don't know how you
> get around it.

  Let me get this straight, because I think I'm reading that both 
ways....

  Either you *CAN* grab the interfaces separately from the device as a 
whole, thus allowing the kernel driver to handle the serial_com 
interfaces and leaving the vendor_specific interface for you, *OR* you 
can NOT grab them separately in which case I don't know how you'd get 
it to work. ;-)

(from another e-mail, you write)
> that).  The second bit looks to be the driver it attached but it 
> doesn't
> look like it gave you a device name.

  Not all USB devices on MacOS are actually assigned a filesystem device 
name. They aren't accessed by that anyway... If you look at the libusb 
code, darwin.c in particular, you'll see the way to enlightenment on 
MacOS by stepping through IOKit for enumerated devices and interfaces 
on them. The trouble is, as far as I can tell, that if MacOS X assigns 
a driver to the device you can not open it to enumerate the interfaces.

  I'm working on it... ;^)

-. ----. -.-- - -.--
Steve Palm - n9...@n9...
-. ----. -.-- - -.--