Mark Lord wrote: > Jeff Garzik wrote: >> >> Without answering your specific question, just remember that sata_mv >> is considerly "highly experimental" right now, and still needs some >> workarounds for hardware errata. >> >> For now, the goal is a system that doesn't crash and doesn't corrupt >> data. If its occasionally slow or spits out a few errors, but >> otherwise still works, that's pretty darned good :) > > I'm currently working with the original authors of sata_mv, and have taken > over maintenance of it for now. It should progress from "highly > experimental" > to "production quality" over the next month or so. > > The (mucho) updated driver I'm using here now is already much improved > in many ways. At some point, I'll break it out into patches for Jeff. > > But there's one MAJOR bugfix patch that I'll release here shortly, > to go with the interrupt handler fix already posted. This is great news. Is there any relationship between the development of this driver and the one maintained by Marvell that's available from their web site ? Their latest version (3.6.1) is released under the GPL, and is a very solid driver based our experience with it over the past few years, though it's targeted at older versions of the linux kernel and needs some porting to 2.6.16 (and contains redundant stuff like its own scsi-ata layer). Denis Leroy - : 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
