From: David Brownell <david-b@pacbell.net>
To: Pete Zaitcev <zaitcev@redhat.com>
Cc: linux-usb-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [linux-usb-devel] Patch for usb-ohci in 2.4 needs review & testing
Date: Mon, 12 May 2003 09:19:48 -0700 [thread overview]
Message-ID: <3EBFC9A4.7020708@pacbell.net> (raw)
In-Reply-To: 20030510004012.A26322@devserv.devel.redhat.com
Hi Pete,
> The attached patch appears to fix a bug which was really making
> my life difficult: dd if=/dev/scd0 produces corrupted ISOs when
> reading off a USB CD-ROM on a box with no less than 2 P4 CPUs,
> HyperThreading and ServerWorks chipset. However, I'm not
> completely sure that I didn't break something.
Did the "ohci-hcd" backport give the same problem?
Or did you not try that?
That 2.5 code has had a lot more attention paid to it
with respect to locking and similar less-common problems.
Personally I'd rather see that version get the attention,
so both 2.4 and 2.5 get the benefits, although I can also
understand wanting changes that seem more incremental.
> - The whole idea of checking jiffy-sized timeouts from an interrupt
> is revolting, but I am wary of unknown here, so I didn't kill it.
> If anyone knows how that abomination came to life, I'll be glad
> to know too.
It shouldn't actually be alive ... never enabled,
because never debugged (and submitted by accident).
Safe IMO to remove completely.
In fact the last time the issue of HCD-enforced
timeouts came up, nobody had anything positive
to say about it. No portable driver has ever
been able to rely on it. What's been lacking is
the will to rip all such code out; in 2.5 only
"uhci-hcd" has any such code left.
- Dave
next prev parent reply other threads:[~2003-05-12 15:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-10 4:40 Patch for usb-ohci in 2.4 needs review & testing Pete Zaitcev
2003-05-12 16:19 ` David Brownell [this message]
2003-05-12 18:48 ` [linux-usb-devel] " Pete Zaitcev
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=3EBFC9A4.7020708@pacbell.net \
--to=david-b@pacbell.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=zaitcev@redhat.com \
/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