On 10 October 2014 01:20, Roy Franz roy.fr...@linaro.org wrote:
On Thu, Oct 9, 2014 at 3:19 PM, Mark Salter msal...@redhat.com wrote:
On Thu, 2014-10-09 at 21:03 +0200, Ard Biesheuvel wrote:
On 9 October 2014 19:23, Mark Rutland mark.rutl...@arm.com wrote:
Hi Ard,
On Wed, Oct 08, 2014 at
On 6 October 2014 13:06, Ard Biesheuvel ard.biesheu...@linaro.org wrote:
This reverts commit 84be880560fb, which itself reverted my original
attempt to move x86 from #include'ing .c files from across the tree
to using the EFI stub built as a static library.
The issue that affected the
Hey,
On 10-10-14 08:35, Ard Biesheuvel wrote:
On 6 October 2014 13:06, Ard Biesheuvel ard.biesheu...@linaro.org wrote:
This reverts commit 84be880560fb, which itself reverted my original
attempt to move x86 from #include'ing .c files from across the tree
to using the EFI stub built as a
On 10 October 2014 10:30, Maarten Lankhorst
maarten.lankho...@canonical.com wrote:
Hey,
On 10-10-14 08:35, Ard Biesheuvel wrote:
On 6 October 2014 13:06, Ard Biesheuvel ard.biesheu...@linaro.org wrote:
This reverts commit 84be880560fb, which itself reverted my original
attempt to move x86
Position independent AArch64 code needs to be linked and loaded at the same
relative offset from a 4 KB boundary, or adrp/add and adrp/ldr pairs will
not work correctly. (This is how PC relative symbol references with a 4 GB
reach are emitted)
We need to declare this in the PE/COFF header,
Hi Ard,
On Fri, Oct 10, 2014 at 10:25:24AM +0100, Ard Biesheuvel wrote:
Position independent AArch64 code needs to be linked and loaded at the same
relative offset from a 4 KB boundary, or adrp/add and adrp/ldr pairs will
not work correctly. (This is how PC relative symbol references with a 4
On 10 October 2014 12:33, Mark Rutland mark.rutl...@arm.com wrote:
Hi Ard,
On Fri, Oct 10, 2014 at 10:25:24AM +0100, Ard Biesheuvel wrote:
Position independent AArch64 code needs to be linked and loaded at the same
relative offset from a 4 KB boundary, or adrp/add and adrp/ldr pairs will
not
On Thu, Oct 09, 2014 at 08:03:52PM +0100, Ard Biesheuvel wrote:
On 9 October 2014 19:23, Mark Rutland mark.rutl...@arm.com wrote:
Hi Ard,
On Wed, Oct 08, 2014 at 03:11:27PM +0100, Ard Biesheuvel wrote:
After the EFI stub has done its business, it jumps into the kernel by
branching to
On 10 October 2014 12:49, Mark Rutland mark.rutl...@arm.com wrote:
On Thu, Oct 09, 2014 at 08:03:52PM +0100, Ard Biesheuvel wrote:
On 9 October 2014 19:23, Mark Rutland mark.rutl...@arm.com wrote:
Hi Ard,
On Wed, Oct 08, 2014 at 03:11:27PM +0100, Ard Biesheuvel wrote:
After the EFI stub
On Fri, Oct 10, 2014 at 12:52:32PM +0100, Ard Biesheuvel wrote:
On 10 October 2014 12:49, Mark Rutland mark.rutl...@arm.com wrote:
On Thu, Oct 09, 2014 at 08:03:52PM +0100, Ard Biesheuvel wrote:
On 9 October 2014 19:23, Mark Rutland mark.rutl...@arm.com wrote:
Hi Ard,
On Wed, Oct 08,
On Fri, Oct 10, 2014 at 02:27:46PM +0100, Ard Biesheuvel wrote:
On 10 October 2014 15:03, Mark Rutland mark.rutl...@arm.com wrote:
[...]
But if the EFI loader is allowed to load stext at the precise start of
RAM (or anywhere not in the idmap), in attempting the copy we'd try to
On Fri, Oct 10, 2014 at 11:37:03AM +0100, Ard Biesheuvel wrote:
On 10 October 2014 12:33, Mark Rutland mark.rutl...@arm.com wrote:
Hi Ard,
On Fri, Oct 10, 2014 at 10:25:24AM +0100, Ard Biesheuvel wrote:
Position independent AArch64 code needs to be linked and loaded at the same
relative
On Fri, 2014-10-10 at 08:30 +0200, Ard Biesheuvel wrote:
On 10 October 2014 01:20, Roy Franz roy.fr...@linaro.org wrote:
On Thu, Oct 9, 2014 at 3:19 PM, Mark Salter msal...@redhat.com wrote:
On Thu, 2014-10-09 at 21:03 +0200, Ard Biesheuvel wrote:
On 9 October 2014 19:23, Mark Rutland
On 10 October 2014 16:14, Mark Salter msal...@redhat.com wrote:
On Fri, 2014-10-10 at 08:30 +0200, Ard Biesheuvel wrote:
On 10 October 2014 01:20, Roy Franz roy.fr...@linaro.org wrote:
On Thu, Oct 9, 2014 at 3:19 PM, Mark Salter msal...@redhat.com wrote:
On Thu, 2014-10-09 at 21:03 +0200,
On 10 October 2014 16:09, Mark Rutland mark.rutl...@arm.com wrote:
On Fri, Oct 10, 2014 at 11:37:03AM +0100, Ard Biesheuvel wrote:
On 10 October 2014 12:33, Mark Rutland mark.rutl...@arm.com wrote:
Hi Ard,
On Fri, Oct 10, 2014 at 10:25:24AM +0100, Ard Biesheuvel wrote:
Position
On Fri, Oct 10, 2014 at 03:50:49PM +0100, Ard Biesheuvel wrote:
On 10 October 2014 16:09, Mark Rutland mark.rutl...@arm.com wrote:
On Fri, Oct 10, 2014 at 11:37:03AM +0100, Ard Biesheuvel wrote:
On 10 October 2014 12:33, Mark Rutland mark.rutl...@arm.com wrote:
Hi Ard,
On Fri, Oct
On Fri, Oct 10, 2014 at 6:27 AM, Ard Biesheuvel
ard.biesheu...@linaro.org wrote:
On 10 October 2014 15:03, Mark Rutland mark.rutl...@arm.com wrote:
[...]
But if the EFI loader is allowed to load stext at the precise start of
RAM (or anywhere not in the idmap), in attempting the copy we'd
Hi Matt,
1. Why x86 code isn't separated to another patch?
2. drivers/firmware/efi/reboot.c: efi_reboot():
One shouldn't use printk() with no KERN_* stuff passed into it.
I'd recommend to use pr_info() macro or something like that.
--
To unsubscribe from this list: send the line unsubscribe
On Fri, Oct 10, 2014 at 3:37 AM, Ard Biesheuvel
ard.biesheu...@linaro.org wrote:
On 10 October 2014 12:33, Mark Rutland mark.rutl...@arm.com wrote:
Hi Ard,
On Fri, Oct 10, 2014 at 10:25:24AM +0100, Ard Biesheuvel wrote:
Position independent AArch64 code needs to be linked and loaded at the
On 10 October 2014 17:55, Roy Franz roy.fr...@linaro.org wrote:
On Fri, Oct 10, 2014 at 3:37 AM, Ard Biesheuvel
ard.biesheu...@linaro.org wrote:
On 10 October 2014 12:33, Mark Rutland mark.rutl...@arm.com wrote:
Hi Ard,
On Fri, Oct 10, 2014 at 10:25:24AM +0100, Ard Biesheuvel wrote:
On 10 October 2014 17:38, Roy Franz roy.fr...@linaro.org wrote:
On Fri, Oct 10, 2014 at 6:27 AM, Ard Biesheuvel
ard.biesheu...@linaro.org wrote:
On 10 October 2014 15:03, Mark Rutland mark.rutl...@arm.com wrote:
[...]
But if the EFI loader is allowed to load stext at the precise start of
Change our PE/COFF header to use the minimum file alignment of
512 bytes (0x200), as mandated by the PE/COFF spec v8.3
Also update the linker script so that the Image file itself is also a
round multiple of FileAlignment.
Signed-off-by: Ard Biesheuvel ard.biesheu...@linaro.org
---
Another one
On Fri, Oct 10, 2014 at 9:58 AM, Ard Biesheuvel
ard.biesheu...@linaro.org wrote:
Change our PE/COFF header to use the minimum file alignment of
512 bytes (0x200), as mandated by the PE/COFF spec v8.3
Also update the linker script so that the Image file itself is also a
round multiple of
On Tue, Oct 07, 2014 at 03:42:31PM +0100, Matt Fleming wrote:
From: Matt Fleming matt.flem...@intel.com
The EFI capsule mechanism allows data blobs to be passed to the EFI
firmware. This patch just introduces the main infrastruture for
interacting with the firmware.
Once a capsule has
24 matches
Mail list logo
