linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pascal Schmidt <der.eremit@email.de>
To: Jens Axboe <axboe@suse.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 18:22:40 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.44.0305061816490.1310-100000@neptune.local> (raw)
In-Reply-To: <20030506152543.GX905@suse.de>

On Tue, 6 May 2003, Jens Axboe wrote:

> No, but clearly something is wrong. At least that you should agree on.

Yes, I would guess the MO drive doesn't like most commands that are
used for DVD/CD-ROMs and writers.

> And knowing hardware, there are probably drives out there that just wont
> work because of the various "weird" commands it gets sent.

Okay, I was assuming those errors don't do harm, but that might
be wrong, yeah.

> Just because it happens to work for you doesn't make it a viable
> solution.

Agreed.

> 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?

2.5
The solution with ide-scsi is good enough for me on 2.4, but since CD
burning also doesn't need ide-scsi any more on 2.5, I'd like to use a
kernel without any SCSI code in it.

> 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.

Okay. I'll try to find a way to pass the information that the drive
was originally detected as ide_optical down to ide-cd.c so I can skip
the commands that don't make sense on an MO drive.

> 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.

I'll go play with the code some more, then.

-- 
Ciao,
Pascal


  parent reply	other threads:[~2003-05-06 16:11 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
2003-05-06 15:43           ` Jens Axboe
2003-05-06 16:23             ` Pascal Schmidt
2003-05-06 16:22           ` Pascal Schmidt [this message]
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=Pine.LNX.4.44.0305061816490.1310-100000@neptune.local \
    --to=der.eremit@email.de \
    --cc=axboe@suse.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;
as well as URLs for NNTP newsgroup(s).