On Sat, May 25, 2002 at 01:00:28AM +0200, Georg Acher wrote:
> Hm, can't see that there is any change in the usb-uhci root hub code but a
> lot in the general hub code, so the problem seems IMO more likely there ;-)
> The eax-register contains a value that looks like a part of an ASCII string
> ("
On Fri, May 24, 2002 at 10:19:07AM -0400, Stuffed Crust wrote:
<...>
> 1) Device plugged in on bootup.
> a) Without the device reset, the device does not initialize properly,
> and unplugging/replugging is necessary.
> b) With the device reset in the driver, on a KT266 (usb-uhci) the
>
Hi!
Regarding USB initialization bug - is there anybody there who has
problems with newest 19-pre or stock (not red hat) 2.4.18 kernel ?
BR,
Jacek
___
Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in
On Fri, May 24, 2002 at 02:04:40PM -0400, Johannes Erdfelt wrote:
> Just to clarify, uhci-alt worked in every case, but usb-uhci would oops
> when resetting the device plugged into the root hub?
In every case I tried, yes. 'uhci' worked fine, while 'usb-uhci' oopsed
on some platforms when plugge
On Fri, May 24, 2002, Stuffed Crust <[EMAIL PROTECTED]> wrote:
> I've been doing a lot of work recently on the linux-wlan-ng prism2.5 USB
> driver, and I've finally reached the pointw here I have to break down
> and ask for help from someone more familiar with the USB way of things.
>
> Basically
I've been doing a lot of work recently on the linux-wlan-ng prism2.5 USB
driver, and I've finally reached the pointw here I have to break down
and ask for help from someone more familiar with the USB way of things.
Basically, thanks to firmware bugs in the hardware, it's often necessary
to reset
