Compact Flash Serial ATA patch
I was having some trouble with a serial ATA compact flash adapter with libata. I wrote a small patch for the kernel to work around the sanity check, dma blacklisting and device ID detections in ata_dev_classify().
I am not exactly a programmer, I'm sure this can be written much better but for anyone who may run into a similar problem with compact flash.
Russell McConnachie.
822,825c822,845
< ((tf->lbam == 0x3c) && (tf->lbah == 0xc3))) {
< DPRINTK("found ATA device by sig\n");
< return ATA_DEV_ATA;
< }
---
Quoted 17 lines
// Allows the compact flash to work, For some reason our // Addonics SATA flash reader/writer. // The following types of flash have been used: // - Infineon 2.0GB // - Sandisk Ultra II 2.0GB // - Lexar Platinum // // Sandisk Compact Flash ((tf->lbam == 0x30) && (tf->lbah == 0)) || // Infineon Compact Flash ((tf->lbam == 0x50) && (tf->lbah == 0)) || // Infineon Compact Flash ((tf->lbam == 0x55) && (tf->lbah == 0)) ||
Quoted 7 lines
// Infineon Compact Flash
(((tf->lbam > 0x2f) && (tf->lbam < 0x7f)) && (tf->lbah == 0)) ||
((tf->lbam == 0x3c) && (tf->lbah == 0xc3))) {
DPRINTK("found ATA device by sig\n");
return ATA_DEV_ATA;
}875a896,897
Quoted 2 lines
else if (device == 0) /* do nothing */ ;
1335,1336c1357,1358
< if (!ata_id_is_ata(dev->id)) /* sanity check */
< goto err_out_nosup;
---
Quoted 2 lines
// if (!ata_id_is_ata(dev->id)) /* sanity check */
// gotoerr_out_nosup;
2235a2258,2260
Quoted 3 lines
"MODEL", "SMI MODEL", "SanDisk SDCFH-2048",
Quoted 3 lines · Russell McConnachie
I was having some trouble with a serial ATA compact flash adapter with libata. I wrote a small patch for the kernel to work around the sanity check, dma blacklisting and device ID detections in
ata_dev_classify().
I've had this problem, too. Apparently, my CF/SATA bridge doesn't support DMA, but libata requires it.
I don't know if this is the right fix (if nothing else the patch needs to be sent in unified diff format), but it's certainly something that needs fixing.
Matt
Signature · 6 lines
Matthew Dharm Home: [email protected] Maintainer, Linux USB Mass Storage Driver Somebody call an exorcist! -- Dust Puppy User Friendly, 5/16/1998
Hi Matt,
The patch which stopped the DMA problems was adding the model ID to the dma blacklist in the libata-core.c file. I will create another patch in unified diff format, it seems that compact flash uses different device IDs than regular ATA/ATAPI devices.
Quoted 14 lines · Matthew Dharm
Quoted 3 lines · Russell McConnachie
I was having some trouble with a serial ATA compact flash adapter with libata. I wrote a small patch for the kernel to work around the sanity check, dma blacklisting and device ID detections in
ata_dev_classify().I've had this problem, too. Apparently, my CF/SATA bridge doesn't support DMA, but libata requires it.
I don't know if this is the right fix (if nothing else the patch needs to be sent in unified diff format), but it's certainly something that needs fixing.
Matt
Quoted 3 lines · Matthew Dharm
I don't know if this is the right fix (if nothing else the patch needs to be sent in unified diff format), but it's certainly something that needs fixing.
I sent Jeff the patch to fix that a few days ago. Jeff can probably tell you if its been applied yet. If not grab the libata PATA patches as they include the needed fixes for 2.6.17-rc. The 2.6.17-mm tree is a bit different so may be ok anyway.
Quoted 2 lines · Russell McConnachie
I am not exactly a programmer, I'm sure this can be written much better but for anyone who may run into a similar problem with compact flash.
Some CF adapters do not include all the neccessary pins for DMA because they were designed to be cheap before the idea of CF using DMA seemed realistic.
Alan
Quoted 8 lines · Alan Cox
Quoted 3 lines · Russell McConnachie
I am not exactly a programmer, I'm sure this can be written much better but for anyone who may run into a similar problem with compact flash.
Some CF adapters do not include all the neccessary pins for DMA because they were designed to be cheap before the idea of CF using DMA seemed realistic.
Some CF adapters I've seen included all necessary pins but the pin connections for DMA were missing. Someone at a slackware mailing list was having the same problem, and if I recall correctly (better check specs though) it can be fixed quite easily:
CF pin 44: disconnect from +V, connect to IDE pin 29. CF pin 43: connect to IDE pin 21.
Typical transfer rates increased to about 10-12 MB/s
Signature · 1 line
left blank, right bald
Quoted 19 lines · markus reichelt
Quoted 10 lines · Alan Cox
Quoted 4 lines · Russell McConnachie
I am not exactly a programmer, I'm sure this can be written much better but for anyone who may run into a similar problem with compact flash.
Some CF adapters do not include all the neccessary pins for DMA because they were designed to be cheap before the idea of CF using DMA seemed realistic.
Some CF adapters I've seen included all necessary pins but the pin connections for DMA were missing. Someone at a slackware mailing list was having the same problem, and if I recall correctly (better check specs though) it can be fixed quite easily:
Quoted 5 lines
CF pin 44: disconnect from +V, connect to IDE pin 29. CF pin 43: connect to IDE pin 21.
Typical transfer rates increased to about 10-12 MB/s
No more than that? I have a CF card on parallel IDE, hdparm can read 20MB/s from it with the 4GB 100xKingston card I use to boot from. Of course this card was bought precisely for its speed (and size).
Helge Hafting