On Thu, 22 Feb 2007 12:11:32 -0500 Jeff Garzik <[EMAIL PROTECTED]> wrote:
> Alan wrote: > > ACPI is the only way to do cable handling on the Nvidia PATA chipset. The > > You failed to quote the salient part of the message. Disliking a > separate pata_acpi driver in no way invalidates your statement (quoted > above). If you drive a device by the ACPI interface you don't get to fiddle with it directly or you end up in a murky world of undefined and ungood behaviour. Testing and vendor information both say pata_acpi is the right way to drive Nvidia PATA ports. Cable problem appears to be that - Tejun fixed the drive side detect logic to be stricter and correct - Large numbers of controllers with host side detect don't do drive side detect Changing the code to clip rates only for 40wire or unknown cables improves the behaviour. In the ACPI case I found another corner case with one BIOS which chooses to boot in PIO mode and which therefore fooled the cable detect trick used by pata_acpi. It now does further cable checking in ->mode_filter which combined with the patch in -mm to do the cable logic last means it works for that case too. Alan - 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/
