On Mon, Jul 31 2006, Linus Torvalds wrote: > > > On Mon, 31 Jul 2006, Jens Axboe wrote: > > > > There are, however, new uses of vendor specific commands that you need > > access to for fully utilizing your drive. As mentioned, Plextor is one > > of these. And they do make current and very good burners, yet we cannot > > add their opcodes to the table because they (sanely) used the vendor > > specific range for that. > > However, before we do that, can somebody actially just FIX that stupid > cdrecord bug. It shouldn't say it can't write the drive, if it's just that > it's not allowed to use one of the vendor-specific extensions. > > As mentioned, I bet burning _does_ actually work. Oh yeah, I think so too. It's for other features on the Plextor, like disc quality scans. So it's not critical as such for burning, but it is something that we do want to work. I don't think you disagree that we need to support the vendor unique range of opcodes. And I don't think you disagree that we cannot safely put these in the global table. So that leaves one sane option - per device cmd filter table. I've kept Peter's original patch somewhat uptodate, I'll bring it to 2.6.18-rc3 and test+submit for 2.6.19. -- Jens Axboe - : send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
