On Wed, Feb 25, 2015 at 12:38:20PM +, Kweh, Hock Leong wrote:
The reason we use this interface for efi capsule is that efi capsule
support multi binaries to be uploaded and each binary file name
can be different.
So you can write the file path to a second file and reload then, once
per
On Tue, Feb 24, 2015 at 12:49:09PM +, Kweh, Hock Leong wrote:
So the process steps basically look like this:
1.) cat capsule_ticket=== acquire a number and lock mutex then
expose
firmware_class user helper
-Original Message-
From: Borislav Petkov [mailto:b...@alien8.de]
Sent: Wednesday, February 25, 2015 7:48 PM
On Tue, Feb 24, 2015 at 12:49:09PM +, Kweh, Hock Leong wrote:
So this sounds pretty overengineered for no reason, or maybe I'm missing
the reason.
If I had to give
On Wed, 25 Feb, at 11:31:32AM, Ingo Molnar wrote:
* Matt Fleming m...@codeblueprint.co.uk wrote:
On Sun, 22 Feb, at 07:43:48PM, Yinghai Lu wrote:
Index: linux-2.6/arch/x86/boot/header.S
===
---
On Tue, 24 Feb, at 04:31:27PM, Yinghai Lu wrote:
On Tue, Feb 24, 2015 at 1:55 PM, Matt Fleming m...@codeblueprint.co.uk
wrote:
On Sun, 22 Feb, at 07:43:48PM, Yinghai Lu wrote:
+Field name: ext_code32_start
+Type:modify (optional, reloc)
+Offset/size: 0x268/4
On 02/24/15 at 10:13am, Juergen Gross wrote:
Areas mapped via early_memremap() should be unmapped via
early_memunmap(), while I/O-areas should be mapped via early_ioremap()
and unmapped via early_iounmap().
There are multiple spots where an area is mapped via the mem variant
and unmapped
* Matt Fleming m...@codeblueprint.co.uk wrote:
On Sun, 22 Feb, at 07:43:48PM, Yinghai Lu wrote:
Index: linux-2.6/arch/x86/boot/header.S
===
--- linux-2.6.orig/arch/x86/boot/header.S
+++ linux-2.6/arch/x86/boot/header.S
@@
