https://bugzilla.novell.com/show_bug.cgi?id=234147
The joydev driver is not loaded automatically for this joystick:
...
Hardware Class: unknown
Model: Mega World International USB Game Controllers
Vendor: usb 0x07b5 Mega World International Ltd.
Device: usb 0x0314 USB Game Controllers
Module
that distributions drop the badmap/goodmap part from
keycodes/macintosh in the xkeyboard-config package.
Signed-off-by: Olaf Hering [EMAIL PROTECTED]
---
This is probably 2.6.18.x material, if major distros settle on 2.6.18.
drivers/usb/input/hid-core.c |4 ++--
drivers/usb/input/hid-input.c | 17
The USB Powerbooks with ISO keyboards have the KEY_GRAVE/KEY_102ND
keys reversed.
This was already the case for ADB keyboards, see adbhid_input_register().
I tried to reuse the hidinput_pb_setup() function as shown in the patch
below. But this does not change anything. Only the change in
On Thu, Sep 28, Alan Stern wrote:
http://marc.theaimsgroup.com/?l=linux-usb-develm=115921335306280w=2
http://marc.theaimsgroup.com/?l=linux-usb-develm=115921335520143w=2
This fixes the USB keyboard.
-
Take Surveys. Earn
On Wed, Sep 27, Greg KH wrote:
@@ -372,6 +379,15 @@ struct usb_device {
int maxchild; /* Number of ports if hub */
struct usb_device *children[USB_MAXCHILDREN];
+
+#ifdef CONFIG_PM
+ struct work_struct autosuspend; /* for delayed autosuspends */
+
On Wed, Sep 27, Greg KH wrote:
Alan Stern:
usbcore: remove usb_suspend_root_hub
This change between -git8 and -git9 makes my keyboard unhappy:
@@ -16,7 +16,7 @@
htab_address = 0xc0007c00
htab_hash_mask= 0x3
Is this related to the 'max power per port' change? Have read it
somewhere on lkml, no idea if it was introduced in 2.6.16.
https://bugzilla.novell.com/show_bug.cgi?id=179366
Description:
Hello,
I have the weirdest report here, with respect to a Memorex 1GB USB
TravelDrive on my Thinkpad
After recent changes, the USB keyboard as shipped with IBM pSeries systems
does not work anymore, unless the keyboard is replugged after reboot.
Adding this model to the blacklist fixes it.
Signed-off-by: Olaf Hering [EMAIL PROTECTED]
---
drivers/usb/input/hid-core.c |4
1 file
On Thu, May 04, Alan Stern wrote:
This shows that without the blacklist entry for the IBM keyboard, the
usbhid driver sends a GET_REPORT request. Lots of HID devices are known
to choke on these requests; that's why there are so many blacklist entries
with HID_QUIRK_NOGET.
Yes, I had
On Fri, May 05, Olaf Hering wrote:
On Thu, May 04, Alan Stern wrote:
This shows that without the blacklist entry for the IBM keyboard, the
usbhid driver sends a GET_REPORT request. Lots of HID devices are known
to choke on these requests; that's why there are so many blacklist
On Tue, May 02, Alan Stern wrote:
As for 2.6.16... Can you log in without using the keyboard (say over
ssh)? If you can, then use usbmon to trace what's happening with the
keyboard. Maybe rmmod usbhid and modprobe usbhid while you're
monitoring, so we can see the keyboard
On Wed, May 03, Alan Stern wrote:
You should also try adding a backlist entry with HID_QUIRK_NOGET for your
keyboard.
Yes, that seems to fix it. I have added this. lsusb shows 2 keyboards
with different ids. Should I add both (3005 and 3006)?
+#define USB_VENDOR_ID_IBM 0x04b3
On Tue, May 02, Alan Stern wrote:
Are you certain this patch is responsible for the breakage? That is, did
you build two kernels that differ only in whether or not this patch is
included and compare their behavior? (I don't trust the git-bisect
procedure to do this correctly.)
2.6.15.7
On Wed, May 03, Olaf Hering wrote:
On Tue, May 02, Alan Stern wrote:
Are you certain this patch is responsible for the breakage? That is, did
you build two kernels that differ only in whether or not this patch is
included and compare their behavior? (I don't trust the git-bisect
On Mon, May 01, Alan Stern wrote:
You could try running a 2.6.15 kernel with the clear_halt line removed.
This patch breaks it. I havent tried to put the code back into a 2.6.16 kernel.
.git/BISECT_LOG
git-bisect start
# good: [2b10839e32c4c476e9d94492756bb1a3e1ec4aa8] Linux v2.6.14
On Thu, Nov 17, Alan Stern wrote:
This patch (as605) removes the private udev-serialize semaphore, relying
instead on the locking provided by the embedded struct device's semaphore.
The changes are confined to the core, except that the usb_trylock_device
routine now uses the return
On Wed, Jan 25, Alan Stern wrote:
My earlier experiment (adding a clear-halt for the interrupt-in endpoint)
failed. It turns out that it does cause problems for other devices. And
it wasn't needed anyway; a simple blacklist entry was enough to get my HP
keyboard working.
This patch
On Mon, May 01, Alan Stern wrote:
I originally added the clear_halt just on a hunch. It seemed to help my
HP keyboard, but it caused problems for other people so I removed it
again. It turned out that the blacklist entry was enough to make the HP
keyboard work okay.
I havent looked,
On Mon, Mar 13, Adrian Bunk wrote:
Subject: 2.6.16-rc5-git14 crash in spin_bug on ppc64
References : http://lkml.org/lkml/2006/3/10/190
Submitter : Olaf Hering [EMAIL PROTECTED]
Status : unknown
I have seen it only once, and I rebooted that kernel alot
The warn() macro in include/linux/usb.h adds a newline.
Signed-off-by: Olaf Hering [EMAIL PROTECTED]
drivers/usb/input/hid-core.c |2 +-
1 files changed, 1 insertion(+), 1 deletion(-)
Index: linux-2.6.15-olh/drivers/usb/input/hid-core.c
2.6.15-rc1 doesnt compile for us:
drivers/usb/host/ehci-pci.c:252: error: implicit declaration of function
'usb_suspend_device'
drivers/usb/core/usb.h must be included somehow. Or should we just
disable CONFIG_USB_SUSPEND?
--
short story of a lazy sysadmin:
alias appserv=wotan
On Thu, Aug 18, Greg KH wrote:
On Mon, Aug 15, 2005 at 01:20:42PM +0200, Olaf Hering wrote:
On Mon, Aug 15, Olaf Hering wrote:
I have a keyspan serial adapter and use it to connect to serial console
on other sytems, with speed 9600.
After a while no chars are transmitted
I have a keyspan serial adapter and use it to connect to serial console
on other sytems, with speed 9600.
After a while no chars are transmitted to the other system anymore, but
receive works ok. This happens also with 2.6.5. Any ideas?
usbcore: registered new driver usbserial
On Mon, Aug 15, Olaf Hering wrote:
I have a keyspan serial adapter and use it to connect to serial console
on other sytems, with speed 9600.
After a while no chars are transmitted to the other system anymore, but
receive works ok. This happens also with 2.6.5. Any ideas?
It happens after
changing CONFIG_LOCALVERSION rebuilds too much, for no appearent reason.
remove code for obsolete kernels from drivers/usb/media/pwc/pwc-ctrl.c
and drivers/usb/misc/sisusbvga/sisusb.h
Signed-off-by: Olaf Hering [EMAIL PROTECTED]
drivers/media/dvb/ttusb-dec/ttusb_dec.c |1 -
drivers/usb
changing CONFIG_LOCALVERSION rebuilds too much, for no appearent reason.
use linux/utsname.h to get KERNEL_VERSION macro
Signed-off-by: Olaf Hering [EMAIL PROTECTED]
drivers/usb/media/sn9c102.h |2 +-
1 files changed, 1 insertion(+), 1 deletion(-)
Index: linux-2.6.13-rc2-mm1/drivers/usb
On Wed, Mar 02, Alan Stern wrote:
This is a known bug in the way the SCSI midlayer interacts with the driver
model core. It's not related to usb-storage or the patch you've been
trying out. You can unblock the rmmod process by unplugging the device.
you are right, happens also with the
On Thu, Feb 17, Alan Stern wrote:
On Thu, 17 Feb 2005, Olaf Hering wrote:
On Mon, Feb 14, Alan Stern wrote:
https://lists.one-eyed-alien.net/pipermail/usb-storage/2004-November/001201.html
Alan,
this patch seems to fix the crashes. Is it ready for production use
current libusb uses alot ioctls not listed in compat_ioctl.h.
That makes G5 users very unhappy because the compat layer
rejects these ioctls.
from linux.h:
#define IOCTL_USB_CLAIMINTF _IOR('U', 15, unsigned int)
#define IOCTL_USB_CLEAR_HALT_IOR('U', 21, unsigned int)
#define
On Mon, Feb 28, [EMAIL PROTECTED] wrote:
Hi Pete,
When I connect USB device it gives device information like,
configuration, interface, and endpoint descriptors. I need bus, level,
and port information to map device files to particular USB port. But
this information I can see in
On Thu, Feb 24, Greg KH wrote:
+++ b/drivers/usb/core/hub.c 2005-02-24 11:15:13 -08:00
@@ -1102,23 +1102,31 @@
}
#ifdef DEBUG
-static void show_string(struct usb_device *udev, char *id, int index)
+static void show_string(struct usb_device *udev, char *id, char *string)
+#else
On Thu, Feb 24, Greg KH wrote:
I've changed my mind.
Thanks Greg. Did you catch all usb_string() users for sysfs attributes?
There were a few more than vendor, product and release from my patch.
I wanted to fix it soon, but I was to lazy.
libsysfs seems to read all files, so we are back to
On Thu, Feb 24, Greg KH wrote:
On Thu, Feb 24, 2005 at 08:53:57PM +0100, Olaf Hering wrote:
On Thu, Feb 24, Greg KH wrote:
I've changed my mind.
Thanks Greg. Did you catch all usb_string() users for sysfs attributes?
I sure hope I did, if not, please let me know.
two more
On Mon, Feb 14, Alan Stern wrote:
https://lists.one-eyed-alien.net/pipermail/usb-storage/2004-November/001201.html
Alan,
this patch seems to fix the crashes. Is it ready for production use, or
should I wait for a differnt patch?
---
SF
-by: Olaf Hering [EMAIL PROTECTED]
SuSE Bugzilla Bug 49049 - no recognition of USB-FDD
4Linux version 2.6.8-24.10-default ([EMAIL PROTECTED]) (gcc version 3.3.4
(pre 3.3.5 20040809)) #1 Wed Dec 22 11:54:27 UTC 2004
6usb 1-1: Product: USB Floppy Drive
6usb 1-1: Manufacturer: Sony
6scsi1
On Thu, Feb 17, Alan Stern wrote:
It hasn't been tested very much. (Would you like to be a beta tester? :-)
Lets just throw it at the customers.
---
SF email is sponsored by - The IT Product Guide
Read honest candid reviews on hundreds
On Mon, Feb 14, Alan Stern wrote:
On Mon, 14 Feb 2005, Olaf Hering wrote:
On Thu, Feb 10, Alan Stern wrote:
And Mike Anderson's response was
http://marc.theaimsgroup.com/?l=linux-scsim=110538854224319w=2
His explanation was Currently scsi_host_cancel being called from
On Thu, Feb 10, Alan Stern wrote:
And Mike Anderson's response was
http://marc.theaimsgroup.com/?l=linux-scsim=110538854224319w=2
His explanation was Currently scsi_host_cancel being called from
scsi_remove_host appears to not do anything as scsi_forget_host removes
the devices from the
I see a few refcount handling bugs in the scsi and/or usb layer.
With a vanilla kernel, plugging an usb stick in , and remove it a few
times:
usb 2-1: USB disconnect, address 4
Oops: kernel access of bad area, sig: 11 [#1]
NIP: CDD3E424 LR: CDD05398 SP: C9713F40 REGS: c9713e90 TRAP: 0300Not
On Tue, Feb 08, Greg KH wrote:
It worked once, I could see the pictures. But all you see is the
directory content and you may retrieve small files. There are some small
textfiles which can be viewed.
Ok, so nothing is completly broken, that's good. In a way...
These are gphoto meta
The attached USB cam worked once on a powerbook, but never again. I
always get timeouts. Same timeouts happen on uhci controllers on i386
and x86_64. Any idea what could be tweaked to make it work?
cowberry:~ # cat /proc/bus/usb/devices
T: Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12
On Tue, Feb 08, Greg KH wrote:
On Tue, Feb 08, 2005 at 05:02:08PM +0100, Olaf Hering wrote:
The attached USB cam worked once on a powerbook, but never again. I
always get timeouts. Same timeouts happen on uhci controllers on i386
and x86_64. Any idea what could be tweaked to make
On Tue, Feb 01, Olaf Hering wrote:
On Mon, Jan 31, Phil Dibowitz wrote:
Okay, lets try this again, shall we?
UNUSUAL_DEV( 0x054c, 0x002c, 0x0601, 0x0601,
Sony,
USB Floppy Drive,
US_SC_DEVICE, US_PR_DEVICE, NULL,
US_FL_SINGLE_LUN
On Wed, Feb 02, Alan Stern wrote:
On Wed, 2 Feb 2005, Olaf Hering wrote:
On Wed, Feb 02, Alan Stern wrote:
What do you think of this patch instead? It's far from a perfect
solution, but it ought to prevent the log flooding that you saw.
Should work as well.
I'm glad my
I just managed to permanently toast my testbox by setting
CONFIG_TASK_SIZE=0xC000. Now the box gets either a machine check or
it floods serial console as soon as usb traffic happens.
...
uhci_hcd :00:12.0: host controller process error, something bad happened!
uhci_hcd :00:12.0:
On Wed, Feb 02, Alan Stern wrote:
What do you think of this patch instead? It's far from a perfect
solution, but it ought to prevent the log flooding that you saw.
Should work as well.
I'm glad my box works again after I removed the PCI combo card for a few
reboots. Just removing the power
On Tue, Feb 01, Olaf Hering wrote:
Any idea why an usb-storage device registers sdb twice? Its a 2.6.9rc2
based kernel for SuSE 9.2-x86_64. I havent seen this before, havent
asked if current Linus tree works any better.
T: Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 3
B
I got an USB stick with write protection switch, writing to it did
not work at all. I was told if the blue LED goes on during plugin,
no trouble. But if it remains off, writing gives io errors.
Even reading did not work, like md5sum /mnt/$file gave io errors.
The odd thing, after a few tries I
On Tue, Feb 01, Olaf Hering wrote:
CONFIG_USB_STORAGE_RW_DETECT since a while, we have it enabled.
I just checked, USB_STORAGE_RW_DETECT appears only once in the source.
Cant this be made a module option for usb-storage?
So it can be switched on or off at runtime via sysfs
On Sun, Jan 30, Alan Stern wrote:
On Sat, 29 Jan 2005, Olaf Hering wrote:
I got this toy, which works ok on a G5, but just hangs and times out
with Linux. There are 2 related entries in unusual_devs.h, but no matter
what combination of flags I try, it doesnt work[tm].
Any ideas?
T
I got this toy, which works ok on a G5, but just hangs and times out
with Linux. There are 2 related entries in unusual_devs.h, but no matter
what combination of flags I try, it doesnt work[tm].
Any ideas?
T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2
B: Alloc= 0/900 us (
This floppy needs the multilun flag, like all the other listed Sony
devices. I'm not sure about the Revision tag, how do I handle 6.01? I
dont have the /proc/bus/usb/devices output from the customer.
4Linux version 2.6.8-24.10-default ([EMAIL PROTECTED]) (gcc version 3.3.4
(pre 3.3.5
We just got this toy. But no driver feels responsible for the comm. part?
T: Bus=01 Lev=02 Prnt=03 Port=00 Cnt=01 Dev#= 4 Spd=480 MxCh= 0
D: Ver= 2.00 Cls=02(comm.) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=1631 ProdID=6200 Rev= 0.01
S: Manufacturer=goodway corp usb
S: Product=gwusb2e
S:
On Wed, Jan 19, David Brownell wrote:
Well it's not actually a real COMM class, but you might see if you can
make usbnet use that interface. Bind to vendor + product though.
I will try that. It looks like the network connector, these are the
chips inside:
PL-2301 0428E
PL-2303 0427H
On Wed, Jan 19, David Brownell wrote:
On Wednesday 19 January 2005 11:31 am, Olaf Hering wrote:
On Wed, Jan 19, David Brownell wrote:
Well it's not actually a real COMM class, but you might see if you can
make usbnet use that interface. Bind to vendor + product though.
I
On Thu, Dec 16, Takashi Iwai wrote:
At Tue, 14 Dec 2004 22:11:16 +0100,
Olaf Hering wrote:
Got a soundblaster live 24bit today, it works ok with 2.6.10-rc3.
I got this crash while playing a wav file in a loop.
while true;do aplay /usr/share/sounds/alsa/test.wav;done
The volume
Got a soundblaster live 24bit today, it works ok with 2.6.10-rc3.
I got this crash while playing a wav file in a loop.
while true;do aplay /usr/share/sounds/alsa/test.wav;done
The volume tuner on the box does not work for some reason, it acts also
as mute button. Mute did not react anymore after
On Tue, Oct 19, Alan Stern wrote:
Can you run the tests with a different USB disk drive? Were the tests on
the Intel and PPC machines done using the same drive?
I have tried it on OSX today, copied 8 iso images on the drive,
rebooted, and copied it back to the internal disk.
3 images were
On Tue, Oct 26, David Brownell wrote:
On Tuesday 26 October 2004 05:16, Olaf Hering wrote:
On Tue, Oct 19, Alan Stern wrote:
Can you run the tests with a different USB disk drive? Were the tests on
the Intel and PPC machines done using the same drive?
I have tried it on OSX
On Tue, Oct 19, Alan Stern wrote:
Can you run the tests with a different USB disk drive? Were the tests on
the Intel and PPC machines done using the same drive?
I had a chance to try another drive today, it worked fine.
The mke2fs did not succeed, lots of io errors after 12 hours, I think
On Tue, Oct 19, Alan Stern wrote:
Can you narrow this down to a specific disk sector?
I ran mke2fs -cc over night, its still not finished. It stalls with this
backtrace every once in a while. Same hang happens also with cp.
usb-storage D 0 3034 1 3035 2946
On Tue, Oct 19, Alan Stern wrote:
Can you run the tests with a different USB disk drive? Were the tests on
the Intel and PPC machines done using the same drive?
Its the same drive, just had to verify the corruption.
I will try another disk tomorrow.
--
USB is for mice, FireWire is for men!
On Tue, Oct 19, David Brownell wrote:
If it was a VT6202, those have always made trouble; the VT6212 is
much better. The EHCI 0.95 chips were less consistently implemented
than the EHCI 1.0 ones, and at the very least some VT6202 timings
caused strange things to happen.
Where do I see the
On Tue, Oct 19, David Brownell wrote:
Well that rev 62 EHCI means the chip is before the VT8235 south bridge
which is at rev 82 ... without opening the box, you can at least see if the
driver said EHCI 1.0 or EHCI 0.95. I suspect this is more like 0.95 and
the 6202, than like 1.0 and the
On Thu, Sep 02, David Brownell wrote:
On Thursday 02 September 2004 3:24 pm, Olaf Hering wrote:
Maybe the call chain is something like this:
ehci_irq
spin_lock (ehci-lock)
ehci_work ehci_watchdog
end_unlink_async
qh_completions
I was unable to test this patch, yet.
The device shows 8 LUNs with our 2.6.5 kernel.
T: Bus=01 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 2 Spd=12 MxCh= 0
D: Ver= 1.10 Cls=00(ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=0409 ProdID=0040 Rev= 1.21
S: Manufacturer=NEC
S: Product=NEC USB
On Wed, Sep 22, Alan Stern wrote:
On Wed, 22 Sep 2004, Olaf Hering wrote:
On Wed, Sep 22, Olaf Hering wrote:
On Wed, Sep 08, Alan Stern wrote:
You might try increasing
the delay to 200 us just to see if it changes anything.
that fixed the hang. I will run some
Here is the result from a static kernel.
BOOTP S = 1
FILE: lemon
Load Addr=0x4000 Max Size=0xbfc000
FINAL Packet Count = 3316
FINAL File Size = 1697344 bytes.
chrpboot starting: loaded at 0x0080
gunzipping (0x0001 - 0x00806c4c:0x0098c482)...done 3517428 bytes
49352 bytes of heap
...
usb-storage: Command READ_10 (10 bytes)
usb-storage: 28 00 00 00 00 00 00 00 08 00
usb-storage: Bulk Command S 0x43425355 T 0x3325 L 4096 F 128 Trg 0 LUN 0 CL 10
usb-storage: usb_stor_bulk_transfer_buf: xfer 31 bytes
usb-storage: Status code 0; transferred 31/31
usb-storage: --
On Thu, Sep 02, Olaf Hering wrote:
Sep 2 20:38:59 banana kernel: ehci_hcd 0001:02:0b.2: irq status 0001 INT
Sep 2 20:38:59 banana kernel: ehci_irq(807) dmesg(5121):c1,j4294737421
Sep 2 20:38:59 banana kernel: qh_completions(246) dmesg(5121):c1,j4294737422 enter
cfc5f330
On Thu, Sep 02, David Brownell wrote:
On Thursday 02 September 2004 3:24 pm, Olaf Hering wrote:
Maybe the call chain is something like this:
ehci_irq
spin_lock (ehci-lock)
ehci_work ehci_watchdog
end_unlink_async
qh_completions
On Thu, Sep 02, David Brownell wrote:
On Wednesday 01 September 2004 5:15 am, Olaf Hering wrote:
I wonder, why has the -dummy ehci_qtd struct no initialized list
pointers?
ehci_qtd_init() initializes qtd-qtd_list ... or do you mean
instead why is it not a member of some list?
I
Current Linus tree still doesnt work with this drive, the genesys patch
that went in recently does not help.
Its stuck in partition type scan. Any ideas?
Maybe this 'Illegal Request: Invalid field in cdb' is the reason for the
failure?
T: Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 3 Spd=480
On Fri, Sep 03, David Brownell wrote:
On Friday 03 September 2004 5:00 am, Olaf Hering wrote:
On Thu, Sep 02, David Brownell wrote:
Can you try this patch? Ideally the entire first scan
would be aborted and the second scan started.
But it's a lot simpler to just not start
On Wed, Sep 01, Olaf Hering wrote:
I tried this patch, it leads to a hard crash after 1 minute.
Very strange...
--- ./drivers/usb/host/ehci-q.c.kaputt2004-08-31 14:21:51.794068000 +0200
+++ ./drivers/usb/host/ehci-q.c 2004-09-01 14:17:10.732679974 +0200
@@ -857,7 +857,7
It dereferences an already freed struct list_head after a few minutes.
I will try to reproduce it on a dual G5.
unmodified 2.6.9-rc1-bk9 dies after a few seconds on the G5.
I wonder, what protects the list operations in qh_completions()? Its
called from a few places, but I dont see much
On Thu, Sep 02, David Brownell wrote:
On Thursday 02 September 2004 11:06 am, Olaf Hering wrote:
It dereferences an already freed struct list_head after a few minutes.
I will try to reproduce it on a dual G5.
unmodified 2.6.9-rc1-bk9 dies after a few seconds on the G5.
I wonder
On Thu, Sep 02, David Brownell wrote:
On Thursday 02 September 2004 12:30 pm, Olaf Hering wrote:
Here is a little debug output attached, generated with this patch.
It shows that qh 0xcfca0140 is passed to qh_completions on both
cpus.
Well now, that'd be evil. Maybe
On Thu, Sep 02, David Brownell wrote:
On Thursday 02 September 2004 1:27 pm, Olaf Hering wrote:
On Thu, Sep 02, David Brownell wrote:
On Thursday 02 September 2004 12:30 pm, Olaf Hering wrote:
Here is a little debug output attached, generated with this patch.
It shows
On Thu, Aug 12, David Brownell wrote:
On Thursday 12 August 2004 4:26 am, Olaf Hering wrote:
On Tue, Jun 15, David Brownell wrote:
Richard Curnow wrote:
One problem I'm hitting is in EHCI, I was wondering if you had any ideas
as to what I could start looking at, annotating
On Thu, Aug 12, David Brownell wrote:
On Thursday 12 August 2004 4:26 am, Olaf Hering wrote:
On Tue, Jun 15, David Brownell wrote:
Richard Curnow wrote:
One problem I'm hitting is in EHCI, I was wondering if you had any ideas
as to what I could start looking at, annotating
On Tue, Jun 15, David Brownell wrote:
Richard Curnow wrote:
One problem I'm hitting is in EHCI, I was wondering if you had any ideas
as to what I could start looking at, annotating etc to debug this. The
problem seems to be here:
static inline void list_del(struct list_head *entry)
{
On Tue, Jul 13, David Brownell wrote:
Instead, how about: (a) longer timeout, 5 seconds to match OHCI's
absurdly long default there; (b) change that handoff failed message
to add continuing anyway; and (c) return 0 as you do, which I'm
expecting is the key part of that patch.
This patch
On Tue, Jul 13, Al Borchers wrote:
Olaf --
Olaf Hering wrote:
Thanks Al!. Works perfectly, even with agetty.
Good news! Thanks for testing it.
Greg, would you accept this patch? It is the
same code we use in the io_ti driver and similar
to the gadget serial code.
I guess
On Mon, Jul 12, Al Borchers wrote:
Olaf --
Olaf Hering wrote:
Hmm, I'm not sure how to translate that to LANG=diff
Here is one such translation--a patch to 2.6.7 to add a
circular buffer to the pl2303 USB serial driver.
I tested it briefly and it solved the dropped newline
problem
On Tue, Jun 15, David Brownell wrote:
[EMAIL PROTECTED] wrote:
Stuart Hayes here at Dell has identified this or/and mix-up in the
ehci-hcd driver. Because of this, ehci-hcd is not properly released by
BIOSes supporting full 2.0 and port behavior can then become erratic.
Good patch, it
On Sun, Jul 11, Luca Risolia wrote:
This single patch contains some updates and cleanups for
the W996[87]CF driver and a new experimental V4L2 driver
for SONiX SN9C10[12] PC Camera Controllers connected to various
image sensors. I have not divided the patch in two logical
sub-patches
On Wed, Jul 07, Greg KH wrote:
On Wed, Jul 07, 2004 at 02:01:04PM +0200, Olaf Hering wrote:
The keyspan_pda driver locks up on a G4 and an ibook G4 when it
transmits data. This happens with our sles9 kernel, which has the 2.6.6
usb stack, and with current 2.6.7-mm6.
Can you use
On Wed, Jul 07, Greg KH wrote:
On Wed, Jul 07, 2004 at 02:01:04PM +0200, Olaf Hering wrote:
The keyspan_pda driver locks up on a G4 and an ibook G4 when it
transmits data. This happens with our sles9 kernel, which has the 2.6.6
usb stack, and with current 2.6.7-mm6.
Can you use
Greg,
is there a reason why the USB_SERIAL_DEBUG option depends on static
USB_SERIAL? This patch works for me.
diff -purN linux-2.6.7/drivers/usb/serial/Kconfig
linux-2.6.7.usbserial-debug/drivers/usb/serial/Kconfig
--- linux-2.6.7/drivers/usb/serial/Kconfig 2004-06-16
Greg,
can you help with this one? I have the keyspan working now, and its
directly connected to a PL2303 adapter on the same box.
writing to the PL2303 and reading from the keyspan leads to garbage
output. Sometimes the newline is repeated to fill the dd blocksize,
somethings I get the 'foo'
On Thu, Jul 08, Al Borchers wrote:
Olaf --
Olaf Hering wrote:
I have the keyspan working now, and its
directly connected to a PL2303 adapter on the same box.
writing to the PL2303 and reading from the keyspan leads to garbage
output. Sometimes the newline is repeated to fill the dd
f178:~ # lsusb
Bus 004 Device 001: ID :
Bus 003 Device 003: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port
Bus 003 Device 001: ID :
Bus 002 Device 004: ID 06cd:0104 Keyspan PDA [prerenum]
Bus 002 Device 001: ID :
Bus 001 Device 001: ID :
f178:~ #
On Thu, Jul 08, Greg KH wrote:
Ah, nice, I missed that when changing the port structures around. Does
this fix the problem for you?
yes, no lockups anymore.
--
USB is for mice, FireWire is for men!
sUse lINUX ag, nRNBERG
---
This
I pulled Linus 2.6.7-bk17 into Gregs usb-2.6 tree. It works ok on 2
different ibook G3, but hangs on an ibook G4. Havent tried other
machines yet.
Any idea what patch can cause this?
...
ohci_hcd 0001:01:1b.1: new USB bus registered, assigned bus number 3
hub 3-0:1.0: USB hub found
hub 3-0:1.0:
On Mon, Jul 05, Olaf Hering wrote:
I pulled Linus 2.6.7-bk17 into Gregs usb-2.6 tree. It works ok on 2
different ibook G3, but hangs on an ibook G4. Havent tried other
machines yet.
Any idea what patch can cause this?
...
ohci_hcd 0001:01:1b.1: new USB bus registered, assigned bus
On Sun, May 30, Vojtech Pavlik wrote:
On Sun, May 30, 2004 at 02:52:27PM -0400, Alan Stern wrote:
On Sun, 30 May 2004, Vojtech Pavlik wrote:
Okay, so can we all agree on this one?
I don't know if it's really needed, but for consistency you might want to
make a similar change
On Thu, Jun 03, Oliver Neukum wrote:
Am Donnerstag, 3. Juni 2004 18:39 schrieb Olaf Hering:
This patch causes deadlocks if you unplug and replug an usb-storage
device.
Only on replug?
yes. plug the usbstick in, reboot, everything works ok. unplug, still
ok, replug, threads hang in D
On Fri, May 14, Greg KH wrote:
drivers/usb/misc/cytherm.c |9
current Linus tree does not compile:
CC [M] drivers/usb/misc/cytherm.o
drivers/usb/misc/cytherm.c: In function `set_brightness':
drivers/usb/misc/cytherm.c:122: error: `led' undeclared (first use in this
unplugging an usb keyboard leads to this oops with Gregs usb-2.6 tree,
from a few days ago. The changes from yesterday will probably not fix it.
This is a Thinkpad T40p.
usb 2-2: new low speed USB device using address 2
usbcore: registered new driver hiddev
input: USB HID v1.00 Keyboard [IBM
1 - 100 of 168 matches
Mail list logo
