Thanks for your replies. I will use %lx instead.
Regards,
Stefan
From: Andrew Fish [mailto:af...@apple.com]
Sent: Friday, October 17, 2014 5:06 PM
To: edk2-devel@lists.sourceforge.net
Subject: Re: [edk2] Print(L"0x%.16x", Value) not working as expected
On Oct 17, 2014, at 3:22 AM,
stefan.kae...
Here are Windows hosted gcc tool chains for EDK2 builds:
https://sourceforge.net/projects/edk2developertoolsforwindows/files/
I will add more readme files tomorrow.
The tools build IA32, X64, IPF, ARM, and AARCH64 from Windows. X64
builds are well tested. I have not yet boot tested IA32 builds b
Olivier,
Thanks for your contribution.
I will review it and if no problem I will help check it in.
Thanks
Feng
From: Olivier Martin [mailto:olivier.mar...@arm.com]
Sent: Tuesday, October 21, 2014 01:09
To: Tian, Feng
Cc: edk2-devel@lists.sourceforge.net
Subject: [PATCH] MdeModulePkg/PartitionDx
Hello,
We have found an issue with
MdeModulePkg/Universal/ReportStatusCodeRouter/RuntimeDxe/ReportStatusCodeRouterRuntimeDxe.c.
Specifically, we have a callback that is triggered on a timer that attempts to
call ReportStatusCode(). However, when serial debug output is enabled, most of
the time
Dear MdeModulePkg maintainer,
Please find the attached patch that fixes El Torito format on media that do
not have a 2KB block size.
El Torito format can be used on different media (eg: USB).
A ISO image can be dumped onto a USB mass-storage.
These media might not have the same block s
> On Oct 20, 2014, at 9:27 AM, Ard Biesheuvel wrote:
>
>> Thanks for your reply.
>>
>> However, the question was about write-protected and execute-protected
>> data. While the UEFI spec describes those bits, it is unclear to me if
>> I can legally map the runtime code sections as read-only and
On 20 October 2014 18:25, Ard Biesheuvel wrote:
> On 20 October 2014 18:16, Andrew Fish wrote:
>>
>>> On Oct 20, 2014, at 4:36 AM, Ard Biesheuvel
>>> wrote:
>>>
>>> Hello all,
>>>
>>> I am currently investigating what would be the best way to make sure
>>> Runtime Services regions are never map
On 20 October 2014 18:16, Andrew Fish wrote:
>
>> On Oct 20, 2014, at 4:36 AM, Ard Biesheuvel
>> wrote:
>>
>> Hello all,
>>
>> I am currently investigating what would be the best way to make sure
>> Runtime Services regions are never mapped both writable and executable
>> by the arm64 Linux kern
> On Oct 20, 2014, at 4:36 AM, Ard Biesheuvel wrote:
>
> Hello all,
>
> I am currently investigating what would be the best way to make sure
> Runtime Services regions are never mapped both writable and executable
> by the arm64 Linux kernel, as a security enhancement. This is
> especially impo
On Sun, Oct 19, 2014 at 05:20:45PM -0700, Jordan Justen wrote:
> On 2014-10-17 10:03:58, Anthony PERARD wrote:
> > This is a bus-like on top of XenStore. It will look for advertised
> > ParaVirtualized devices and initialize them by producing XenBus
> > protocol.
> >
> > Origin: FreeBSD 10.0
> >
On Sun, Oct 19, 2014 at 05:00:13PM -0700, Jordan Justen wrote:
> On 2014-10-17 10:03:51, Anthony PERARD wrote:
> > This patch is inspired by InterlockedCompareExchange32 from the
> > BaseSynchronizationLib.
>
> Why not attempt to add it to BaseSynchronizationLib?
The BaseSynchronizationLib have a
On Sun, Oct 19, 2014 at 04:27:11PM -0700, Jordan Justen wrote:
> On 2014-10-17 10:03:46, Anthony PERARD wrote:
> > This includes Component Name and Driver Binding.
> >
> > Contributed-under: TianoCore Contribution Agreement 1.0
> > Signed-off-by: Anthony PERARD
> > Reviewed-by: Konrad Rzeszutek W
On Sun, Oct 19, 2014 at 04:47:32PM -0700, Jordan Justen wrote:
> On 2014-10-17 10:03:45, Anthony PERARD wrote:
> > This patch imports publics headers in order to use features from Xen
> > like XenStore, PV Block... There is only the necessary header files and
> > there are only a few modifications
Hello all,
I am currently investigating what would be the best way to make sure
Runtime Services regions are never mapped both writable and executable
by the arm64 Linux kernel, as a security enhancement. This is
especially important under kexec, as the UEFI memory ranges may
survive many reboots.
Hi, experts:
I am studying Intel 64 and IA-32 Architectures Software Developer's
Manual Volume 3A.pdf .
I have a few questions about Multi-processor management.
1. 7.5 Multi-processor initialization In Chapter 7
..
The mechanism for carrying out the MP initialization protocol diffe
15 matches
Mail list logo