public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Steven Scholz <steven.scholz@imc-berlin.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Re: nomen est omen: i.MX or mc9329 ?
Date: Mon, 28 Jun 2004 11:31:05 +0200	[thread overview]
Message-ID: <40DFE559.5000904@imc-berlin.de> (raw)
In-Reply-To: <20040628092036.GB13868@pengutronix.de>

Robert Schwebel wrote:

> On Mon, Jun 28, 2004 at 09:19:13AM +0200, llandre wrote:
> 
>>>>>how will we call the Motorola i.MX processors in future?
>>>>>
>>>>>Will it be "imx", "i.MX", "iMX" or MC9328MX{1,21,L}?
>>>>
>>>>The original 2.4 Linux port was mx1ads which is definitely wrong: it is
>>>>the name of the Motorola development board. Following the scheme of the
>>>>other architectures and platforms I would vote for imx.
>>>
>>>Following the scheme of the other architectures and platforms _and_ 
>>>speaking as a hardware developer I would vote for MC9328MX...
>>>Or at least "iMX".
>>
>>I vote for MC9328MX{1,21,L}.
> 
> 
> Stop - we have to differentiate between the "machine type" (which is
> imx) and the _implementation_ (which could be something like M9328MXL)
> and the "board" (M83281ADS). 
> 
> What about this: 
> 
> 	"machine type" (arch/arm/mach-xxx in Linux nomenclature): imx
> 	"implementation" (asm/arm/arch-xxx/yyy.h): MC9328MXL
> 	"board": M83281ADS

Hmm. I was talking about the cpu/ directory in U-Boot...

Altough the MC9328 has an ARM9 core I think we should create a new 
cpu/mc9328 (or cpu/iMX) directory and put the driver code for integrated 
peripherals (as UARTs etc.) into that directory.
This is done for loads of other CPUs. Just search for '*serial*' or '*fec*' 
in cpu/.

As for Linux I think you're right. But we don't have mach-xxx nor arch-xxx 
in U-Boot, do we?

--
Steven

  reply	other threads:[~2004-06-28  9:31 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-27 11:25 [U-Boot-Users] nomen est omen: i.MX or mc9329 ? Steven Scholz
2004-06-27 18:18 ` [U-Boot-Users] " Robert Schwebel
2004-06-28  7:11   ` Steven Scholz
2004-06-28  7:19     ` llandre
2004-06-28  9:20       ` Robert Schwebel
2004-06-28  9:31         ` Steven Scholz [this message]
2004-06-28  9:35         ` Wolfgang Denk
2004-06-28 10:51           ` Robert Schwebel
2004-06-28 11:37             ` Wolfgang Denk
2004-06-28 12:38               ` Robert Schwebel
2004-06-28 14:10                 ` Wolfgang Denk
2004-06-28 14:17                   ` Steven Scholz
2004-06-28 12:14             ` Steven Scholz
2004-06-28 13:01               ` Robert Schwebel
2004-06-28 15:15                 ` Sascha Hauer
2004-06-28  9:57         ` llandre
2004-06-28 10:09           ` Steven Scholz
2004-06-28 11:07             ` llandre

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=40DFE559.5000904@imc-berlin.de \
    --to=steven.scholz@imc-berlin.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