From: Greg KH <greg@kroah.com>
To: John Mock <kd6pag@qsl.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: USB driver troubles: OHCI vs. UHCI
Date: Tue, 2 Mar 2004 19:27:37 -0800 [thread overview]
Message-ID: <20040303032737.GA16680@kroah.com> (raw)
In-Reply-To: <E1AyM9d-00022O-00@penngrove.fdns.net>
On Tue, Mar 02, 2004 at 06:30:37PM -0800, John Mock wrote:
> I've been using a homebrew USB driver for a PIC microprocessor development
> board (Microchip PICkit, which uses the HID 'knothole'), based the 2.4.21
> USB skeleton driver (with a few minor changes) for many months now on a
> PowerMac 8500 with an add-on OHCI board. I tried compiling for a Sony
> VAIO R505EL, which uses the UHCI driver, with poor results.
>
> Under 2.4.22, it works the first time the device is opened, but hangs on
> subsequent operations until the device is power cycled or the UHCI driver
> is module is removed/re-installed again.
Sounds like a problem with your driver.
> I tried updating it to 2.6.1-rc2 and it quickly gets an error, saying
>
> [skel]_write - failed submitting write urb, error -22.
>
> Thinking i had messed up the driver, i generated a current kernel (2.6.3)
> on the PowerMac, and the updated driver worked the first time with the
> OHCI board.
>
> Is this a known problem with 2.6.xx, and if so, what does it mean??
No it isn't.
> Any idea what the skeleton driver isn't doing under 2.4.2x which causes
> a device to enter a hung state on subsequent opens on UCHI (but not OHCI)?
>
> As of a few minutes ago, i have a workaround. But i'm still quite puzzled
> and hope someone else has been here before.
Care to post the driver?
thanks,
greg k-h
prev parent reply other threads:[~2004-03-03 3:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-03 2:30 USB driver troubles: OHCI vs. UHCI John Mock
2004-03-03 3:27 ` Greg KH [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040303032737.GA16680@kroah.com \
--to=greg@kroah.com \
--cc=kd6pag@qsl.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.