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 15:24:41 -0700 [thread overview]
Message-ID: <527EB629.4030101@boundarydevices.com> (raw)
In-Reply-To: <20131109211656.AC5083811CC@gemini.denx.de>
Thanks Wolfgang,
On 11/09/2013 02:16 PM, Wolfgang Denk wrote:
> Dear Eric Nelson,
>
> In message <527E99CB.7030804@boundarydevices.com> you wrote:
>>
>> 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
>
> We should be really precise when using terms like "architecture".
> Multi-arch would actually mean that one U-Boot image was capable of
> running on - say - both ARM and MIPS processors.
>
> We are not in a shape to even be able to run on all boards of a single
> processor family within the same architecture. Even if others use
> Big Words for their marketing documents, we should stick to plain
> technical facts and use appropriate names.
>
Points taken.
next prev parent reply other threads:[~2013-11-09 22:24 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
2013-11-09 21:16 ` Wolfgang Denk
2013-11-09 22:24 ` Eric Nelson [this message]
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=527EB629.4030101@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 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.