On Thu, 1 Nov 2007, Steven King wrote:
> > But you didn't post the log messages, so I haven't seen them.
> > In addition, that "wrong number of endpoints" message occurs long after
> > the underlying problem; it's probably not connected.
>
> Okay, attached is full .config, dmesg, /proc/bus/usb/de
On Thu, 1 Nov 2007, Steven King wrote:
> > The real question is why 2.6.24-rc1 doesn't like the second
> > configuration descriptor. To answer it, you should see what shows up
> > in the dmesg log when you first plug in the device on a kernel with
> > CONFIG_USB_DEBUG enabled.
>
> ?!? As I wrote
On Thursday 01 November 2007 7:51:25 Alan Stern wrote:
> On Thu, 1 Nov 2007, Steven King wrote:
> > Per a suggestion by David Brownwell, rebuilt with CONFIG_USB_DEBUG
> > enabled and loading usbserial and ti_usb_3410_5052 with debug=1, I see in
> > 'dmesg'
> >
> > 'drivers/usb/serial/usb-serial.c:
On Thursday 01 November 2007 7:47:24 Alan Stern wrote:
> 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
On Thu, 1 Nov 2007, Steven King wrote:
> Per a suggestion by David Brownwell, rebuilt with CONFIG_USB_DEBUG enabled
> and
> loading usbserial and ti_usb_3410_5052 with debug=1, I see in 'dmesg'
>
> 'drivers/usb/serial/usb-serial.c: wrong number of endpoints'
>
> which is pretty much what I ex
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
6 matches
Mail list logo