> 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- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/