Hi Ard,
On Tue, Jul 15, 2014 at 05:50:30PM +0100, Ard Biesheuvel wrote:
The EFI loader may load Image at any available offset. This means Image may
reside very close to or at the base of DRAM, in which case the relocation
done by efi_entry() results in Image being moved up in memory, which is
On Tue, 2014-07-15 at 16:28 +0100, Leif Lindholm wrote:
On Tue, Jul 15, 2014 at 11:04:37AM -0400, Mark Salter wrote:
On Tue, 2014-07-15 at 15:49 +0100, Leif Lindholm wrote:
On Tue, Jul 15, 2014 at 10:23:26AM -0400, Mark Salter wrote:
On Tue, 2014-07-15 at 14:54 +0100, Leif Lindholm
On Tue, 2014-07-15 at 18:50 +0200, Ard Biesheuvel wrote:
The EFI loader may load Image at any available offset. This means Image may
reside very close to or at the base of DRAM, in which case the relocation
done by efi_entry() results in Image being moved up in memory, which is
undesirable
On 16/07/14 15:34, Matt Fleming wrote:
On Tue, 15 Jul, at 08:44:34AM, H. Peter Anvin wrote:
Do we know what the Windows bootloader does? I thought it did use the
EFI File Protocol?
Good question. I'm not sure what the answer is, I'll try and find some
time to take a look.
I'm in the middle
On Tue, 2014-07-15 at 12:58 +0200, Ard Biesheuvel wrote:
After the EFI stub has done its business, it jumps into the kernel by
branching
to offset #0 of the loaded Image, which is where it expects to find the header
containing a 'branch to stext' instruction.
However, the header is not
On Wed, Jul 16, 2014 at 03:51:37PM +0100, Mark Salter wrote:
On Tue, 2014-07-15 at 12:58 +0200, Ard Biesheuvel wrote:
After the EFI stub has done its business, it jumps into the kernel by
branching
to offset #0 of the loaded Image, which is where it expects to find the
header
On Wed, 2014-07-16 at 16:53 +0100, Mark Rutland wrote:
On Wed, Jul 16, 2014 at 03:51:37PM +0100, Mark Salter wrote:
On Tue, 2014-07-15 at 12:58 +0200, Ard Biesheuvel wrote:
After the EFI stub has done its business, it jumps into the kernel by
branching
to offset #0 of the loaded
On 16 July 2014 16:10, Mark Salter msal...@redhat.com wrote:
On Tue, 2014-07-15 at 18:50 +0200, Ard Biesheuvel wrote:
The EFI loader may load Image at any available offset. This means Image may
reside very close to or at the base of DRAM, in which case the relocation
done by efi_entry()
On 16 July 2014 23:03, Mark Salter msal...@redhat.com wrote:
On Wed, 2014-07-16 at 22:38 +0200, Ard Biesheuvel wrote:
On 16 July 2014 21:45, Mark Salter msal...@redhat.com wrote:
On Wed, 2014-07-16 at 16:53 +0100, Mark Rutland wrote:
On Wed, Jul 16, 2014 at 03:51:37PM +0100, Mark Salter
On Wed, 2014-07-16 at 22:38 +0200, Ard Biesheuvel wrote:
On 16 July 2014 21:45, Mark Salter msal...@redhat.com wrote:
On Wed, 2014-07-16 at 16:53 +0100, Mark Rutland wrote:
On Wed, Jul 16, 2014 at 03:51:37PM +0100, Mark Salter wrote:
On Tue, 2014-07-15 at 12:58 +0200, Ard Biesheuvel wrote:
On Wed, Jul 16, 2014 at 1:38 PM, Ard Biesheuvel
ard.biesheu...@linaro.org wrote:
On 16 July 2014 21:45, Mark Salter msal...@redhat.com wrote:
On Wed, 2014-07-16 at 16:53 +0100, Mark Rutland wrote:
On Wed, Jul 16, 2014 at 03:51:37PM +0100, Mark Salter wrote:
On Tue, 2014-07-15 at 12:58 +0200,
11 matches
Mail list logo
