Changes in siimage driver?
Quoted 1 line · Bartlomiej Zolnierkiewicz
controllers. I believe freebsd's workaround is correct and we can
adopt > it.
Quoted 1 line
For more details please see the other thread regarding siimage.
According to what I've seen in the release notes of the closed-source siimage driver (I posted what I found), the right fix could be in netbsd's code, but in sys/dev/ata/wd.c :
* Some Seagate S-ATA drives have a PHY which can get confused
* with the way data is packetized by some S-ATA controllers. *
* The work-around is to split in two any write transfer whose
* sector count % 15 == 1 (assuming 512 byte sectors).
I'm not smart enough to try and write a patch, but maybe the siimage maintainer could have a look to that file...
Eduardo.
Did that already, yet the linux does not like odd break point in the SG list and thus there are some ugliess to solve.
Andre Hedrick
LAD Storage Consulting Group
Quoted 27 lines · CASINO_E
Quoted 1 line · Bartlomiej Zolnierkiewicz
controllers. I believe freebsd's workaround is correct and we can
adopt > it.
Quoted 1 line
For more details please see the other thread regarding siimage.
According to what I've seen in the release notes of the closed-source siimage driver (I posted what I found), the right fix could be in netbsd's code, but in
sys/dev/ata/wd.c:* Some Seagate S-ATA drives have a PHY which can get confused
* with the way data is packetized by some S-ATA controllers. *
* The work-around is to split in two any write transfer whose
* sector count % 15 == 1 (assuming 512 byte sectors).I'm not smart enough to try and write a patch, but maybe the siimage maintainer could have a look to that file...
Eduardo.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/