Tejun Heo wrote:
[cc'ing ATA gurus]
Hello, again.
Okay, there are two different problems here, so I was confused a bit,
but now I see what's going on.
sjackerman@xxxxxxxxxxx wrote:
ata2: SATA max UDMA/133 cmd 0xE400 ctl 0xE002 bmdma 0xDC08 irq 10
scsi2 : ata_piix
ata1.00: CFA, max PIO4, 8005536 sectors: LBA
ata1.00: ata1: dev 0 multi count 0
ata1.00: qc timeout (cmd 0xef)
ata1.00: failed to set xfermode (err_mask=0x4)
..
Jeff, Alan, Mark and Albert, do you have ideas how we should support
this one? This thing locks up if nIEN is set in command FIS.
It would be useful to see the full tf on those errors.
My experience with PATA drives and CF cards, it that they
default to PIO4 (assuming they report supporting PIO4).
So we don't actually need to do a set xfer mode on them.
Is the full IDENTIFY data available (hex, please)?
Perhaps we can recognize this beast and just handle it
differently when detected.
Is it the CF card, or the CF adaptor, that's the problem?
Many questions, not many answers (yet).
-
To unsubscribe from this list: send the line "unsubscribe linux-ide" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
