Hi Simon,
thanks for helping, please find my reply below.
On 21 August 2015 at 23:51, Simon Glass s...@chromium.org wrote:
Note that once you call exit_boot_services you will not be able to use
the console. Be careful here - the board may appear to hang but
actually it is broken by you trying
Hi Bin, Simon,
On 18 August 2015 at 15:47, Stoppa, Igor igor.sto...@intel.com wrote:
Hi,
I have verified that I can reproduce a working build of U-Boot as
x86-64bit EFI payload for Qemu: I can boot it, interact with various
filesystems of both real and emulated disks, etc.
Now I would
Hi again,
On 20 August 2015 at 12:44, Stoppa, Igor igor.sto...@intel.com wrote:
It happens much earlier than I thought: I was expecting it would get
stuck during the handover from the stub to the real U-Boot, after the
jump_to_uboot call, instead it never reaches that point.
Now I am able
Hi,
I have verified that I can reproduce a workign build of U-Boot as
x86-64bit EFI payload for Qemu: I can boot it, interact with various
filesystems of both real and emulated disks, etc.
Now I would like to build and boot it for a real board, still as EFI payload.
The docs/README.efi file
On 17 August 2015 at 10:48, Bin Meng bmeng...@gmail.com wrote:
Hi Igor,
On Mon, Aug 17, 2015 at 3:10 PM, Stoppa, Igor igor.sto...@intel.com wrote:
[...]
One other thing that I haven't fully investigated yet (so maybe it's
already explained elsewhere) is: after the application/payload
On 17 August 2015 at 12:48, Stoppa, Igor igor.sto...@intel.com wrote:
I'm referring to this:
http://www.denx.de/wiki/view/DULG/UBootEnvVariables
I thought it would become a partition, but maybe I've assumed too much
and it is implemented in some other way?
ah, I see now that I should use
Hello Bin,
a couple more of last-minute comments below:
On 15 August 2015 at 04:44, Bin Meng bmeng...@gmail.com wrote:
+For building an EFI payload, run:
make qemu-x86_defconfig
Since qemu-x86_defconfig was an example, maybe this could be written as:
make selected defconfig, i.e.
Hi Bin,
On 14 August 2015 at 13:30, Bin Meng bmeng...@gmail.com wrote:
I reread the doc and found the only thing that confused you is 'make
menuconfig'. Actually it is not needed as the build step of EFI
application and payload is pretty clear.
Please notice also that not all the options
Hi Bin,
On 14 August 2015 at 13:47, Bin Meng bmeng...@gmail.com wrote:
The doc has a misleading 'make menuconfig' when building the EFI
application and payload. Clarify this and also update information
on test with QEMU.
Signed-off-by: Bin Meng bmeng...@gmail.com
---
doc/README.efi | 28
Hi Bin, Simon,
thanks for your time, unfortunately I'm still having issues, please see below.
On 14 August 2015 at 05:09, Bin Meng bmeng...@gmail.com wrote:
I am using QEMU 2.3.0 (built from source) and EFI BIOS (IA32 and X64,
built from git source)
I downloaded and built the latest stable
Hi Bin,
going back to the ml thread for closure
On 14 August 2015 at 12:34, Bin Meng bmeng...@gmail.com wrote:
I will send it to you offline.
That one worked on my qemu setup.
So I used the instructions from your patch to the README.efi
for replicating it.
* I copied qemu-x86_defconfig to
Hi Bin,
On 14 August 2015 at 15:15, Bin Meng bmeng...@gmail.com wrote:
These are Kconfig options. I am not sure what makes you think they are binary?
Binary as commented out vs set to y
That might be inferred from the doc, when it is said to set a certain option.
So one might just try to
Hi Bin,
On 14 August 2015 at 15:34, Bin Meng bmeng...@gmail.com wrote:
Hi Igor,
On Fri, Aug 14, 2015 at 7:46 PM, Stoppa, Igor igor.sto...@intel.com wrote:
[...]
I'm still not sure I got that right, even after consulting the EFI specs.
It is already documented, see section Inner workings
Hi Bin,
On 14 August 2015 at 15:54, Bin Meng bmeng...@gmail.com wrote:
Hi Igor,
On Fri, Aug 14, 2015 at 8:46 PM, Stoppa, Igor igor.sto...@intel.com wrote:
[...]
Yes, I did read it. That section is - unsurprisingly - written from
the perspective of a U-Boot developer/user.
Yes
Hi Bin,
On 13 August 2015 at 15:37, Bin Meng bmeng...@gmail.com wrote:
x86 architecture --- Mainboard vendor --- efi
x86 architecture --- Mainboard model --- efi
These two should not be changed for EFI payload. What you selected is
for EFI application.
Thanks a lot. Now it built.
If
Hello,
I'm using the HEAD of the master branch from git://git.denx.de/u-boot-x86.git
I want to build U-Boot as 64bit EFI payload.
According to docs/README.efi, I've done the following:
u-boot-x86 make qemu-x86_defconfig
u-boot-x86 make menuconfig
x86 architecture --- Mainboard vendor --- efi
On 13 August 2015 at 15:57, Bin Meng bmeng...@gmail.com wrote:
Hi Igor,
On Thu, Aug 13, 2015 at 7:00 PM, Igor Stoppa igor.sto...@intel.com wrote:
[...]
+In this case, known as bare mode, fom the fact that it runs on the
fom?
argh, sorry, fixed
+'bare metal', U-Boot acts like a BIOS
Hi Bin,
On 13 August 2015 at 15:46, Stoppa, Igor igor.sto...@intel.com wrote:
for EFI application.
Thanks a lot. Now it built.
It built, but I didn't get much further :-(
I'm running qemu 2.1.3 on OpenSUSE and it doesn't seem to start in EFI
mode other than with a build of the Open Virtual
+Simon
Hello Bin, Simon,
On 13 August 2015 at 17:52, Stoppa, Igor igor.sto...@intel.com wrote:
I'm running qemu 2.1.3 on OpenSUSE and it doesn't seem to start in EFI
mode other than with a build of the Open Virtual Machine Firmware that
I found googling [1]. With this I can reach an EFI
Hi Bin Meng,
thanks for your reply, please find few comments inlined below.
On 11 August 2015 at 17:09, Bin Meng bmeng...@gmail.com wrote:
Hi Igor,
On Tue, Aug 11, 2015 at 9:18 PM, Stoppa, Igor igor.sto...@intel.com wrote:
U-Boot supports running bare-metal as well as being loaded
Explicitly list the targets supported in each section of the
instructions
from the x86 README.
---
doc/README.x86 | 17 ++---
1 file changed, 10 insertions(+), 7 deletions(-)
diff --git a/doc/README.x86 b/doc/README.x86
index af2459c..1105afe 100644
--- a/doc/README.x86
+++
Hi Bin,
On 12 August 2015 at 13:59, Bin Meng bmeng...@gmail.com wrote:
+Simon.
Hi Igor,
On Wed, Aug 12, 2015 at 6:41 PM, Stoppa, Igor igor.sto...@intel.com wrote:
Explicitly list the targets supported in each section of the
instructions
from the x86 README.
Please add Signed-off
Hi Simon,
On 12 August 2015 at 16:31, Simon Glass s...@chromium.org wrote:
I prefer 'bare mode' to 'raw mode'. It suggests that U-Boot is running
on the bare metal. Perhaps we should drop the word 'raw' and use
'bare' instead, for consistency?
Yes, I could do it for the entire doc, if this
Hi Bin,
On 12 August 2015 at 16:27, Bin Meng bmeng...@gmail.com wrote:
Hi Igor,
On Wed, Aug 12, 2015 at 8:20 PM, Igor Stoppa igor.sto...@intel.com wrote:
Explicitly list the targets supported in each section of the instructions
from the x86 README.
Nits: we should put tags in the
Hello,
I have read the documentation coming with u-boot and several other
links that I got from Google, but I am still confused on certain
items.
I'll gladly provide patches for enhancing the documentation, if anyone
can help me
to understand better.
My impression is that the typical way of
25 matches
Mail list logo
