[LinuxBIOS] [PATCH][v3] Support for multiple LinuxBIOS payloads

Carl-Daniel Hailfinger c-d.hailfinger.devel.2006 at gmx.net
Wed Aug 29 16:36:40 CEST 2007

On 29.08.2007 09:21, Stefan Reinauer wrote:
> * Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006 at gmx.net> [070828 01:01]:
>> On 19.08.2007 20:14, Uwe Hermann wrote:
>>>  - Payload files must be named 'payload[0-9]', i.e. payload0, payload1, etc.
>>>    Actually, you can specify the prefix (e.g. 'payload') via Kconfig.
>> Can we tell the implementation in some way that we'd like it to ignore
>> payloads with numbers before x?
> Seems simple, but why?

Ability to modify boot order without reflashing. But this could be
accomplished with the "next payload" selection via CMOS.

>>>  - All payload files must be in the same target directory (which can be
>>>    specified via Kconfig).
>> I'd like not to introduce/keep such limitations.
> I think this is merely a practical issue as Kconfig is not that
> flexible.

OK, as long as the lar can be populated without the help of Kconfig.

>> Can one payload decide which payload to run next? For example, lbmenu
>> might want to make sure the netboot payload is run instead of FILO.
> I suggest that LinuxBIOS decides via the CMOS or some similar mechanism
> (LBtable?) which payload to run next. This should be a mechanism that
> LinuxBIOS and the payload can modify.



More information about the coreboot mailing list