On Wed, 19 Mar 2008, Pavel Machek wrote: > Also, for polling mode to work on Acers, we need > to insert a delay. Can we, in the future, always trigger any such performance damaging "fixups" based on DMI white/black lists? As a rule? This is not the first time I see a vendor push broken crap, and everyone else who did it right get the shaft, because people don't like to add quirks to common code. We get performance enhancement features disabled, mdelays added... And for the do-as-windows-does crowd, they do it on vendorissued device drivers, which obviously don't hork everyone else's devices. Our equivalent solution is to key things to DMI matches. This is worth keeping in mind, because the ACPI subsystem seems to be a common target for such bad behaviour. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
