linux-kernel - Re: [linux-usb-devel] ti_usb_3410

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 1 Nov 2007 10:47:24 -0400 (EDT)
From:	Alan Stern <stern@...land.harvard.edu>
To:	Steven King <sfking@...dc.com>
cc:	linux-kernel@...r.kernel.org,
	<linux-usb-devel@...ts.sourceforge.net>
Subject: Re: [linux-usb-devel] ti_usb_3410_5052 breakage in 2.6.24-rc1

On Wed, 31 Oct 2007, Steven King wrote:

>   My TI eZ430 (MSP-FET430UIF JTAG Tool) usb dongle works fine with 2.6.23.1 
> and earlier, but doesn't work with 2.6.24-rc1; the ti_usb_3410_5052 module is 
> loaded but the device descriptor is bogus, reporting only a single 
> configuration, whereas in 2.6.23.1 it reports 2 configurations, allowing one 
> to select the second configuration to get a serial port.
> 
> git bisect fingered this commit:
> 
> 063a2da8f01806906f7d7b1a1424b9afddebc443 "USB: serial core should respect 
> driver requirements"

Are you certain about this?  That commit could not possibly have 
changed the way the USB core evaluates the device or configuration 
descriptors.  In fact, the commit affects only code in the usb-serial 
driver, which doesn't get loaded until well after the descriptors have 
been parsed.

Alan Stern

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/