From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC PACH v2 1/1] Add vexpress_aemv8a_aarch32 variant
Date: Mon, 5 Dec 2016 14:00:21 -0500 [thread overview]
Message-ID: <20161205190021.GR4248@bill-the-cat> (raw)
In-Reply-To: <CAD0U-h+bf4++XTtdVnH1TqTVyn1y=2Su4tjEj+Ww0kDS4E2Bjg@mail.gmail.com>
On Mon, Dec 05, 2016 at 06:01:48PM +0000, Ryan Harkin wrote:
> Hi Tom,
>
[snip]
> At the moment, the BASE_FVP_DRAM version is a clone of the BASE_FVP
> code, just with a different bootcmd. Now the AARCH32 is another clone
> with CPU_V7 and bootz instead of booti.
>
> I'd be interested to know if there is a better way to handle those
> small variations. A better structured header than vexpress_aemv8a.h
> would be a good start, of course.
The very new include/environment/ directory would be the place to put
these various environment bits (probably under armltd/) and then you
could probably do something like:
#ifdef CONFIG_ARM64
#define BOARD_BOOTCMD "booti"
#else
#define BOARD_BOOTCMD "bootz"
#endif
#define BOOTCOMMAND "..." \
BOARD_BOOTCMD + " $loadaddr - $fdtaddr"
And add some other choice / bools to board/armltd/vexpress/Kconfig to
enable/disable other environment things as needed.
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20161205/fc62ca28/attachment.sig>
prev parent reply other threads:[~2016-12-05 19:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-05 16:11 [U-Boot] [RFC PACH v2 1/1] Add vexpress_aemv8a_aarch32 variant Ryan Harkin
2016-12-05 17:13 ` Tom Rini
2016-12-05 18:01 ` Ryan Harkin
2016-12-05 19:00 ` Tom Rini [this message]
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=20161205190021.GR4248@bill-the-cat \
--to=trini@konsulko.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox