Re: SATA status report updated

2005-08-22 Thread Simon Oosthoek
Hi Rainer Rainer Koenig wrote: Jeff Garzik <[EMAIL PROTECTED]> writes: 8) The DMA pad code is very buggy. It uses the dma_map_single() to map a buffer, but never synchronizes nor flushes the buffer. This can and will lead to data corruption, particularly on x86-64 platform. That's very bad

Re: SATA status report updated

2005-08-19 Thread Simon Oosthoek
Jeff Garzik wrote: Yes, that's why I have resisted the "just add the PCI ID" patches that have cropped up. SiS submitted patches that duplicated portions of libata inside their driver, rather than simply fixing libata as would be proper. So we are stuck in the middle :( Someone needs to wo

Re: SATA status report updated

2005-08-19 Thread Simon Oosthoek
Jeff Garzik wrote: Things in SATA-land have been moving along recently, so I updated the software status report: http://linux.yyz.us/sata/software-status.html Although I have not updated it in several weeks, folks may wish to refer to the hardware status report as well: http://lin