is CONFIG_COREINFO_SECONDARY_PAYLOAD supposed to work?
I tried to add this option in kconfig, but the coreboot table is flushed. I
tried to fix it. But it seems to be hard. Anyone got idea? Or I have to work
really hard to fix it? :(
Zheng
Date: Sun, 20 Mar 2016 20:07:34 -0700
From: nochristrequi...@gmail.com
To: rminn...@gmail.com
Subject: Re: [coreboot] Multiple payloads support?
CC: coreboot@coreboot.org; stefan.reina...@coreboot.org; fishb...@hotmail.com
I should have been more clear - first build your image using the coreboot build
system and specify SeaBIOS as your payload. Then compile coreinfo. Last,
include coreinfo in your image using the command I provided in the previous
e-mail.
Coreinfo will now show up as a boot option under SeaBIOS. This is how I do it -
no need to mess with bayou. Works with memtest and other elf binaries as well.
Good luck!
On Sun, Mar 20, 2016 at 7:59 PM, Nick <nochristrequi...@gmail.com> wrote:
Bayou is not necessary - use SeaBIOS to run coreinfo.
./build/cbfstool ./build/coreboot.rom add-payload -f
/gitrepo/coreboot/payloads/coreinfo/build/coreinfo.elf -n img/coreinfo.elf -t
payload
On Sun, Mar 20, 2016 at 7:02 PM, ron minnich <rminn...@gmail.com> wrote:
it's a bit of work but I got it to build two years ago.
ron
On Sun, Mar 20, 2016 at 6:56 PM Zheng Bao <fishb...@hotmail.com> wrote:
But Bayou seems to be dead. It can not be built. The definition like "struct
LAR" goes nowhere.
Zheng
From: rminn...@gmail.com
Date: Sun, 20 Mar 2016 21:17:24 +0000
To: fishb...@hotmail.com; coreboot@coreboot.org; stefan.reina...@coreboot.org
Subject: Re: [coreboot] Multiple payloads support?
It was done about 10 years ago and it was called bayou. Take a look in the
libpayload side.
On Sat, Mar 19, 2016 at 11:30 PM Zheng Bao <fishb...@hotmail.com> wrote:
Hi, all,
I am trying to integrate SeaBIOS and another payload(coreinfo, nvramcui)
into final image.
After a quick code checking, current code in repo does not support multiple
payload, does it?
I want to let Coreboot load and run nvramcui first. The user can decide to
change the
CMOS setting or not. If user want to save the setting, the system need to
reboot. If user wants
to give up the change, the system goes out of the nvramcui and goes into
SeaBIOS. Just like
other IBV's BIOS.
Did anyone do this job before? Any suggestion?
Zheng
--
coreboot mailing list: coreboot@coreboot.org
https://www.coreboot.org/mailman/listinfo/coreboot
--
coreboot mailing list: coreboot@coreboot.org
https://www.coreboot.org/mailman/listinfo/coreboot
--
coreboot mailing list: coreboot@coreboot.org
https://www.coreboot.org/mailman/listinfo/coreboot
--
coreboot mailing list: coreboot@coreboot.org
https://www.coreboot.org/mailman/listinfo/coreboot
--
coreboot mailing list: coreboot@coreboot.org
https://www.coreboot.org/mailman/listinfo/coreboot
