On Sat, Apr 27, 2019 at 09:56:08AM +0200, Alexander Graf wrote:
>
> >>> UEFI gets a bad rap at being complicated, but I think the U-Boot work
> >>> has shown that implementing the core UEFI ABI doesn't require much code
> >>> and isn't the complicated mess they everyone fears it to be.
> >> Depend
On Thu, Nov 08, 2018 at 02:17:18PM +, Grant Likely wrote:
> Any agenda items for todays call? Here is what I have so far:
>
> - Updates
>- SetVariable()
I haven't written the update for this yet, and I'm not going to be able
to make the meeting. Sorry about that; I'll try to get it writt
On Thu, Nov 01, 2018 at 03:13:37PM +, David Rusling wrote:
> I'll attempt not to add noise into an otherwise detailed and technical
> discussion, but I like to go back to first principles:
>
> [1] Does Peter's suggested mechanism extend the use model that exists
> between a kernel and UEFI?
>
t userspace will
> still need to copy the new .cap from sysfs to the EFI, correct?
>
> > - during shutdown, we copy that .cap to the ESP as a Capsule on Disk
> > - during boot up, UEFI reads that .cap and applies the update to the
> >storage. Any cases the OS was wrong a
.
>
> This is an RFC patch. In the process of writing it, and after looking at
> the ECR submitted by Peter Jones[1], I started having doubts. I no
> longer think this is the right decision. Since the ECR now provides a
> mechanism for reporting which runtime services can be cal
