Thierry Vignaud wrote: > Thierry Vignaud writes: > >>>> none of both these patches worked :-( >>> The second didn't work? But you said the following one liner >>> worked. >> Worked on top of *your original patch*. >> >> What's more, >> >>> + return ata_bmdma_drive_eh(ap, vt6420_prereset, ata_std_softreset, >>> sata_std_hardreset, ata_std_postreset); >> is different from: >> >> + return ata_bmdma_drive_eh(ap, vt6420_prereset, ata_std_softreset, >> + NULL, ata_std_postreset); >> >> Note also that I tested my one liner on top of 2.6.18-rc4-mm1 + your >> patch whereas I tested your latest patches on top of 2.6.18-rc4-mm2 >> //\\ >> >> Can this make a difference? >> >>> The second patch is essentially identical to what you did the one >>> liner. Can you please check it once more? I'll prepare old-sequence >>> hardreset in the meantime. > > an btw, "the second patch is essentially identical to what you did the > one liner" doesn't *accuratly* describe the differences between your > last week patch and the second of other day patch. There're actually > a *little* more than my one-liner :-) : Heh heh this is really getting out of hand with all those different patches. Anyways, the stuff I've added recently shouldn't make too much difference. The additional codes are taken from sata_phy_reset to make it more similar to the original code. Anyways, I'll just attach my current sata_via.c to this mail as the confusion level seems to be pretty high at this point. If this version works, everything is fine. I'll submit split patches to Jeff. Sorry about the confusion. Thanks. -- tejun