From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?ISO-8859-1?B?Sm9z6SBG6WxpeCBPbnRh8fNu?= Date: Wed, 19 Jan 2011 22:55:54 +0000 Subject: Re: Proper way to get USB class codes Message-Id: List-Id: References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable To: linux-hotplug@vger.kernel.org El d=EDa 15 de enero de 2011 19:26, Jos=E9 F=E9lix Onta=F1=F3n escribi=F3: > Hello everybody, > I've got some doubts and problems getting USB class codes via udev and > i'll be very grateful if someone could clarify. > > First of all, using udevadm i've realized some usb devices left the > class/subclass/protocol attributes with 00: > > =A0 =A0ATTR{bDeviceClass}=3D"00" > =A0 =A0ATTR{bDeviceSubClass}=3D"00" > =A0 =A0ATTR{bDeviceProtocol}=3D"00" > > Is that an issue on the usb device itself or an issue on udev reading > usb device/interface descriptor? > > Second, i've some doubts about when should I use the > ID_USB_INTERFACES, TYPE or INTERFACE property: in which cases should I > use one or another? Why the TYPE property sometimes appear as 0/0/0 > even when the ID_USB_INTERFACES and INTERFACE properties are filled? > > Thanks for sharing your thoughs. Hello everyone, I've been doing some tests and the fact is I think this could be an udev bug: HAL reports class/subclass/protocol for all USB devices with no failures at all. Here the same example as above but using HAL: usb.interface.class =3D 11 (0xb) (int) usb.interface.subclass =3D 0 (0x0) (int) usb.interface.protocol =3D 0 (0x0) (int) After had been looking through bugzilla.kernel.org I realized there weren't any bug reported about it. Does anyone think, like me, this could be a bug? Would somebody tell me if i can perform some more tests before reporting the bug myself? Thanks in advance. --=20 http://fontanon.org