On Sun, Feb 24, 2002 at 12:39:15AM -0600, Dan Hopper wrote:
>
> The reason I'd like to switch back to usb-uhci instead of uhci is
> twfold: Vmware seems to want to only use usb-uhci and not uhci
> (dummies!). And uhci seems to be unable to get the scanner going
> such that it doesn't "stutter"
Greg KH <[EMAIL PROTECTED]> remarked:
> These patches will not apply for the 2.4 tree, even if you tried :)
>
> What problems are you having with 2.4.18-rc1 and previous? Any oops
> messages?
Hi,
Well, basically if I use usb-uhci instead of uhci, the computer
locks during the shutdown process.
On Sat, Feb 23, 2002 at 08:54:11PM -0600, Dan Hopper wrote:
>
> I wonder if anyone might look at doing the same sort of fix to
> the 2.4.18 working tree? I experience the same sort of behavior
> with usb-uhci on my KT266A board (VT82C586B USB) on 2.4.18-rc1 (and
> previous 2.4.x kernels, too).
Greg KH <[EMAIL PROTECTED]> remarked:
>
> On Fri, Feb 15, 2002 at 10:22:05AM -0800, Patrick Mochel wrote:
> >
> > On Fri, 15 Feb 2002, Patrick Mochel wrote:
> >
> > >
> > > > no, it doesn't solve the problem. i would like to test it whith
> > > > preemtible kernel not set but it doesn't boot.
I thought the first suggestion here made the most sense,
allowing you to change the size of the URB buffer.
I agree that a new function is the best way to do this (as
opposed to allowing people to change the size themselves
directly in the urb and picking up the change on resubmission)
for the fo
On Sat, Feb 23, 2002 at 07:17:58PM +0530, Phani Ram wrote:
>
> hi,
> While trying isochronous data over bluetooth , i am getting the following
> message on the sending side.
> The kernel version is 2.4.14.
>
> usb-uhci >In function process_iso( )
>
> usb-uhci: process_iso: 0: len :49
hi,
While trying isochronous data over bluetooth , i am getting the following
message on the sending side.
The kernel version is 2.4.14.
usb-uhci >In function process_iso( )
usb-uhci: process_iso: 0: len :49 0230 status 0
usb-uhci: process_iso: 1: len :49 0230 status 0
