In message <4637379F.7070805@xxxxxx>, you write: >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). The CF card I'm using is a modern SanDisk, which supports up to MDMA2. I'd like to be able to use their new Extreme IV, which supports up to UDMA6. The flash parts themselves are now getting fast enough that DMA really makes a difference vs. PIO. The same card in a CF<->PATA adapter chained to a PATA<->SATA adapter based on a different bridge chip works fine. So I don't think it's the card, or the CF technology inherently. My personal estimation is that the ACard bridge chip is buggy and in need of a work-around. What do I need to run in order to extract the full IDENTIFY data for you? Keep in mind that I can't get a kernel booted that will fully see this device. (i.e., no SCSI disk is ever allocated) Thanks, -Craig - 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
