public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
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:57:02 -0700	[thread overview]
Message-ID: <527EBDBE.1000006@boundarydevices.com> (raw)
In-Reply-To: <20131109211409.A1CC23811CC@gemini.denx.de>

Thanks Wolfgang.

On 11/09/2013 02:14 PM, Wolfgang Denk wrote:
> Dear Eric Nelson,
>
> In message <1384027962-11556-1-git-send-email-eric.nelson@boundarydevices.com> you wrote:
> ...
>> +Supporting multiple architectures on Freescale i.MX6
>> +
>> +This file describes how to support multiple CPU architectures
>> +(i.MX6DQ and i.MX6DLS) in a single U-Boot image.
>
> I think the term "architectures" is greatly misleading here. An
> "architecture" is for example ARm or MIPS or Power Architecture.
>
> What you are talking about are mere CPU models.
>
> Please adapt the Subject and commit message.
>

Done. I started typing in "multi-CPU", but that's also overloaded,
so I stumbled on BOMs, since that seems more to the point (that
a board can be assembled using different specific parts).

It still suffers from some awkwardness surrounding what to call
the division between the high-end parts and the low-end.

Choosing words is hard, and suggestions are welcome.

I starting to use the term "SKU", but I'm not sure how commonly
used that term has become.

Regards,


Eric

  reply	other threads:[~2013-11-09 22:57 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
2013-11-09 21:14 ` Wolfgang Denk
2013-11-09 22:57   ` Eric Nelson [this message]
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=527EBDBE.1000006@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