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 Wilk
>
> ---
> Change in V3:
> - enable compilation for Ia32 and Ia32X64
>
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 in order to facilitate future merge of
> more recent header (that would
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?
-Jordan
> The function will be used in the "OvmfPkg/XenBusDxe: Add Grant Table
> functions" patch.
>
> C
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
>
> License: This patch adds XenBus.c which is under the MIT licence.
>
> Cont
Hi, Jordan
I agree with Andrew. The best fix should be "movw %es, %ax"
I searched MdePkg and MdeModulePkg, looks like only DebugSupportDxe .S file has
such issue.
Is it possible to make a clean-up?
Best Regards
Feng
-Original Message-
From: Jordan Justen [mailto:jljus...@gmail.com]
> On Oct 19, 2014, at 4:47 PM, 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 in order
SourceLevelDebugPkg/DebugAgentLib x64 also used movw %es, %rax. We need to fix
it also.
And UefiCpuPkg/Library/CpuExceptionLib x64 usedmovl%es, %eax. We could
clean it to make a consistence in code base.
-Original Message-
From: Tian, Feng [mailto:feng.t...@intel.com]
Sent: Mon
Hi All,
I am trying to implement a non-volatile variable storage at the top end of
an eMMC flash device. From all the reading, I have implemented that
firmware volume block protocol.
What I can't figure is, what kind of device path do I install along with
FVB protocol ?
Thanx.
---