From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: Jiri Kosina <jikos@jikos.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel 2.6.22-rc3 breaks USB: Unable to get HID descriptor (error sending control message: Operation not permitted)
Date: Sun, 3 Jun 2007 07:52:31 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0706030749580.3653@p34.internal.lan> (raw)
In-Reply-To: <Pine.LNX.4.64.0706031321450.29896@twin.jikos.cz>
On Sun, 3 Jun 2007, Jiri Kosina wrote:
> On Sun, 3 Jun 2007, Justin Piszcz wrote:
>
>>> Thanks. Does by any chance reverting the commit
>>> 9f8b17e643fe6aa505629658445849397bda4e4f improve the situation?
>> I have not played around with git/etc enough to back it out, if you have a
>> patch that applies on top of 2.6.22-rc3 that backs it out I can give it a try.
>
> Please try this
[[ .. snip .. ]]
The patch was successful and now my USB device is working again!
p34:/usr/src/linux-2.6.22-rc3# patch -p1 < ../usb.patch
patching file drivers/usb/core/Kconfig
patching file drivers/usb/core/devio.c
patching file drivers/usb/core/driver.c
patching file drivers/usb/core/hub.c
patching file drivers/usb/core/inode.c
patching file drivers/usb/core/message.c
patching file drivers/usb/core/usb.c
patching file drivers/usb/core/usb.h
patching file include/linux/usb.h
p34:/usr/src/linux-2.6.22-rc3#
[[ .. recompile/reboot .. ]]
p34:~# upsc belkin@localhost
battery.charge: 100
battery.charge.low: 30
battery.charge.warning: 50
battery.runtime: 210
battery.type: PbAc
battery.voltage: 27.1
battery.voltage.nominal: 24
driver.name: newhidups
driver.parameter.pollfreq: 5
driver.parameter.port: auto
driver.version: 2.0.4
driver.version.data: Belkin HID 0.1
driver.version.internal: 0.28
input.frequency: 59.8
input.frequency.nominal: 60
input.sensitivity: normal
input.transfer.high: 136
input.transfer.high.max: 141
input.transfer.high.min: 131
input.transfer.low: 90
input.transfer.low.max: 95
input.transfer.low.min: 85
input.voltage: 122.8
input.voltage.nominal: 120
output.frequency: 59.8
output.voltage: 122.0
ups.beeper.status: enabled
ups.delay.restart: 0
ups.delay.shutdown: 0
ups.firmware: 4
ups.load: 43
ups.load.high: 100
ups.mfr: Belkin
ups.mfr.date: 2002/03/01
ups.model: UPS
ups.power.nominal: 1200
ups.serial: D2002337105
ups.status: OL CHRG
ups.test.result: No test initiated
ups.type: offline
p34:~#
p34:~# uname -a
Linux p34.internal.lan 2.6.22-rc3 #2 SMP Sun Jun 3 07:45:09 EDT 2007 x86_64 GNU/Linux
p34:~#
It looks good to me, very nice-- hopefully it will get into 2.6.22 final?
Thanks!
Justin.
next prev parent reply other threads:[~2007-06-03 11:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-02 22:43 Justin Piszcz
2007-06-03 9:49 ` Jiri Kosina
2007-06-03 10:36 ` Justin Piszcz
2007-06-03 10:54 ` Oliver Neukum
2007-06-03 12:29 ` Justin Piszcz
2007-06-03 11:00 ` Jiri Kosina
2007-06-03 11:16 ` Justin Piszcz
2007-06-03 11:22 ` Jiri Kosina
2007-06-03 11:52 ` Justin Piszcz [this message]
2007-06-03 12:35 ` Kay Sievers
2007-06-03 12:40 ` Justin Piszcz
2007-06-03 12:44 ` Justin Piszcz
2007-06-03 16:51 ` Kay Sievers
2007-06-03 9:55 ` Jiri Kosina
2007-06-03 10:48 ` [linux-usb-devel] " Oliver Neukum
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=Pine.LNX.4.64.0706030749580.3653@p34.internal.lan \
--to=jpiszcz@lucidpixels.com \
--cc=jikos@jikos.cz \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®