From: Mark Lord <lkml@rtr.ca>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Jan Scholz <scholz@fias.uni-frankfurt.de>,
Greg KH <gregkh@suse.de>,
Linux Kernel <linux-kernel@vger.kernel.org>,
USB list <linux-usb@vger.kernel.org>
Subject: Re: libusb broken on 2.6.28 x86_64 ?
Date: Fri, 02 Jan 2009 10:44:44 -0500 [thread overview]
Message-ID: <495E366C.9050309@rtr.ca> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0901020820500.22914-100000@netrider.rowland.org>
Alan Stern wrote:
> On Fri, 2 Jan 2009, Mark Lord wrote:
..
>> This patch, below, FIXES it for me, by undoing a change from 2.6.28.
>>
>> Signed-off-by: Mark Lord <mlord@pobox.com>
>>
>> --- old/drivers/usb/core/driver.c 2008-12-24 18:26:37.000000000 -0500
>> +++ linux/drivers/usb/core/driver.c 2009-01-02 04:34:11.000000000 -0500
>> @@ -279,9 +279,7 @@
>> * altsetting means creating new endpoint device entries).
>> * When either of these happens, defer the Set-Interface.
>> */
>> - if (intf->cur_altsetting->desc.bAlternateSetting == 0)
>> - ; /* Already in altsetting 0 so skip Set-Interface */
>> - else if (!error && intf->dev.power.status == DPM_ON)
>> + if (!error && intf->dev.power.status == DPM_ON)
>> usb_set_interface(udev, intf->altsetting[0].
>> desc.bInterfaceNumber, 0);
>> else
>
> For a proper fix, see
>
> http://bugzilla.kernel.org/show_bug.cgi?id=12301#c13
>
> A corresponding patch has been posted to linux-usb here:
>
> http://marc.info/?l=linux-usb&m=123074111001861&w=2
..
Mmm.. too bad linux-kernel wasn't CC'd on that, or I might have
found the patch and saved some sleep. Good to see that it has
been fixed down in a subsystem tree, though.
> I have no idea what's going on with the 64-bit vs. 32-bit stuff, though.
..
Yeah, something is very broken somewhere, because the _compat ioctl()s
should really produce the same behaviour as the 64-bit ones.
Looking forward to seeing this regression fixed in mainline ASAP.
Cheers
next prev parent reply other threads:[~2009-01-02 15:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-02 6:31 libusb broken on 2.6.28 x86_64 ? Mark Lord
2009-01-02 7:01 ` Mark Lord
2009-01-02 7:24 ` Greg KH
2009-01-02 7:48 ` Mark Lord
2009-01-02 7:51 ` Mark Lord
2009-01-02 7:58 ` Greg KH
2009-01-02 8:15 ` Mark Lord
2009-01-02 8:25 ` Mark Lord
2009-01-02 8:28 ` Greg KH
2009-01-02 9:37 ` Mark Lord
2009-01-02 13:23 ` Alan Stern
2009-01-02 15:44 ` Mark Lord [this message]
[not found] <20090102082824.GA4212@suse.de.suse.lists.linux.kernel>
2009-01-02 11:43 ` Marcus Meissner
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=495E366C.9050309@rtr.ca \
--to=lkml@rtr.ca \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=scholz@fias.uni-frankfurt.de \
--cc=stern@rowland.harvard.edu \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox