Greetings,
What is the status of native raminit on haswell? It's the first generation
that doesn't have a native implementation.
I did find some seemingly successful past work [1] but what happened to it?
Did it run into a blocker issue or was it just abandoned in favor of other
priorities?
[1]
Thanks a lot to everyone (also the OpenBIOS project people) who helped me and contributed to guide me up to here!Regards,Bernd___
coreboot mailing list -- coreboot@coreboot.org
To unsubscribe send an email to coreboot-le...@coreboot.org
# 9 November 2021 - coreboot EFI working group
Attendees: Martin Roth, Felix Held, Michael Niewöhner, Matt DeVillier, Nate
DeSimone, Patrick Georgi, Tim Crawford, Werner Zeh
## Agenda:
* [Edward] Supporting some UEFI interfaces continues to be a hot topic, one
such area is ESRT table ASL gener
On Wed, Nov 10, 2021 at 11:39 AM bernd...@web.de wrote:
> So if I got it right maybe I've installed the wrong python version.
Since coreboot did seem to build, I believe you installed the correct
version. I don't believe SeaBIOS requires python to actually run, only
to compile.
> Anyway, I see t
Hi. When installing python I did:
$ apt-get install python
or
$ sudo apt-get install python
I don't remember.
So if I got it right maybe I've installed the wrong python version.
Anyway, I see the output (probably of coreboot) in the original terminal window
and the output (probably of SeaBIOS)
> /bin/sh: 1: python: not found
> make[2]: *** [Makefile:168: out/romlayout16.lds] Error 127
I ran in to this error the other day in a clean build environment and
was going to mention it in the thread about python in the build
system, but Peter Surge already commented here on it.
If you are on Ub
On Wed, Nov 10, 2021 at 2:05 AM bernd...@web.de wrote:
> I see something like:
>
> The command 'qemu-system-x86_64' wasn't found, but can be installed with:
> sudo apt install qemu-system-x86 # version 1:4.2-3ubuntu6.18, or
> sudo apt install qemu-system-x86-xen # version 1:4.2-3ubuntu6.18
Well,
Sorry. For some reason (maybe because of putting these characters '<' '>' around the text) it wasn't transmitted that I'm there:Step 8 - Run QEMURegards,Bernd Originalnachricht Betreff: [coreboot] Re: Installing coreboot with SeaBIOSVon: Nicholas An: bernd...@web.deCc: coreboot@core
Am 10.11.21 um 10:43 schrieb Nico Huber:
Hi Julian,
Am 10.11.21 um 10:02 schrieb Julian Stecklina:
CBFS: Found 'fallback/romstage' @0x80 size 0x3ba0 in mcache @0x00014e2c
WARN - MOVS to ROM at RIP dc2f RCX ee8 ff200300->ff200300
The warning is from us. Improvising a stack trace at this poi
Hi Julian,
Am 10.11.21 um 10:02 schrieb Julian Stecklina:
CBFS: Found 'fallback/romstage' @0x80 size 0x3ba0 in mcache @0x00014e2c
WARN - MOVS to ROM at RIP dc2f RCX ee8 ff200300->ff200300
The warning is from us. Improvising a stack trace at this point yields:
cbfs_prog_stage_load -> cbfs_l
Hi. I'm there:https://doc.coreboot.org/tutorial/part1.htmlI did:$ qemu-system-x86_64 -bios build/coreboot.rom -serial stdioI see something like:The command 'qemu-system-x86_64' wasn't found, but can be installed with:sudo apt install qemu-system-x86 # version 1:4.2-3ubuntu6.18, orsudo apt ins
Hi Patrick,
On Tue, 2021-11-09 at 17:43 +, Patrick Georgi via coreboot wrote:
>
> Is there any particular concern with having coreboot in that memory region on
> your platform that makes you ask this or is this just some general curiosity?
Thanks for confirming that we are not doing anything
12 matches
Mail list logo