All of lore.kernel.org
 help / color / mirror / Atom feed
From: Graeme Russ <graeme.russ@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v4 1/5] x86: Add a target for running as a coreboot payload
Date: Thu, 17 Nov 2011 20:43:52 +1100	[thread overview]
Message-ID: <4EC4D758.7090306@gmail.com> (raw)
In-Reply-To: <1321489672-6191-2-git-send-email-gabeblack@chromium.org>

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 <gabeblack@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

  reply	other threads:[~2011-11-17  9:43 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-17  0:27 [U-Boot] [PATCH v4 0/5] Add a coreboot board, CPU, and configuration, and target Gabe Black
2011-11-17  0:27 ` [U-Boot] [PATCH v4 1/5] x86: Add a target for running as a coreboot payload Gabe Black
2011-11-17  9:43   ` Graeme Russ [this message]
2011-11-17 10:11     ` Gabe Black
2011-11-17 10:26       ` Graeme Russ
2011-11-17 12:33         ` Alan Carvalho de Assis
2011-11-17 21:31         ` Gabe Black
2011-11-17  0:27 ` [U-Boot] [PATCH v4 2/5] x86: Add a basic implementation for a coreboot board Gabe Black
2011-11-17  0:27 ` [U-Boot] [PATCH v4 3/5] x86: Add a preliminary coreboot configuration header Gabe Black
2011-11-17  0:27 ` [U-Boot] [PATCH v4 4/5] x86: Add an implementation for a coreboot CPU Gabe Black
2011-11-17  0:27 ` [U-Boot] [PATCH v4 5/5] x86: Make the serial port work for the coreboot board Gabe Black

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4EC4D758.7090306@gmail.com \
    --to=graeme.russ@gmail.com \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.