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-22 Thread Rainer Koenig
Hi Simon, Simon Oosthoek <[EMAIL PROTECTED]> writes: > Unfortunately I'm not able to check the logic of the driver, because > although I can read C, I'm totally unfamiliar with the disk controler > logic in the kernel... Well, today I've spent some time in looking at the SiS driver and compared

Re: SATA status report updated

2005-08-21 Thread Mogens Valentin
Jeff Garzik wrote: Although I have not updated it in several weeks, folks may wish to refer to the hardware status report as well: http://linux.yyz.us/sata/sata-status.html Jeff, is it possible for you at this time to comment on support for the JMicron JMB360 sataII chip? Possible timef

Re: SATA status report updated

2005-08-21 Thread Jeff Garzik
Mogens Valentin wrote: Jeff, is it possible for you at this time to comment on support for the JMicron JMB360 sataII chip? Possible timeframe? Never heard of it. Jeff - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTEC

Re: SATA status report updated

2005-08-20 Thread Rainer Koenig
Hi Jeff, Jeff Garzik <[EMAIL PROTECTED]> writes: > Here is a list of problems with the patch. I'll paste this into the > bug as well: [Lot of interesting issues] > 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.

Re: SATA status report updated

2005-08-19 Thread Jeff Garzik
Simon Oosthoek wrote: I know Mandriva is on the ball and a bug with some information and an updated patch is on the kernel bugme... http://qa.mandriva.com/show_bug.cgi?id=17654 http://bugme.osdl.org/show_bug.cgi?id=4192 I'd say it's important to get some proper fix in a distribution soon (so

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 Jeff Garzik
Rainer Koenig wrote: Hi Simon, Simon Oosthoek <[EMAIL PROTECTED]> writes: I'm wondering how the support for the SIS 182 controller is doing, I noticed they have a GPL driver on their website for kernel 2.6.10, which is not a drop in replacement for sata_sis.c in 2.6.12.5, I haven't tried comp

Re: SATA status report updated

2005-08-19 Thread Rainer Koenig
Hi Simon, Simon Oosthoek <[EMAIL PROTECTED]> writes: > I'm wondering how the support for the SIS 182 controller is doing, I > noticed they have a GPL driver on their website for kernel 2.6.10, > which is not a drop in replacement for sata_sis.c in 2.6.12.5, I > haven't tried compiling it as an ad

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

Re: SATA status report updated

2005-08-13 Thread Erik Slagter
On Fri, 2005-08-12 at 17:30 -0400, Jeff Garzik wrote: > Matthew Garrett wrote: > > Jeff Garzik <[EMAIL PROTECTED]> 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 > > > >

Re: SATA status report updated

2005-08-12 Thread Jeff Garzik
Mogens Valentin wrote: 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 >> Queueing support, NCQ: >> #3 will be supported by libata, for all hardware and devices that >> s

Re: SATA status report updated

2005-08-12 Thread Jeff Garzik
Daniel J Blueman wrote: As stability is a concern, why not get the ATA passthru work in sooner, then follow up with the SMART support after the passthru code has had time to mature? SMART support == passthru. Jeff - To unsubscribe from this list: send the line "unsubscribe linux-ker

Re: SATA status report updated

2005-08-12 Thread Jeff Garzik
Matthew Garrett wrote: Jeff Garzik <[EMAIL PROTECTED]> 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 I couldn't see any reference to system-wide power management (ie, suspend/resume

Re: SATA status report updated

2005-08-12 Thread Mogens Valentin
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 >> Queueing support, NCQ: >> #3 will be supported by libata, for all hardware and devices that >> support NCQ. I guess this mea

Re: SATA status report updated

2005-08-12 Thread David Greaves
Jeff Garzik wrote: > > True enough :/ > > It's been feature-complete for a while, but the reports from testers > in the field have made me too nervous to push it into the upstream > kernel. > > I might push it upstream, but disable it by default, which would allow > for a wider test audience. Cou

Re: SATA status report updated

2005-08-12 Thread Luben Tuikov
On 08/12/05 01:09, 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 Good write up. I like the simplicity of error handling. Thumbs up! Luben - To unsubscribe fro

Re: SATA status report updated

2005-08-12 Thread Luben Tuikov
On 08/12/05 01:09, 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 r

Re: SATA status report updated

2005-08-12 Thread Matthew Garrett
Jeff Garzik <[EMAIL PROTECTED]> 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 I couldn't see any reference to system-wide power management (ie, suspend/resume of machines with SA

Re: SATA status report updated

2005-08-12 Thread Daniel J Blueman
As stability is a concern, why not get the ATA passthru work in sooner, then follow up with the SMART support after the passthru code has had time to mature? IMHO, the passthru work is good value alone, as there is currently no way to adjust various parameters (AM, spindown time, ...) of SATA disk

Re: SATA status report updated

2005-08-11 Thread Jeff Garzik
Rob van Nieuwkerk wrote: On Fri, 12 Aug 2005 01:09:12 -0400 Jeff Garzik <[EMAIL PROTECTED]> wrote: Hi Jeff, Things in SATA-land have been moving along recently, so I updated the software status report: http://linux.yyz.us/sata/software-status.html Is any progress made on SMART su

Re: SATA status report updated

2005-08-11 Thread Rob van Nieuwkerk
On Fri, 12 Aug 2005 01:09:12 -0400 Jeff Garzik <[EMAIL PROTECTED]> wrote: Hi Jeff, > Things in SATA-land have been moving along recently, so I updated the > software status report: > > http://linux.yyz.us/sata/software-status.html Is any progress made on SMART support ? I've been reading