From: Pete Zaitcev <zaitcev@redhat.com>
To: David Brownell <david-b@pacbell.net>
Cc: Pete Zaitcev <zaitcev@redhat.com>,
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 14:48:55 -0400 [thread overview]
Message-ID: <20030512144855.A2256@devserv.devel.redhat.com> (raw)
In-Reply-To: <3EBFC9A4.7020708@pacbell.net>; from david-b@pacbell.net on Mon, May 12, 2003 at 09:19:48AM -0700
> From: David Brownell <david-b@pacbell.net>
> Date: Mon, 12 May 2003 09:19:48 -0700
> > 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.
Greg sent me that, but I haven't tried it yet. Sorry.
Obviously, ohci-hcd is better, but you know where I work.
We have to support ancient codebases practically forever,
despite what press says. The ohci fix we talk about comes
from qualifying 2.4.9 on top of the line hardware, some of
which is not released yet.
> > - 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.
Heh. I'm afraid I won't be able to touch it, see above.
I'll look on the ohci-hcd, but certain events may be pushing
it to next week.
-- Pete
prev parent reply other threads:[~2003-05-12 18:36 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 ` [linux-usb-devel] " David Brownell
2003-05-12 18:48 ` Pete Zaitcev [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=20030512144855.A2256@devserv.devel.redhat.com \
--to=zaitcev@redhat.com \
--cc=david-b@pacbell.net \
--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