On Oct 2, 2015 10:37 AM, "Borislav Petkov" <bp@xxxxxxxxx> wrote: > > On Fri, Oct 02, 2015 at 05:05:52AM +0800, Kweh, Hock Leong wrote: > > From: "Kweh, Hock Leong" <hock.leong.kweh@xxxxxxxxx> > > > > Dear maintainers & communities, > > > > This patchset is created on top of Matt's patchset: > > 1.)https://lkml.org/lkml/2014/10/7/390 > > "[PATCH 1/2] efi: Move efi_status_to_err() to efi.h" > > 2.)https://lkml.org/lkml/2014/10/7/391 > > "[PATCH 2/2] efi: Capsule update support" > > > > It expose a misc char interface for user to upload the capsule binary and > > calling efi_capsule_update() API to pass the binary to EFI firmware. > > > > The steps to update efi firmware are: > > 1.) cat firmware.cap > /dev/efi_capsule_loader > > 2.) reboot > > > > Any failed upload error message will be returned while doing "cat" through > > Write() function call. > > > > Tested the code with Intel Quark Galileo platform. > > What does the error case look like? A standard glibc message about > write(2) failing? > close(2), right? --Andy -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
