All of lore.kernel.org
 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 12:09:41 +0200	[thread overview]
Message-ID: <40DFEE65.7060908@imc-berlin.de> (raw)
In-Reply-To: <6.0.1.1.0.20040628115415.01f96428@192.168.2.1>

llandre wrote:

> 
>> 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
> 
> 
> For me everything is ok but the board name. I never saw that name before.
> On my board I can read:
> 
> MOTOROLA
> M9328MX1ADS/M9328MXLADS
> Ver 2.0
> 
> Do you really have that name on your PCB?

Arhg!

I just noticed: While the chip is called MC9328MX1 the eval board has 
actually M9328MX1ADS printed on it (which is the order code). Note the 
missing 'C' ...

Steven

  reply	other threads:[~2004-06-28 10:09 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
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 [this message]
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=40DFEE65.7060908@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 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.