All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Rae <srae@broadcom.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/4] vexpress64: switch to generic board
Date: Fri, 26 Dec 2014 09:59:49 -0800	[thread overview]
Message-ID: <549DA215.8070308@broadcom.com> (raw)
In-Reply-To: <1419382966-8635-1-git-send-email-linus.walleij@linaro.org>

Acked-by: Steve Rae <srae@broadcom.com>

On 14-12-23 05:02 PM, Linus Walleij wrote:
> The few Versatile Express ARMv8 platforms we have may just as
> well be switched to generic board from the beginning.
>
> Tested on the ARM foundation model and the in progress support
> for the ARMv8 Juno board.
>
> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
> ---
>   include/configs/vexpress_aemv8a.h | 5 +++--
>   1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/include/configs/vexpress_aemv8a.h b/include/configs/vexpress_aemv8a.h
> index f3af971214a5..027d78b59171 100644
> --- a/include/configs/vexpress_aemv8a.h
> +++ b/include/configs/vexpress_aemv8a.h
> @@ -8,6 +8,9 @@
>   #ifndef __VEXPRESS_AEMV8A_H
>   #define __VEXPRESS_AEMV8A_H
>
> +/* We use generic board for v8 Versatile Express */
> +#define CONFIG_SYS_GENERIC_BOARD
> +
>   #ifdef CONFIG_BASE_FVP
>   #ifndef CONFIG_SEMIHOSTING
>   #error CONFIG_BASE_FVP requires CONFIG_SEMIHOSTING
> @@ -25,8 +28,6 @@
>
>   /*#define CONFIG_ARMV8_SWITCH_TO_EL1*/
>
> -/*#define CONFIG_SYS_GENERIC_BOARD*/
> -
>   #define CONFIG_SYS_NO_FLASH
>
>   #define CONFIG_SUPPORT_RAW_INITRD
>

  reply	other threads:[~2014-12-26 17:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-24  1:02 [U-Boot] [PATCH 2/4] vexpress64: switch to generic board Linus Walleij
2014-12-26 17:59 ` Steve Rae [this message]
2014-12-29 14:13 ` Simon Glass
2014-12-30  2:26 ` [U-Boot] [U-Boot,2/4] " Tom Rini

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=549DA215.8070308@broadcom.com \
    --to=srae@broadcom.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.