On Nov 26, 2012, at 10:54 PM, Ramesh Raju wrote:
> All,
>
>Whenever protocol installed we have RegisterProtocolNotify function to get
> the Callback. I don’t see any notification event if the protocol is
> uninstalled. Is there any reason for that?
It is functioning as intended. Register
On Nov 27, 2012, at 9:21 AM, James White wrote:
> Hi Andrew
>
> Thanks for your reply. Great help.
>
> I currently have the problem that I'm trying to split SEC from PEI/DXE/BDS. I
> load the Sec module into a read-only ROM. The ROM is memory-mapped at 0x0
> (this is specific to my platform).
Committed in r13967-13969.
I made a minor change in 2/3 to add typecasts to BochsWrite calls for VS2012.
Thanks for the contribution!
-Jordan
On Fri, Nov 23, 2012 at 7:53 AM, Gerd Hoffmann wrote:
> From: Gerd Hoffmann
>
>
> Hi,
>
>
>
> This patch series adds support for the bochs dispi inte
On 11/27/2012 10:44 AM, Andrew Fish wrote:
> The edk2 build system produces a command line tool called VolInfo that
> dumps FVs. It does not disassemble code, but it will show you the layout.
>
> The FD layout is defined in the platforms .FDF file. Look in the [FD.*]
> sections. So for example:
> h
Hi Andrew
Thanks for your reply. Great help.
I currently have the problem that I'm trying to split SEC from PEI/DXE/BDS. I
load the Sec module into a read-only ROM. The ROM is memory-mapped at 0x0 (this
is specific to my platform).
When I disassemble Sec/Sec/OUTPUT/SecEntryPoint.obj I can see
The edk2 build system produces a command line tool called VolInfo that dumps
FVs. It does not disassemble code, but it will show you the layout.
The FD layout is defined in the platforms .FDF file. Look in the [FD.*]
sections. So for example:
https://edk2.svn.sourceforge.net/svnroot/edk2/trunk
Is there a way that I can disasseble my generated UEFI binary (in my case
FV/SEC_RTSM_VE_CORTEX-A15_MPCORE_EFI.fd) so that I can see the exact
instructions that are being run once the firmware is executed from ROM?
Is there documentation about the format of that .fd? In my case I only have the
I can make my own copy if I will not agree :)
On 27.11.2012, at 11:53, Tian, Feng wrote:
> Ok, here assertions are mainly used to ensure there is no over boundary.
>
> If there is no big functionality impact or defect, we prefer to not change
> it. Do you agree?J
>
> Thanks
> Feng
>
> From