Hi Gabe, On 17/11/11 11:27, Gabe Black wrote: > Add a target for running u-boot as a coreboot payload in boards.cfg. > > Signed-off-by: Gabe Black <gabebl...@chromium.org> > --- > Changes in v2: > Change capitalization of the x86 tag. > > Changes in v3: > Move the Signed-off-by line up. > > Changes in v4: > Change the summary tag style. > > boards.cfg | 1 + > 1 files changed, 1 insertions(+), 0 deletions(-) > > diff --git a/boards.cfg b/boards.cfg > index 8b7a03b..4b2a1a7 100644 > --- a/boards.cfg > +++ b/boards.cfg > @@ -272,6 +272,7 @@ tcm-bf518 blackfin blackfin > tcm-bf537 blackfin blackfin > eNET x86 x86 eNET - > sc520 eNET:SYS_TEXT_BASE=0x38040000 > eNET_SRAM x86 x86 eNET - > sc520 eNET:SYS_TEXT_BASE=0x19000000 > +coreboot-x86 x86 x86 coreboot > chromebook-x86 coreboot coreboot:SYS_TEXT_BASE=0xFC0000 > sandbox sandbox sandbox sandbox > sandbox - > cobra5272 m68k mcf52x2 cobra5272 - > idmr m68k mcf52x2
As mentioned by others before, there is no reason to have these as discrete patches - Please merge into a single 'Add coreboot payload' Is there any real reason to reference 'chromebook-x86'? And finally, what is the plan for motherboard specific coreboot variants? Regards, Graeme _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
