From: Rene Herman <rene.herman@keyaccess.nl>
To: viro@parcelfarce.linux.theplanet.co.uk
Cc: Linus Torvalds <torvalds@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: [RFC] removal of legacy cdrom drivers (Re: [PATCH] mcdx.c insanity removal)
Date: Mon, 03 May 2004 20:08:31 +0200 [thread overview]
Message-ID: <40968A9F.6070608@keyaccess.nl> (raw)
In-Reply-To: <20040503055934.GA17014@parcelfarce.linux.theplanet.co.uk>
viro@parcelfarce.linux.theplanet.co.uk wrote:
> OK... So we have
> * potentially faulty mcdx (2.4, apparently either driver corrupts
> memory in some conditions or isofs does the same for some IO failures -
> need to take a look at that report more carefully).
> * cdu31a (FUBAR driver, nasty to fix, "most of the time" works on
> 2.6)
> * sbpcd (at least two, both untested with 2.6)
Okay, with a trivial hack to have the thing initialise when builtin,
sbpcd does pretend to work:
3y25:~$ uname -r
2.6.5
3y25:~$ mount | grep cdrom
/dev/sbpcd on /mnt/cdrom type iso9660 (ro,noexec,nosuid,nodev)
3y25:~$ ls /mnt/cdrom/
cd.id* install.exe* lecdemos/ readme.doc* resource/
support/
However, any "cp" from cd-rom oopses the box.
> Is anybody willing to fix those drivers?
I was actually planning to get around to that at some point. Somewhat
fond of this drive. As you say, driver is a disaster area; a few trivial
fixes are not what it wants and at this point, fixing it properly would
not be a trivial undertaking for me. Am also currently very busy
elsewhere. Could it be kept around a bit?
Rene.
next prev parent reply other threads:[~2004-05-03 18:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040502024637.GV17014@parcelfarce.linux.theplanet.co.uk>
[not found] ` <Pine.LNX.4.58.0405011953140.18014@ppc970.osdl.org>
2004-05-03 1:16 ` [RFC] removal of legacy cdrom drivers (Re: [PATCH] mcdx.c insanity removal) viro
2004-05-03 3:21 ` Rene Herman
2004-05-03 5:59 ` viro
2004-05-03 18:08 ` Rene Herman [this message]
2004-05-03 19:45 ` viro
2004-05-03 21:22 ` Rene Herman
2004-05-03 21:30 ` Linus Torvalds
2004-05-03 21:34 ` viro
2004-05-05 23:41 ` Adrian Bunk
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=40968A9F.6070608@keyaccess.nl \
--to=rene.herman@keyaccess.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
--cc=viro@parcelfarce.linux.theplanet.co.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.