On Wed, 2013-03-06 at 08:35 -0500, shea@xxxxxxxxxxxx wrote: > Unrelated to the initial issue, but with the growing number of fixes > for buggy firmware out there, maybe we should consider an approach > similar to CONFIG_PCI_QUIRKS and the separate drivers/pci/quirks.c, > where all of the system specific EFI quirks are isolated and can be > compiled out if you know your firmware is good? Right, the firmware bug spectrum is indeed starting to grow rapidly. I was hoping we could avoid doing something like PCI quirks because that whole thing is a mess and I am concerned about an explosion of quirks that would need to be maintained, some being used in core architecture code. Upto now, we've been catering for the least common denominator, which has worked, but obviously isn't ideal. My plan has always been to try and hold off on introducing something like quirks until my hand is forced. But it is likely that will happen sooner rather than later. One problem we have though, is clearly identifying machines that suffer from these bugs because of the cross-pollination of firmware from Independent BIOS Vendors (IBVs) and OEMs. In theory, we could use the FirmwareRevision field in the EFI System Table, along with DMI strings and such. > Also might be nice to have a separate config option specifically for > all the Apple quirks, as their EFI seems to be the worst out there with > respect to following standards. AFAIK, it's that they're based on EFI 1.10, so pre-UEFI days. -- Matt Fleming, Intel Open Source Technology Center -- To unsubscribe from this list: send the line "unsubscribe linux-efi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
