mobile phone (obex) support in hal

Bastien Nocera hadess at
Fri Feb 16 03:46:16 PST 2007

On Fri, 2007-02-16 at 01:35 +0200, Alex Kanavin wrote:
> 2007/2/16, Bastien Nocera <hadess at>:
> > Adding this would actually be easy, might not even be needed. The
> > Communications Device Class docs[1] say that "0xb" is obex. So
> > "usb.interface.subclass" with a value of "11 (0xb)" means that you have
> > the USB OBEX interface.
> >
> > Does it make sense to translate this property to a string like
> > "usb-obex"?
> There can be several USB OBEX interfaces on one device, reading
> interface desription string is the only way to tell them apart. That
> was my point. See
> for an example.

Ha. Got it now. I double-checked the iInterface value using my Nokia
phone with a DKU2 cable, and only got:
      iInterface              0
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        8
      bAlternateSetting       1
      bNumEndpoints           2
      bInterfaceClass        10 CDC Data
      bInterfaceSubClass      0 Unused
      bInterfaceProtocol      0

So it seems that some data is missing on my phone/cable. In fact all of
the iInterface values are zero for all my USB devices (and there's a

Bastien Nocera <hadess at> 

More information about the hal mailing list