From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Brownell Date: Thu, 17 Jan 2002 20:22:39 +0000 Subject: Re: Forward: hotplugging usb-storage: bcdDevice at fault? 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 The match algorithm in userland is supposed to be exactly the same as that in the kernel. If it doesn't do the same thing, then fix the userland version ... There was some uncertainty about the documentation for that kernel algorithm too, though: it may not have matched the code with respect to this stuff. - Dave ----- Original Message -----=20 From: "Fumitoshi UKAI" To: Sent: Thursday, January 17, 2002 8:22 AM Subject: Forward: hotplugging usb-storage: bcdDevice at fault? > Hi, >=20 > I received the attached mail from a user. As he said, some entries have > bcdDevice_lo =3D bcdDevice_hi with match_flag & 0x0C =3D 0x0C, which means > matches for both device_lo and device_hi. For examples, in=20 > drivers/usb/storage/unusual_devs.h: >=20 > UNUSUAL_DEV( 0x03f0, 0x0207, 0x0001, 0x0001, > "HP", > "CD-Writer+ 8200e", > US_SC_8070, US_PR_SCM_ATAPI, init_8200e, 0), >=20 > But usb.agent code to match device_lo and device_hi is > bcdDevice_lo <=3D bcdDevice < bcdDevice_hi, so it is always fails > because bcdDevice_lo =3D bcdDevice_hi. >=20 > So, why usb.agent doesn't match bcdDevice_lo <=3D bcdDevice <=BCdDevice_h= i? > Is it bugs of usb_device_id entries? >=20 > Thanks, > Fumitoshi UKAI >=20 >=20 _______________________________________________ Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net Linux-hotplug-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel