From: "Benjamin Herrenschmidt" <benh@kernel.crashing.org>
To: "Robert E Brose II" <bob@kunk.jriver.com>,
"Tony Howard" <tahoward@ntrnet.net>
Cc: <linuxppc-dev@lists.linuxppc.org>
Subject: Re: cdrecord, cdrdao failing with scsi bus reset
Date: Sat, 21 Sep 2002 13:55:13 +0200 [thread overview]
Message-ID: <20020921115514.20288@192.168.4.1> (raw)
In-Reply-To: <20020921052807.20546.qmail@kunk.jriver.com>
>I got it off of this list myself, I think it was originally for
>2.4.3. I've just kept remaking it as I put new kernels on
>my machine as it seems to never have made it to the official
>kernel. It patches several scsi drivers but the only ones that
>affect Mac users are the 53c94 and mesh drivers.
>
>http://www.jriver.com/~bob/daofix-2.4.17.diff
>
>Is against the 2.4.17 kernel. I just tried it on the latest
>benh 2.4 kernel (2.4.20-pre7) and it patched ALTHOUGH there
>were offsets in the mesh driver which seems to have been worked
>on lately. I haven't verified that it works past the 2.4.19
>kernel I'm currently using. YMMV.
Interesting. I don't think this patch does things the right
way though, but I'll see what I can do with it.
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-09-21 11:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20020920200528.14119.qmail@kunk.jriver.com>
2002-09-20 20:21 ` cdrecord, cdrdao failing with scsi bus reset Robert E Brose II
2002-09-20 4:12 ` Tony Howard
2002-09-21 5:28 ` Robert E Brose II
2002-09-21 11:55 ` Benjamin Herrenschmidt [this message]
2002-09-24 16:26 ` Tony Howard
[not found] <20020921142023.24406.qmail@kunk.jriver.com>
2002-09-21 14:27 ` Robert E Brose II
2002-09-03 12:03 /proc file system not working Sanjeev Manral
2002-09-09 19:16 ` cdrecord, cdrdao failing with scsi bus reset Tony Howard
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=20020921115514.20288@192.168.4.1 \
--to=benh@kernel.crashing.org \
--cc=bob@kunk.jriver.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=tahoward@ntrnet.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;
as well as URLs for NNTP newsgroup(s).