From: Jens Axboe <axboe@suse.de>
To: Pascal Schmidt <der.eremit@email.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [IDE] trying to make MO drive work with ide-floppy/ide-cd
Date: Tue, 6 May 2003 17:25:43 +0200 [thread overview]
Message-ID: <20030506152543.GX905@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.44.0305061715150.965-100000@neptune.local>
On Tue, May 06 2003, Pascal Schmidt wrote:
> On Tue, 6 May 2003, Jens Axboe wrote:
>
> > It barfs at a lot of commands, not surprisingly. ide-cd really has no
> > concept of devices other than cd/dvd.
>
> I'm not complaining about those messages. ;)
No, but clearly something is wrong. At least that you should agree on.
And knowing hardware, there are probably drives out there that just wont
work because of the various "weird" commands it gets sent.
Just because it happens to work for you doesn't make it a viable
solution.
> > You need to patch cdrom.c as well:
> >
> > if ((fp->f_mode & FMODE_WRITE) && !CDROM_CAN(CDC_DVD_RAM))
> > return -EROFS;
> >
>
> Simply removing that test doesn't get me working write support,
> I still get:
>
> # mount -t ext2 /dev/hde /mnt/mo
> mount: block device /dev/hde is write-protected, mounting read-only
>
> The disk is not write-protected, I checked.
Shouldn't matter, the drive has to check for that particular bit (and it
obviously does not). Are we still talking 2.5 or 2.4?
> >> What can I do to help get this drive supported under 2.5/ide-cd?
> > I'm tempted to say ide-scsi + sd, but that goes against my principles...
> > It shouldn't be too much work to make ide-cd work gracefully.
>
> Well, I'm not familiar with the code at all, so I don't know where
> to look.
You can play with the c code, you've demonstrated that much so far. So
play some more, find out which commands are aborted and why. The log
messages even tell you which ones. Now find out if these are necessary
for proper MO functionality or not. Or maybe some vital commands are
even missing, lots of fun there :). But it really should not be very
hard.
--
Jens Axboe
next prev parent reply other threads:[~2003-05-06 15:13 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-05 20:04 [IDE] trying to make MO drive work with ide-floppy Pascal Schmidt
2003-05-06 9:41 ` Alan Cox
2003-05-06 14:02 ` [IDE] trying to make MO drive work with ide-floppy/ide-cd Pascal Schmidt
2003-05-06 14:07 ` Jens Axboe
2003-05-06 15:19 ` Pascal Schmidt
2003-05-06 15:25 ` Jens Axboe [this message]
2003-05-06 15:43 ` Jens Axboe
2003-05-06 16:23 ` Pascal Schmidt
2003-05-06 16:22 ` Pascal Schmidt
2003-05-06 17:59 ` Pascal Schmidt
2003-05-06 18:04 ` Jens Axboe
2003-05-06 18:18 ` Pascal Schmidt
2003-05-06 14:10 ` Pascal Schmidt
2003-05-06 14:11 ` Jens Axboe
2003-05-06 15:15 ` Pascal Schmidt
2003-05-07 18:02 ` Pascal Schmidt
2003-05-07 19:33 ` Jens Axboe
2003-05-08 11:33 ` Pascal Schmidt
2003-05-08 12:09 ` Jens Axboe
2003-05-08 12:20 ` Bartlomiej Zolnierkiewicz
2003-05-08 12:43 ` Pascal Schmidt
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=20030506152543.GX905@suse.de \
--to=axboe@suse.de \
--cc=der.eremit@email.de \
--cc=linux-kernel@vger.kernel.org \
/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