From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 4/8] mxsboot: stop referring to i.MX28 as this ought to work for all i.MXS SoCs
Date: Tue, 29 May 2012 23:35:49 +0200 [thread overview]
Message-ID: <20120529213549.74CD82073AD@gemini.denx.de> (raw)
Dear Otavio,
I wrote:
> In message <CAP9ODKoA--EB3EsRP-OrFJ191fTOZvE-gFYCZrULkEtdC=3yYg@mail.gmail.com> you wrote:
> >
> > > But I haven't seen "i.MXS" used before, and to me it makes no sense as
> > > it mixes unrelated name spaces.
> > >
> > > Please either use the Freescale name(s), or use "mxs".
> >
> > http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=i.MXS
>
> It seems you are supporting my argument? Because the "i.MXS" I see
> documented there appears to have very little in common with, for
> example, i.MX28: "The processor features an ARM920T? core operating at
> 100 MHz"... ?
Or look at the "Parametrics" section:
- Not Recommended for New Design
- No Longer Manufactured
"i.MXS" is definitely a bad choice of name for what you have in mind.
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Honest error is to be pitied, not ridiculed.
-- Philip Earl of Chesterfield
next reply other threads:[~2012-05-29 21:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-29 21:35 Wolfgang Denk [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-05-12 23:40 [U-Boot] [PATCH 0/8] Minor fixes and start of consolidation onto mxs SoC Otavio Salvador
2012-05-12 23:40 ` [U-Boot] [PATCH 4/8] mxsboot: stop referring to i.MX28 as this ought to work for all i.MXS SoCs Otavio Salvador
2012-05-13 17:12 ` Marek Vasut
2012-05-13 18:19 ` Otavio Salvador
2012-05-29 20:44 ` Wolfgang Denk
2012-05-29 21:25 ` Otavio Salvador
2012-05-29 21:32 ` Wolfgang Denk
2012-05-29 21:53 ` Otavio Salvador
2012-05-30 5:49 ` Marek Vasut
2012-05-30 12:01 ` Otavio Salvador
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=20120529213549.74CD82073AD@gemini.denx.de \
--to=wd@denx.de \
--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