> Apparently, there's a window when OHCI is shut down, when we shut the
> controller down and freed hcca, but did not release the IRQ. On a shared
> IRQ, some other device interrupts, and we oops referring to hcca.
>
> The attached patch looks like a ham-fisted way to fix this ...
Indeed. Did you
Hi, Alan:
Here's one more bug I'd like to discuss.
Kimball Murray from Stratus found this oops, and it's easily reproducible
on his hardware. They have some electronic means to unplug hardware, so
running a test which plugs and unplugs in a loop causes an oops.
Apparently, there's a window when
On Tue, 15 Aug 2006 11:37:49 -0400 (EDT), Alan Stern <[EMAIL PROTECTED]> wrote:
> As long as you are cleaning things up, here are a few more things to
> correct along the way... :-)
How about now?
-- Pete
diff -urp -X dontdiff linux-2.6.18-rc6/Documentation/usb/error-codes.txt
linux-2.6.18-r
On Tue, Sep 05, 2006 at 04:12:24PM +0100, Tony Olech wrote:
> + #include
> + #include
> + #include
> + #include
> + #include
> + #include
> + #include
> + #include
> + #include
> + #include
> + #include
> + #include
> + #include
> + #include
> + #include
> + #include
> + #include
>
On Tue, Sep 05, 2006 at 04:12:24PM +0100, Tony Olech wrote:
> + #define FTDI_ERR(format, arg...) printk(KERN_ERR "ftdi.%d " format \
> + " *ERROR*\n", ftdi->sequence_num, ## arg)
> + #define ELAN_ERR(format, arg...) printk(KERN_ERR "ftdi " format "
> *ERROR*\n", \
> + ## arg)
> + #
The command "cdrecord dev=/dev/uba x.iso" prints nasty garbage if a blank
is not in the drive. This happens because drivers have to set req->errors
separately from just returning zero uptodate with end_that_request_first,
end_that_request_last. These functions only set error in BIO, but sg_io()
ign
On Thursday 07 September 2006 15:24, Iñaky Pérez-González wrote:
> Sorry, messed up with my mailer -- retrying
>
For those who is still not obvious, I am not really that proficient
with quilt and friends; this means I screwed up--thanks to gregkh
for fixing it up.
---
From: Nobuhiro Iwamatsu <[EMAIL PROTECTED]>
This patch is support USB20SVGA-WH & USB20SVGA-DG of the sisusb device.
As for this device, Device ID is different according to the color of the
product. A blue device is supported. However, a green, white device is
not supported.
http://www.lubic.jp/u
From: Ralf Schlatterbeck <[EMAIL PROTECTED]>
The patch adds a new device ID for the Gamma Scout Geiger counter
device.
Signed-off-by: Ralf Schlatterbeck <[EMAIL PROTECTED]>
Signed-off-by: Greg Kroah-Hartman <[EMAIL PROTECTED]>
---
drivers/usb/serial/ftdi_sio.c |1 +
drivers/usb/serial/ftdi_s
From: Kai Lindhom <[EMAIL PROTECTED]>
From: Kai Lindhom <[EMAIL PROTECTED]>
Signed-off-by: Daniel Ritz <[EMAIL PROTECTED]>
Acked-by: Dmitry Torokhov <[EMAIL PROTECTED]>
Signed-off-by: Greg Kroah-Hartman <[EMAIL PROTECTED]>
---
drivers/usb/input/usbtouchscreen.c |2 +-
1 files changed, 1 inser
From: Adrian Bunk <[EMAIL PROTECTED]>
On Fri, Sep 01, 2006 at 01:58:18AM -0700, Andrew Morton wrote:
>...
> Changes since 2.6.18-rc4-mm3:
>...
> +gregkh-usb-hid-core.c-adds-all-gtco-calcomp-digitizers-and-interwrite-school-products-to-blacklist.patch
>...
> USB tree updates.
>...
The GNU C compi
Here are a some fixes for USB against 2.6.18-rc6. They do the
following:
- build warning fix in the usbhid driver
- usb touchscreen bugfix
- new device id added to the ftdi_sio driver
- new device id added to the sisusbvga driver
Please pull from:
master.ke
Sorry, messed up with my mailer -- retrying
usb: introduce usb_reenumerate_device()
This function implements a logical reset which will cause the device
to be reenumerated in the USB stack, without physically being
disconnected from the bus.
This is useful for device-firmware-upload cases where
usb: introduce usb_reenumerate_device()
This function implements a logical reset which will cause the device
to be reenumerated in the USB stack, without physically being
disconnected from the bus.
This is useful for device-firmware-upload cases where we can't use
usb_reset_device() as it would b
Alan Stern wrote:
>> I have an usb HP cd-writer plus 8200. It is not working properly with
>> usb-storage (linux 2.6.17.1 righ now, but does'nt work with eny 2.6 kernel,
>> udev 0.97), and is identified by the system as a hard disk (sda) insted of a
>> removable cd device (sr0).
This is fixed
On Sun, 2006-09-03 at 23:40 -0700, David Brownell wrote:
>
> > Going through the ethtool operations, I think that it should be
> > possible to implement a few of them, including ETHTOOL_GREGS,
> > ETHTOOL_GEEPROM, ETHTOOL_SEEPROM, ETHTOOL_NWAY_RST and ETHTOOL_GPERMADDR.
> > Do you think these sho
On Thursday 07 September 2006 15:25, Daniel Ritz wrote:
> before 2.6.19, please :)
>
> [PATCH] usbtouchscreen: fix ITM data reading
>
> From: Kai Lindhom <[EMAIL PROTECTED]>
> Signed-off-by: Daniel Ritz <[EMAIL PROTECTED]>
>
Acked-by: Dmitry Torokhov <[EMAIL PROTECTED]>
Greg, will you push it t
On Thu, 7 Sep 2006, Siddharth Choudhuri wrote:
> Thanks. I put printk() in sd_init_command() to output
> block(rq->sector) and count(Scpnt->request_bufflen >>
> 9). Now, I can see the [read/write, block, count] as I
> start some file I/O activity on a mounted usb flash
> disk (moutned as vfat). I
before 2.6.19, please :)
[PATCH] usbtouchscreen: fix ITM data reading
From: Kai Lindhom <[EMAIL PROTECTED]>
Signed-off-by: Daniel Ritz <[EMAIL PROTECTED]>
diff --git a/drivers/usb/input/usbtouchscreen.c
b/drivers/usb/input/usbtouchscreen.c
index 3b175aa..a338bf4 100644
--- a/drivers/usb/input/u
--
This is a multi-part message in MIME format.
Command 'this' not recognized.
--=_NextPart_4.67609405517578E-02
Command '--=_nextpart_4.67609405517578e-02' not recognized.
Content-Type: text/html; format=flowed
Command 'content-type:' not recognized.
>>
>
> If you want to get this information, you're probably
> better off getting it
> at the point where it is sent to the device, not at
> the points where the
> conversions are made. For example, take a look at
> sd_init_command() in
> drivers/scsi/sd.c.
>
Thanks. I put printk() in sd_init_comman
On Thu, 7 Sep 2006, Luigi Genoni wrote:
> Hi,
>
> I have an usb HP cd-writer plus 8200. It is not working properly with
> usb-storage (linux 2.6.17.1 righ now, but does'nt work with eny 2.6 kernel,
> udev 0.97), and is identified by the system as a hard disk (sda) insted of a
> removable cd d
Hi,
I have an usb HP cd-writer plus 8200. It is not working properly with
usb-storage (linux 2.6.17.1 righ now, but does'nt work with eny 2.6 kernel,
udev 0.97), and is identified by the system as a hard disk (sda) insted of a
removable cd device (sr0).
it is plugged correctly and i see in /p
23 matches
Mail list logo
