Stanislav Brabec wrote:
> Jeff Garzik wrote:
>> Tejun Heo wrote:
>>> [libata]
>>> And, as the device requires custom high level driver, libata fails
>>> miserably.  Would it be worth to try support these devices?  Or are
>>> they just too outdated to put the effort in?
>> What SCSI peripheral device type does it report, when booted under libata?
> 
> Internal IOMEGA ZIP 100 IDE (manufactured by NEC).
> 
> ata1.01: ATAPI, max PIO2, CDB intr
> ata1.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2
> ata1.01: cmd a0/00:00:00:00:20/00:00:00:00:00/b0 tag 0 cdb 0x12 data 36 in
>          res 00/00:00:00:00:00/00:00:00:00:00/00 Emask 0x2 (HSM violation)
> ata1: soft resetting port
> ata1.01: configured for PIO2
> ata1: EH complete
> ata1.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2
> ata1.01: cmd a0/00:00:00:00:20/00:00:00:00:00/b0 tag 0 cdb 0x12 data 36 in
>          res 00/00:00:00:00:00/00:00:00:00:00/00 Emask 0x2 (HSM violation)
> ata1.01: configured for PIO2
> ata1: EH complete
> ata1.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2
> ata1.01: cmd a0/00:00:00:00:20/00:00:00:00:00/b0 tag 0 cdb 0x12 data 36 in
>          res 00/00:00:00:00:00/00:00:00:00:00/00 Emask 0x2 (HSM violation)
> ata1: soft resetting port
> ... and so on
> 
> For more see
> https://bugzilla.novell.com/show_bug.cgi?id=232086
> (complete ide-floppy and libata logs are there)

I'm attaching full dmesg with libata here just in case.

It seems ide-floppy needs some special handlings in interrupt handling
too like delaying data transfer by several ticks after device indicates
readiness.  Apart from separate high level driver, we might have to
modify libata HSM implementation if we're gonna support these devices.

Can someone more knowledgeable explain what needs to be done differently
from standard ATAPI for these devices?

Thanks.

-- 
tejun