Re: UEFI Plugfest 2013 -- New Orleans

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, 19 Aug, at 09:09:54PM, David Woodhouse wrote:
> 3. Even if we can't *remove* the code, sometimes we can disable it at
> runtime if we detect the BIOS is new enough that it shouldn't be broken.
 
Yes, this is definitely something we should be looking to implement.

It seems likely to me that we're eventually going to start hitting
issues supporting the latest UEFI firmware because of the workarounds
we're currently carrying in the kernel. The EDKII folks are surprised
time and time again to hear of the hoops we jump through in the kernel
to support buggy implementations.

It's only going to be a matter of time until we *have* to disable some
our workarounds in order to boot the most recent incarantions of UEFI.
Not least because carrying these workarounds unconditionally and
indefinitely severely limits our ability to innovate.

-- 
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




[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [ECOS]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux