Damien, > When scanning the drive, you need to poke it using > scsi_report_opcode() to determine which write operation is supported. > Then sd.c need to be modified to generate the proper write command if > the regular WRITE 10/16/32 are not supported. You will also need to > make sure that this does not break ATA drives managed with libata, so > check libata-scsi translation. > > Not saying this can all be accepted though. But that is what is > needed. > > Martin ? This is clearly a rare and special case, I have never come across a drive that couldn't handle a regular WRITE command. I don't see any reason to burden our stack with workarounds for drives that use custom firmware. -- Martin K. Petersen Oracle Linux Engineering
