From: Roy Franz
Date: Mon Mar 09 2015 - 21:54:22 EST
On Mon, Mar 9, 2015 at 2:23 PM, Borislav Petkov <bp@xxxxxxxxx> wrote:
> + pjones.
> So reportedly, there is already a capsule-loading thing which doesn't
> need the kernel at all:
> So why are we even wasting energy with this discussion here?
The network boot case can be taken care of as Peter described (ie
taking network device paths, instead of just file paths), so
this should work for those cases as well. There would be some extra
setup, as for this to work the EFI firmware update program
would need to be run at boot (via the BootNext variable), but I don't
think this is unreasonable.
It looks like GnuEFI now supports Aarch64, so building the firmware
update utility shouldn't be a problem. Peter - have you you tried
this on Aarch64 yet? If not I'll give it a try.
I think there is some value in using runtime update capsule calls, as
that will help make sure the feature works in the firmware. I think
with arm64 servers
in an early stage of development, we can influence the firmware
support of various features by using them. I don't know that this is
a sufficient reason, but if
runtime capsules are never used then there is a good chance that there
will be many broken implementations.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/