Hello
I got it working. Thanks for the help. I used the code from the book with
the uefi.h include and I modeled the .inf file from the samplehelloapp in
the edk2. The only problem was using the webpage to generate the guid. I
don't know if that line was meant to generate a guid or simply use
On Jan 30, 2014, at 3:20 PM, John Davis wrote:
> Yeah, I don't think this code will build. I understand what you guys were
> telling me about it being a higher abstraction. Kind of like programming in
> Xt versus programming in Motif but when I try to massage it into building it
> does not wo
Yeah, I don't think this code will build. I understand what you guys were
telling me about it being a higher abstraction. Kind of like programming in
Xt versus programming in Motif but when I try to massage it into building
it does not work. It complains about not being able to find efi.h. I did
On 2014-01-30 06:36:08, Wei Liu wrote:
> On Wed, Jan 29, 2014 at 02:45:55PM -0800, Jordan Justen wrote:
> > This is a subset of the current ovmf-s3 branch at:
> > https://github.com/jljusten/edk2.git
> >
> > The goal is to bring the Xen boot path back together with
> > the QEMU boot path as much a
Hello Andrew,
It kind of looks like the one you show. Kind of.
For reference here it is
--
#include "efi.h"
EFI_STATUS InitializeHelloApplication( IN EFI_HANDLE ImageHandle, IN
EFI_SYSTEM_TABLE *SystemTable) {
UINTN Index;
SystemTable->ConOut->OutputString(SystemTable->ConOut,L"He
Hello Laurie,
Thank you for letting me know the source is still valid. I'll look at the
references you provided to see if I can get it working. I do have that
massive 400+ page pdf and I have built the emulator. It just takes a while
to dig though. It seems the answer is in there, I just haven'
Another comment the “Beyond BIOS” book Helloworld,c could be used in any UEFI
|EFI system. This is because it is using the UEFI Services directly for
ConOut and ConIn. In contrast, the AppPkg\Applications\Hello would need the
EDK II library UefiLib compiled with it and it also has a dependen
On Jan 30, 2014, at 12:38 PM, John Davis wrote:
> Hello
>
> I'm reading the Beyond Bios book in conjunction with the stuff on tianocore.
> The example code in chapter 4 of that book talks about a HelloApplication.
> The format looks different from the sample code in AppPkg\Hello directory o
The Hello in the AppPkg\Applications\Hello\ uses the “Print” function that is
part of the UefiLib Library. While the Helloworld.c in the Beyond BIOS book is
making a call using the EFI_SERVICES SystemTable pointer that is passed into
its entry point.
Both are correct and both are current.
For w
Hello
I'm reading the Beyond Bios book in conjunction with the stuff on
tianocore. The example code in chapter 4 of that book talks about a
HelloApplication. The format looks different from the sample code in
AppPkg\Hello directory of the EDK2 src. Is that format/api shown in the
book obsolete?
On Wed, Jan 29, 2014 at 02:45:55PM -0800, Jordan Justen wrote:
> This is a subset of the current ovmf-s3 branch at:
> https://github.com/jljusten/edk2.git
>
> The goal is to bring the Xen boot path back together with
> the QEMU boot path as much as possible. This will allow
> the rest of S3 suppor
On Wed, Jan 29, 2014 at 01:59:58PM -0800, Jordan Justen wrote:
> Whoops. Looks like I also submitted a patch for the
> missing s on BaseTools.
>
> On 2014-01-29 08:50:50, Leif Lindholm wrote:
> > Actually, there is another issue with the new edksetup.sh - it returns
> > success
> > (0) regardless
Liming,
I didn't hit any issue with that code, but have been trying to work out the
reason of the compilation error.
As UnicodeFiFoRemoveOneKey() is called only when FIFO buffer is not empty,
should the obsolete code be removed & the function's return type changed to
VOID?
Do you plan to impleme
13 matches
Mail list logo
