Alan Stern wrote:
On Sat, 27 Dec 2003, David Brownell wrote:
Yes, a bug! I fixed it in the updated patch which I've attached;
it applies cleanly to Greg's current usb-devel-2.6 BK.
[ Split out patches will coming out too, in dribs and drabs. ]
Okay. I won't have time to look at the updated pa
Martin MOKREJ© wrote:
When trying "ifconfig usb0 IP-address", I get in syslog:
...
usb0: register usbnet at usb-:00:1d.0-2, Prolific PL-2301/PL-2302
usb0: open reset fail (-32) usbnet usb-:00:1d.0-2, Prolific PL-2301/PL-2302
I think the right answer is just a patch to ignore open reset fai
On Sat, 27 Dec 2003, David Brownell wrote:
> Yes, a bug! I fixed it in the updated patch which I've attached;
> it applies cleanly to Greg's current usb-devel-2.6 BK.
>
> [ Split out patches will coming out too, in dribs and drabs. ]
Okay. I won't have time to look at the updated patch for a l
Greg:
Here's a policy question for you.
Apparently some devices put extra garbage at the end of their
configuration information. For the particular device considered here,
there's a device descriptor followed by an illegal length-1 descriptor.
(Note that configuration information should never
Rogério:
>From the log you collected, it's clear that Windows initializes each port
of your internal hub twice! Don't ask me why. Maybe that's what the
Linux driver needs to do.
Anyway, let's start off small. Here's a diagnostic patch for you to try.
This won't fix anything, but it will prin
[EMAIL PROTECTED] wrote:
Hi, David,
Thank you so much for your response.
I am not quite understand what you mean by "It's safe to leave that
BIOS feature enabled, unless your BIOS is buggy in that area, since
Linux turns it off later if you start up the "native" USB.".
Linux should know how to
Stavros Markou wrote:
Hi,
I have sent approximately two months ago mails about the problems
concerning resetting a usb device and I was pointed to
usb_physical_reset_device. Then I saw that this function was never
exported as others like usb_reset_device or declared at .
I noticed that too. A
On Sun, 2003-12-28 at 10:38, Alan Stern wrote:
> It certainly sounds like your device puts some extra garbage in its
> descriptors.
I think you're right. After the USB_DT_DEVICE descriptor is the
descriptor of length 1. Then there is nothing else.
> Try this patch. Instead of returning an err
On Sat, 27 Dec 2003, Ashley Reed wrote:
> If I just commented out "header->bDescriptorType == USB_DT_DEVICE", then
> it would fail with the warning "invalid descriptor of length 1". That's
> why I removed the check for the descriptor being less than 2 bytes. I
> don't know anything about the USB
On Sat, 2003-12-27 at 22:39, Alan Stern wrote:
> On Sat, 27 Dec 2003, Johannes Erdfelt wrote:
> > Complain to the manufacturer? If the descriptor really is less than 2
> > bytes, then it certainly is invalid.
>
> The error message complained not about the descriptor length but about its
> type.
I
Hi,
On Sat, Dec 27, 2003 at 07:24:11PM +0200, Petko Manolov wrote:
> Hi there,
>
> On Fri, 26 Dec 2003, Dimitri Torfs wrote:
>
> > "Chip" identification of the pegasus driver does not work correctly on
> > big endian machines, resulting in incorrect packet lengths for
> > received
On Sat, 27 Dec 2003, Anders Karlsson wrote:
> Dec 27 17:44:14 oden kernel: usb-storage: This device (03ee,6901,0100 S
> 04 P 00) has unneeded SubClass and Protocol entries in unusual_devs.h
> Dec 27 17:44:14 oden kernel:Please send a copy of this message to
> <[EMAIL PROTECTED]>
Thanks for se
On Sat, 27 Dec 2003, Johannes Erdfelt wrote:
> On Sat, Dec 27, 2003, Ashley Reed <[EMAIL PROTECTED]> wrote:
> > I have an AxisPad game controller from WalMart. The USB driver
> > identifies it as "USB HID v1.00 Gamepad [ANKO Corp. Gemini Industries
> > Inc. ]". The game pad doesn't work in any k
13 matches
Mail list logo
