Hello.
I run Linux kernel 2.6.6 and have an ohci_hcd controller (nVidia). I
just plugged in a USB joystick (which I suspect should be fully
supported by the usbhid driver). The usbhid driver does not detect the
joystick when it is loaded. I notice these messages in dmesg that
occur when the
On Sat, May 29, 2004 at 07:47:55AM -0700, Greg KH wrote:
> On Sat, May 29, 2004 at 04:13:24PM +0200, Vojtech Pavlik wrote:
> > On Sat, May 29, 2004 at 03:23:09PM +0200, Oliver Neukum wrote:
> >
> > > > Here I have this patch ported from a 2.4 verison of a patch by guy at
> > > > Dell ([EMAIL PROTE
On Fri, May 28, 2004 at 09:09:28PM -0700, David Brownell wrote:
>
> Please use 2.6.7-rc1 as I requested.
All right. Here are results from 2.6.7-rc1. Not that they differ
very much from what I posted before.
> cd /sys/class/usb_host/usb4
> cat registers
bus pci, device :00:1d.7
On Sun, 30 May 2004, Tomasz Motylewski wrote:
> > If you want, you can try applying the patch below to 2.6.6 or 2.6.7. It
> > changes the existing code to look for a short CSW rather than a 0-length
> > CSW. I don't think it's as safe as the existing code, but if it helps
> > people we'll try to
> If you want, you can try applying the patch below to 2.6.6 or 2.6.7. It
> changes the existing code to look for a short CSW rather than a 0-length
> CSW. I don't think it's as safe as the existing code, but if it helps
> people we'll try to put it in. Judging by other people's logs, though,
>
On Sat, May 29, 2004 at 03:49:24PM -0400, Alan Stern wrote:
> Granted that's so, it doesn't mean we need to use ->serialize. And if we
> do, the parts of usbcore that could send messages to ep0 (probably just
> the usbfs and sysfs routines) will have to be changed to lock the device.
I don't know
On Sat, 29 May 2004, Oliver Neukum wrote:
> Am Samstag, 29. Mai 2004 17:23 schrieb Alan Stern:
> > However, there's a definite disadvantage to using dev->serialize for this
> > purpose: It can delay khubd and disconnect notifications. usb-storage
> > can wait for fairly long periods, 20 or 30 sec
On Sat, May 29, 2004 at 02:51:48PM -0400, Alan Stern wrote:
> On Sat, 29 May 2004, Jens Axboe wrote:
>
> > > > Both 2.6.7-rc1 and BK current spit out a bunch of:
> > > >
> > > > drivers/usb/class/usblp.c: usblp1: nonzero read/write bulk status received: -2
> > > > drivers/usb/class/usblp.c: usblp
On Sat, 29 May 2004, Tomasz Motylewski wrote:
>
> On Wed, 26 May 2004, Alan Stern wrote:
> > On Wed, 26 May 2004, Tomasz Motylewski wrote:
> > > I would like to ask first whether there is some reliable, recommended
> > > workaround to get writing to such USB/IDE disks? Reading goes very well with
Am Samstag, 29. Mai 2004 17:23 schrieb Alan Stern:
> However, there's a definite disadvantage to using dev->serialize for this
> purpose: It can delay khubd and disconnect notifications. usb-storage
> can wait for fairly long periods, 20 or 30 seconds sometimes. If it holds
> the serialize semaph
On Sat, 29 May 2004, Jens Axboe wrote:
> Sure. Ok, so now it appears to work with bk-current (I re-applied the
> patch) and usb debugging enabled. Here's the output from dmesg after the
> boot, scanning/printing works.
Your log looks normal, at a quick glance. Don't you just love these
problems
On Sat, 29 May 2004, Jens Axboe wrote:
> > > Both 2.6.7-rc1 and BK current spit out a bunch of:
> > >
> > > drivers/usb/class/usblp.c: usblp1: nonzero read/write bulk status received: -2
> > > drivers/usb/class/usblp.c: usblp1: error -2 reading from printer
> > > drivers/usb/class/usblp.c: usblp1
tong changda wrote:
How to debug such kind of problem?
In this case, the RNDIS spec says the device descriptor
needs to say it's a communications class device. So the
attached patch should make that part work much better.
This is almost a PXA-specific issue, since it's the most
widely used chip
On Wed, 26 May 2004, Alan Stern wrote:
> On Wed, 26 May 2004, Tomasz Motylewski wrote:
> > I would like to ask first whether there is some reliable, recommended
> > workaround to get writing to such USB/IDE disks? Reading goes very well with a
> > speed over 30 MB/s. ID: 05e3:0702
> > EHCI control
On Sat, May 29 2004, Alan Stern wrote:
> [Moved to linux-usb-devel rather than linux-kernel]
>
> On Sat, 29 May 2004, Jens Axboe wrote:
>
> > On Sat, May 29 2004, Greg KH wrote:
> > >
> > > Alan, looks like your "fix the VIA controller driver" patch broke
> > > something here, care to look into
[Moved to linux-usb-devel rather than linux-kernel]
On Sat, 29 May 2004, Jens Axboe wrote:
> On Sat, May 29 2004, Greg KH wrote:
> >
> > Alan, looks like your "fix the VIA controller driver" patch broke
> > something here, care to look into it?
>
> Thanks for the hint, backing out this patch:
>
On Fri, 28 May 2004, Stephen Hemminger wrote:
> Here is a successful hot sync, followed by an unsuccessful attempt
> to start the MS import program... The program starts, just the
> Linux side doesn't get to setting up the disk device.
> uhci_hcd :00:1f.2: port 1 portsc 0093
> hub 1-0:1.0:
On Sat, 29 May 2004, Vojtech Pavlik wrote:
> On Sat, May 29, 2004 at 03:23:09PM +0200, Oliver Neukum wrote:
>
> > > Here I have this patch ported from a 2.4 verison of a patch by guy at
> > > Dell ([EMAIL PROTECTED]), that uses the serialize semaphore in devio.c
> > > and in usb-storage.
> > >
>
On Sat, May 29, 2004 at 04:13:24PM +0200, Vojtech Pavlik wrote:
> On Sat, May 29, 2004 at 03:23:09PM +0200, Oliver Neukum wrote:
>
> > > Here I have this patch ported from a 2.4 verison of a patch by guy at
> > > Dell ([EMAIL PROTECTED]), that uses the serialize semaphore in devio.c
> > > and in u
Am Samstag, 29. Mai 2004 16:13 schrieb Vojtech Pavlik:
> On Sat, May 29, 2004 at 03:23:09PM +0200, Oliver Neukum wrote:
>
> > > Here I have this patch ported from a 2.4 verison of a patch by guy at
> > > Dell ([EMAIL PROTECTED]), that uses the serialize semaphore in devio.c
> > > and in usb-storag
On Sat, May 29, 2004 at 03:23:09PM +0200, Oliver Neukum wrote:
> > Here I have this patch ported from a 2.4 verison of a patch by guy at
> > Dell ([EMAIL PROTECTED]), that uses the serialize semaphore in devio.c
> > and in usb-storage.
> >
> > This is needed on storage devices, where even sending
Am Samstag, 29. Mai 2004 09:21 schrieb Vojtech Pavlik:
> Hi!
>
> Here I have this patch ported from a 2.4 verison of a patch by guy at
> Dell ([EMAIL PROTECTED]), that uses the serialize semaphore in devio.c
> and in usb-storage.
>
> This is needed on storage devices, where even sending a harmles
After doing some tracing:
lubbock only receive get_descriptor request (including get
device,configurator,string,endpoint), And it seems lubbock return the right
configurator as followed:
But the Windows never did a set configuration operation,Seem something was
wrong?
The configurator that lubb
Hi!
Here I have this patch ported from a 2.4 verison of a patch by guy at
Dell ([EMAIL PROTECTED]), that uses the serialize semaphore in devio.c
and in usb-storage.
This is needed on storage devices, where even sending a harmless
GET_DESCRIPTOR command at the wrong time will lead to a STALL condi
24 matches
Mail list logo
