Thanks for the help, Andrew and Jaben! When I'm back at my office
tomorrow, I'll try loading those two items and let everyone know if it
worked. If it doesn't work, I'll just have to require that users have UEFI
2.1+.
Thomas Rognon
On Tue, Mar 12, 2013 at 4:38 PM, Andrew Fish wrote:
> So Hii
On 03/12/13 21:45, Duane Voth wrote:
> Yes, Intel 3.5 drivers installed: edk2\Intel3.5\EFIX64\* (Build won't
> work without them). Yes e1000 speced on qemu command line:
>
> qemu-system-x86_64 -serial file:con.out -hda ovmf.disk -uuid
> 71656d75-5f64-7561-6e65-5f3030303031 -device
> e1000,netde
Anyone seeing this?
Error validating server certificate for 'https://edk2.svn.sourceforge.net:443':
- The certificate is not issued by a trusted authority. Use the
fingerprint to validate the certificate manually!
Certificate information:
- Hostname: *.svn.sourceforge.net
- Valid: from Mon,
So Hii got added to UEFI 2.1, there was an older not backward compatible
version in the Intel Framework specs. The Framework specs eventually turned
into the PI specs.
So if a system is older than UEFI 2.1 then it will not have the Hii related
protocols.
It seems the newer shell and some of
Given the code in that constructor, I would say that you are EFI 2.0 compliant,
but that is not enough for this library. I copied the constructor below, which
just returns an error.
EFI_STATUS
EFIAPI
HandleParsingLibConstructor (
IN EFI_HANDLEImageHandle,
IN EFI_SYSTEM_TABLE *Syste
Awesome, thanks. I'll read those now.
Right now, one of my test machine is asserting after calling
HandleParsingLibConstructor. This machine has far fewer drivers than my
development machine, so I still haven't figured out what I'm missing yet.
Here's more detailed info:
Here is the debug outp
Yes, Intel 3.5 drivers installed: edk2\Intel3.5\EFIX64\* (Build won't
work without them). Yes e1000 speced on qemu command line:
qemu-system-x86_64 -serial file:con.out -hda ovmf.disk -uuid
71656d75-5f64-7561-6e65-5f3030303031 -device
e1000,netdev=net0,mac=52:54:00:12:34:03 -netdev
type=tap,id=
On Mar 12, 2013, at 1:07 PM, Thomas Rognon wrote:
> I'm interested in contributing my GUI framework as a edk2 subproject, but
> I'll have to clear that by my employer first. Also, I've never contributed
> to an open source project before, so I'm not sure how that process works.
>
The proces
Thomas,
The edk2 is an example of a UEFI implementation, but many can exist.
I think you should read UEFI 2.3.1 (http://www.uefi.org/specs/) section 2.6 to
understand what a UEFI system is required to do.
I'd also point that something like a Firmware Volume is not UEFI, but PI (UEFI
Platform
I'm interested in contributing my GUI framework as a edk2 subproject, but
I'll have to clear that by my employer first. Also, I've never contributed
to an open source project before, so I'm not sure how that process works.
On Tue, Mar 12, 2013 at 1:14 PM, Andrew Fish wrote:
> On Mar 12, 2013,
I haven't yet come across a computer that has all, or even most, of the
drivers included in edk2. This is a problem because my UEFI application
depends on some of these drivers.
I need to deploy my application as efi files and not interfere with the
vendor's firmware volumes, so creating my own f
http://www.reformasostenible.com/zpzlm/leiqr/njs
3/12/2013 8:05:47 PM
Nicola Johnsen--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
htt
The patch looks good.
Thanks,
-Erik
Reviewed-by: Erik Bjorge
From: Stanbro, Matthew A [mailto:matthew.a.stan...@intel.com]
Sent: Thursday, March 07, 2013 1:16 PM
To: edk2-devel@lists.sourceforge.net
Subject: [edk2] Copy Patch
Fixes bug in CP function to prevent copying of files if destination
On Mar 12, 2013, at 9:21 AM, Thomas Rognon wrote:
> I ran into the same issues and, as far as I could find out, UEFI provides
> nothing for user interface except the ability to transfer a pixel buffer to
> the screen. HII and VFR aren't user interface, they are just underlying
> structures th
The patch looks good.
Thanks,
-Erik
Erik Bjorge
From: Stanbro, Matthew A [mailto:matthew.a.stan...@intel.com]
Sent: Thursday, March 07, 2013 1:15 PM
To: edk2-devel@lists.sourceforge.net
Subject: [edk2] Help Patch
Rewrite's Help.c to call the ShellPrintHelp function. Adds a footer to the
botto
I ran into the same issues and, as far as I could find out, UEFI provides
nothing for user interface except the ability to transfer a pixel buffer to
the screen. HII and VFR aren't user interface, they are just underlying
structures that a user interface can be built upon. I ended up writing my
o
The README is rather extended than trimmed, so that users grepping for the
file name have a pointer.
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Laszlo Ersek
---
OvmfPkg/README|1 +
OvmfPkg/create-release.py |1 -
2 files changed, 1 insertions(+),
On 03/11/13 21:11, Duane Voth wrote:
> I can run OVMF without networking using qemu with no problem, and I have
> qemu with networking (using taps and a bridge) working properly, but
> when I use the network enabled OVMF.fd I get the blank vga console with
> no screen or network activity. OVFM.fd
Hi Everyone
After some research I did a sample application that loads a bmp image on
the screen using GOP. But now I have another question.
Some days ago someone send an e-mail to the group asking about resize vfr
fonts, and this person told that he was able to resize images, but not the
texts.
Th
19 matches
Mail list logo
