mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: "Kevin P. Fleming" <kevin@labsysgrp.com>,
	linux-usb-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org
Subject: Re: [linux-usb-devel] [PATCH] current state of the 2.5.1 USB tree
Date: Thu, 27 Dec 2001 21:40:25 -0800	[thread overview]
Message-ID: <009901c18f62$2723a920$6800000a@brownell.org> (raw)
In-Reply-To: <20011219104253.A11032@kroah.com> <061101c18f35$5e141e60$6800000a@brownell.org> <008a01c18f48$beaa3e90$6caaa8c0@kevin>

> Yes, I would very much like to see EHCI support in a 2.4.x compatible form,
> even if it's not in the mainline kernel. Last time I tried the CVS code, I
> couldn't even get it compile, but maybe things have improved since then (two
> months ago) :-)

I'm surprised you had problems even then, but for a while you
needed a 2.4ac kernel.  Those usbcore changes merged
into Linus' tree at about 2.4.10 and I know folk used that OK.

What was your build problem?  I was going to suggest "try the
CVS ref24 tag", but somehow it's missing most of EHCI (odd).
I'd expect the 1-December code to behave on recent 2.4.x
systems; I certainly used it on 2.4.15 ...

Looks like the best solution is for me to try to build some patch.
It won't be as current as what the 2.5 USB tree has, but maybe the
only major issue can be lack of transaction translator (hub) support.


> I also have a USB 2.0 external hard drive that I'd sure like to see run at
> something higher than 1 megabyte per second <G>

Quite doable ... that was the first device I got working, and it was
a treat to get a dozen times faster than that!  (One person benched
a single drive at over 22 MByte/sec on a 2.4.5/PPC box, one that
I think doesn't have a very fast CPU.)  For now it'll only work on 2.4
since the bio/scsi changes appear to have confused usb-storage.

Also 22 MByte/sec needs smarter scatter/gather I/O in usb-storage,
or making sure SCSI delivers physically contiguous buffers (no I
don't think that one's very realistic :).

- Dave




      reply	other threads:[~2001-12-28  5:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-19 18:42 Greg KH
2001-12-19 20:01 ` [PATCH] current state of the 2.4.17-rc2 " Greg KH
2001-12-27 23:22 ` [linux-usb-devel] [PATCH] current state of the 2.5.1 " David Brownell
2001-12-28  2:38   ` Kevin P. Fleming
2001-12-28  5:40     ` David Brownell [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='009901c18f62$2723a920$6800000a@brownell.org' \
    --to=david-b@pacbell.net \
    --cc=kevin@labsysgrp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    /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

all inboxes | Powered by JetHome®