variables properly. This means that mokutil 0.2 won't work
> with this kernel commit, but mokutil 0.3 which uses efivar
> (https://github.com/lcp/mokutil/commit/7b49e834284659527c9f7cf554f223748c00564b)
> should work properly.
>
> fwupdate works properly in most instances except for
variables properly. This means that mokutil 0.2 won't work
> with this kernel commit, but mokutil 0.3 which uses efivar
> (https://github.com/lcp/mokutil/commit/7b49e834284659527c9f7cf554f223748c00564b)
> should work properly.
>
> fwupdate works properly in most instances except for
On 03/22/2016 04:37 PM, Limonciello, Mario wrote:
> ed8b0de5a33d2a2557dce7f9429dca8cb5bc5879 caused all variables to be
> immutable by default. This causes problems with userspace applications
> mokutil and fwupdate.
> ---
> drivers/firmware/efi/vars.c | 2 ++
> include/linux
On 03/22/2016 04:37 PM, Limonciello, Mario wrote:
> ed8b0de5a33d2a2557dce7f9429dca8cb5bc5879 caused all variables to be
> immutable by default. This causes problems with userspace applications
> mokutil and fwupdate.
> ---
> drivers/firmware/efi/vars.c | 2 ++
> include/linux
ed8b0de5a33d2a2557dce7f9429dca8cb5bc5879 caused all variables to be
immutable by default. This causes problems with userspace applications
mokutil and fwupdate.
---
drivers/firmware/efi/vars.c | 2 ++
include/linux/efi.h | 8
2 files changed, 10 insertions(+)
diff --git
ed8b0de5a33d2a2557dce7f9429dca8cb5bc5879 caused all variables to be
immutable by default. This causes problems with userspace applications
mokutil and fwupdate.
---
drivers/firmware/efi/vars.c | 2 ++
include/linux/efi.h | 8
2 files changed, 10 insertions(+)
diff --git
On Tue, Mar 10, 2015 at 10:56:32AM -0400, Peter Jones wrote:
> That said, I haven't sent my patch to add the capsule headers to gnu-efi
> yet, so you won't get very far - I'll make sure and send those this
> week, hopefully today.
Slight correction, I did actually do that - it's in the current
On Mon, Mar 09, 2015 at 06:54:12PM -0700, Roy Franz wrote:
> On Mon, Mar 9, 2015 at 2:23 PM, Borislav Petkov wrote:
> > + pjones.
> >
> > So reportedly, there is already a capsule-loading thing which doesn't
> > need the kernel at all:
> >
> > https://git
On Mon, Mar 09, 2015 at 06:54:12PM -0700, Roy Franz wrote:
On Mon, Mar 9, 2015 at 2:23 PM, Borislav Petkov b...@alien8.de wrote:
+ pjones.
So reportedly, there is already a capsule-loading thing which doesn't
need the kernel at all:
https://github.com/rhinstaller/fwupdate
So why
On Tue, Mar 10, 2015 at 10:56:32AM -0400, Peter Jones wrote:
That said, I haven't sent my patch to add the capsule headers to gnu-efi
yet, so you won't get very far - I'll make sure and send those this
week, hopefully today.
Slight correction, I did actually do that - it's in the current
On Mon, Mar 9, 2015 at 2:23 PM, Borislav Petkov wrote:
> + pjones.
>
> So reportedly, there is already a capsule-loading thing which doesn't
> need the kernel at all:
>
> https://github.com/rhinstaller/fwupdate
>
> So why are we even wasting energy with this discussio
+ pjones.
So reportedly, there is already a capsule-loading thing which doesn't
need the kernel at all:
https://github.com/rhinstaller/fwupdate
So why are we even wasting energy with this discussion here?
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply
+ pjones.
So reportedly, there is already a capsule-loading thing which doesn't
need the kernel at all:
https://github.com/rhinstaller/fwupdate
So why are we even wasting energy with this discussion here?
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply
On Mon, Mar 9, 2015 at 2:23 PM, Borislav Petkov b...@alien8.de wrote:
+ pjones.
So reportedly, there is already a capsule-loading thing which doesn't
need the kernel at all:
https://github.com/rhinstaller/fwupdate
So why are we even wasting energy with this discussion here?
--
Regards
14 matches
Mail list logo
