[Maybe BUG] hal does not have correct info about usb_device.device_class

[David Zeuthen]

Hi,

[it's getting old, but.. :-)]

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet and in e-mail?

A: No.
Q: Should I include quotations after my reply?

[sorry - now, on a more serious note]

On Fri, 2005-01-21 at 04:24 +0200, Paul Ionescu wrote:
> Hi David,
> 
> In my case, in 
> usb.interface.class 
> I have the value 0 for all 3 interfaces.
> I think I should have e0/e0/fe for int0/int1/int2.
> 

The tripplet (0, 0, 0) means vendor specific interface. I actually
get that with my "Microsoft Wireless Transciever for Bluetooth 2.0"
on the three USB interfaces for Wireless Radio USB device. Yet, the
device class tripplet is (0xe0, 0x01, 0x01) which tells me that
it's indeed a Bluetooth dongle (and Linux 2.6.10 supports it).

(and the really funny thing is that this tiny device actually
exports a USB hub with two other USB HID devices; when I start
hcid these two devices actually go away - oh well)

OTOH, I have a bunch of other multi interface devices that uses
the standard USB protocols and they have different classes for
each device - one of them is a 2xPS2 -> USB converter, pretty
handy actually.

So, I'm pretty sure hal works as intended :-)

Cheers,
David

_______________________________________________
hal mailing list
hal at lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/hal