From: Eric W. Biederman on
Matthew Garrett <mjg59(a)srcf.ucam.org> writes:

> On Tue, Aug 03, 2010 at 02:45:33PM -0700, Eric W. Biederman wrote:
>
>> EFI runtime calls have the nasty fact that they don't work in general even
>> if EFI is present because you may have the wrong word size EFI running on
>> your machine. A 32bit EFI and a 64bit kernel or a 64bit EFI and a 32bit kernel.
>
> You've already failed to boot in that case.

Only if you have EFI runtime services enabled in your kernel. You can
skip the efi junk and the kernel runs just fine. Doing what we do on
every other platform which appears to be a combination of ACPI and
direct hardware access appears to be good enough, and that is a path
that actually gets tested regularly.

Eric
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Matthew Garrett on
On Tue, Aug 03, 2010 at 02:58:10PM -0700, Eric W. Biederman wrote:

> Only if you have EFI runtime services enabled in your kernel. You can
> skip the efi junk and the kernel runs just fine. Doing what we do on
> every other platform which appears to be a combination of ACPI and
> direct hardware access appears to be good enough, and that is a path
> that actually gets tested regularly.

I think wanting to set the nvram variables so that your bootloader works
is a pretty typical usecase...
--
Matthew Garrett | mjg59(a)srcf.ucam.org
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/