From: Eric Nelson <eric.nelson@boundarydevices.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH RFC] imx: add multi-architecture README
Date: Sat, 09 Nov 2013 13:23:39 -0700 [thread overview]
Message-ID: <527E99CB.7030804@boundarydevices.com> (raw)
In-Reply-To: <1384027962-11556-1-git-send-email-eric.nelson@boundarydevices.com>
Hi all,
On 11/09/2013 01:12 PM, Eric Nelson wrote:
> Signed-off-by: Eric Nelson <eric.nelson@boundarydevices.com>
> ---
> doc/README.imx6-multi-arch | 254 +++++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 254 insertions(+)
> create mode 100644 doc/README.imx6-multi-arch
>
> diff --git a/doc/README.imx6-multi-arch b/doc/README.imx6-multi-arch
> new file mode 100644
> index 0000000..a31718c
As I mentioned yesterday, I'd like to get some agreement about some
of the fundamentals of how we'll do multi-arch, since they have an
impact on some patches in flight, notably
http://lists.denx.de/pipermail/u-boot/2013-November/thread.html#166154
As Edward's patch pointed out, the updates to consolidate the
pad names did not address the question of multiple declarations,
and in this document, I propose that (and how) we turn the
declarations into macros.
If that's agreed upon, I have a patch which does this without
any backward incompatibility (this required minor changes to mx6qarm2,
titanium, and mx6qsabreauto).
The other key change is that the DDR configuration files should
change to use macros instead of ".DATA" declarations directly
to allow use in run-time selection.
Again, this is simple enough to do in a backward-compatible way,
but I'd like to get agreement before submitting patches.
At the end of the document, I started to stray into policy and
know there may not be agreement about the "how" bits of this,
so I figured it was time to stop typing and get some feedback.
Please let me know your thoughts.
Regards,
Eric
next prev parent reply other threads:[~2013-11-09 20:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-09 20:12 [U-Boot] [PATCH RFC] imx: add multi-architecture README Eric Nelson
2013-11-09 20:23 ` Eric Nelson [this message]
2013-11-09 21:16 ` Wolfgang Denk
2013-11-09 22:24 ` Eric Nelson
2013-11-09 21:14 ` Wolfgang Denk
2013-11-09 22:57 ` Eric Nelson
2013-11-11 12:03 ` Tapani
2013-11-11 15:12 ` Eric Nelson
2013-11-11 17:51 ` Eric Nelson
[not found] ` <528124FA.6030203@boundarydevices.com>
2013-11-11 19:18 ` Eric Nelson
2013-11-11 19:36 ` Eric Nelson
2013-11-12 11:05 ` Tapani
2013-11-12 14:34 ` Eric Nelson
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=527E99CB.7030804@boundarydevices.com \
--to=eric.nelson@boundarydevices.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