All of lore.kernel.org
 help / color / mirror / Atom feed
From: eric@eukrea.com (Eric Bénard)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: imx: Add some core definitions for MX53
Date: Wed, 27 Oct 2010 15:33:07 +0200	[thread overview]
Message-ID: <4CC82A13.8000909@eukrea.com> (raw)
In-Reply-To: <20101027132213.GJ6017@pengutronix.de>

Hi,

Le 27/10/2010 15:22, Sascha Hauer a ?crit :
 > That's a way we can go but only if the common name is not MX5 or MX5x.
 > We've done it with the mx21/27 and it failed when the mx25 came out
 > which was completely incompatible. Since then everybody looking at
 > the code must know that mx2x is mx21/27 but not mx25. I suggest
 > something like MX513 instead.
 >
MX513 is the partnumber of a member of the i.MX51 family so that's maybe not 
the best choice.
http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=i.MX513

Eric

WARNING: multiple messages have this Message-ID (diff)
From: "Eric Bénard" <eric@eukrea.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: "Grant Likely" <grant.likely@secretlab.ca>,
	amit.kucheria@canonical.com, linux@arm.linux.org.uk,
	Dinh.Nguyen@freescale.com, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, daniel@caiaq.de,
	"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
	valentin.longchamp@epfl.ch
Subject: Re: [PATCH] ARM: imx: Add some core definitions for MX53
Date: Wed, 27 Oct 2010 15:33:07 +0200	[thread overview]
Message-ID: <4CC82A13.8000909@eukrea.com> (raw)
In-Reply-To: <20101027132213.GJ6017@pengutronix.de>

Hi,

Le 27/10/2010 15:22, Sascha Hauer a écrit :
 > That's a way we can go but only if the common name is not MX5 or MX5x.
 > We've done it with the mx21/27 and it failed when the mx25 came out
 > which was completely incompatible. Since then everybody looking at
 > the code must know that mx2x is mx21/27 but not mx25. I suggest
 > something like MX513 instead.
 >
MX513 is the partnumber of a member of the i.MX51 family so that's maybe not 
the best choice.
http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=i.MX513

Eric

  reply	other threads:[~2010-10-27 13:33 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-26 18:53 [PATCH] ARM: imx: Add some core definitions for MX53 Dinh.Nguyen at freescale.com
2010-10-26 18:53 ` Dinh.Nguyen
2010-10-26 19:10 ` Uwe Kleine-König
2010-10-26 19:10   ` Uwe Kleine-König
2010-10-26 22:37   ` Nguyen Dinh-R00091
2010-10-26 22:37     ` Nguyen Dinh-R00091
2010-10-27  8:29 ` Grant Likely
2010-10-27  8:29   ` Grant Likely
2010-10-27  9:09   ` Uwe Kleine-König
2010-10-27  9:09     ` Uwe Kleine-König
2010-10-27 10:22     ` Grant Likely
2010-10-27 10:22       ` Grant Likely
2010-10-27 13:22       ` Sascha Hauer
2010-10-27 13:22         ` Sascha Hauer
2010-10-27 13:33         ` Eric Bénard [this message]
2010-10-27 13:33           ` Eric Bénard
2010-10-27 13:56           ` Sascha Hauer
2010-10-27 13:56             ` Sascha Hauer
2010-10-27 14:57             ` Nguyen Dinh-R00091
2010-10-27 14:57               ` Nguyen Dinh-R00091
2010-10-27 16:31               ` Sascha Hauer
2010-10-27 16:31                 ` Sascha Hauer
2010-10-27 23:44         ` Robert Schwebel
2010-10-27 23:44           ` Robert Schwebel
2010-10-27 13:36     ` Rob Herring
2010-10-27 13:36       ` Rob Herring

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=4CC82A13.8000909@eukrea.com \
    --to=eric@eukrea.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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.