From: David Brownell <david-b@pacbell.net>
To: linux-kernel@vger.kernel.org
Subject: 2.4.20-pre7 USB 2.0 "ehci-hcd" patches
Date: Fri, 13 Sep 2002 16:20:05 -0700 [thread overview]
Message-ID: <3D8272A5.5030405@pacbell.net> (raw)
I thought I'd send the note here as well as to the Linux-USB list.
Either because I thought the exposure to more folk that may have
shiny new hardware could be useful, or because I'm a glutton for
punishment ... I'm not sure yet.
The two patches are archived, such as
http://marc.theaimsgroup.com/?l=linux-usb-devel&m=103195770819572&w=2
http://marc.theaimsgroup.com/?l=linux-usb-devel&m=103195884620392&w=2
I won't see LKML followups unless you cc me, but I'll see posts
on the USB developer's list.
- Dave
-------- Original Message --------
Subject: [linux-usb-devel] [PATCH 2.4.20-pre7 0 of 2] EHCI updates
Date: Fri, 13 Sep 2002 15:51:11 -0700
From: David Brownell <david-b@pacbell.net>
To: linux-usb-devel@lists.sourceforge.net
I'm sending a couple of EHCI related patches out for folk who'd
like to try this on top of 2.4.20-pre7.
I'd like to see if anyone has any feedback about it before taking
the next steps to get it into 2.4.20 ... there are improvements,
but likely some problems could still stand to get fixed.
If you're using EHCI hardware, please try the patches. Especially if:
- You've had problems before; CardBus should work, and there were
a bunch of bugfixes too.
- You're not using a NEC host controller: Intel (ICH4), VIA
(VT6202, VT8235), SIS (962, 963), NForce2, and so on. If you
have a newish motherboard, it may well have USB 2.0 built in.
- You want to use USB 1.1 interrupt transactions through USB 2.0
hubs, such as for many HID devices, some Ethernet adapters, some
disks, and so on.
The first patch does some minor updates to usbcore, which happens
to break the current 2.4.20-pre7 ehci-hcd code.
The second patch brings ehci-hcd up to the 2.5.34bk4 level, and
relies on that first patch.
- Dave
reply other threads:[~2002-09-13 23:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3D8272A5.5030405@pacbell.net \
--to=david-b@pacbell.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox