All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven King <sfking@fdwdc.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [linux-usb-devel] ti_usb_3410_5052 breakage in 2.6.24-rc1
Date: Thu, 1 Nov 2007 09:19:52 -0700	[thread overview]
Message-ID: <200711010919.53057.sfking@fdwdc.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0711011044400.4146-100000@iolanthe.rowland.org>

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 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.


 100% certain.  After bisecting it, I reversed that commit on an otherwise 
stock -rc1 and the device started working again.

-- 
Steven King -- sfking at fdwdc dot com

  reply	other threads:[~2007-11-01 16:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-01  5:25 ti_usb_3410_5052 breakage in 2.6.24-rc1 Steven King
2007-11-01  6:19 ` Greg KH
2007-11-01  6:34   ` Steven King
2007-11-01 10:25   ` Steven King
2007-11-01 14:51     ` [linux-usb-devel] " Alan Stern
2007-11-01 17:31       ` Steven King
2007-11-01 20:08         ` Alan Stern
2007-11-01 14:47 ` Alan Stern
2007-11-01 16:19   ` Steven King [this message]
     [not found] <200711011634.32360.sfking@fdwdc.com>
2007-11-02 21:14 ` Alan Stern

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200711010919.53057.sfking@fdwdc.com \
    --to=sfking@fdwdc.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.