public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Gerlando Falauto <gerlando.falauto@keymile.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v1 2/4] mpc83xx: add support for mpc8309
Date: Fri, 28 Sep 2012 16:08:39 +0200	[thread overview]
Message-ID: <5065AF67.9040303@keymile.com> (raw)
In-Reply-To: <20120927181817.bb7050de0a47024086bd3c93@freescale.com>

On 09/28/2012 01:18 AM, Kim Phillips wrote:
> On Thu, 27 Sep 2012 09:21:19 +0200
> Gerlando Falauto<gerlando.falauto@keymile.com>  wrote:
>
>> On 09/27/2012 03:22 AM, Kim Phillips wrote:
[...]
> so far the 8308 and the 8360 are the only SoCs that don't have a
> 'tens'/MPC83Xx defines.  The 8360 can get away with it, since it's
> very close to the 8358 (and we can avoid that marketing-imposed
> snafu).  The 8308 and 9 are more different (QE vs TSEC), but as seen
> here, there are other commonalities.

I personally don't think adding a new 830x symbol would lead to that 
much saving. Plus it should be the last one of the series so there won't 
be much use in the future either.
So unless you think that's absolutely necessary, I'd submit a v2 without 
this.

Thanks again,
Gerlando

  reply	other threads:[~2012-09-28 14:08 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-26  8:28 [U-Boot] [PATCH v1 0/4] introducing vect1: mpc8309 keymile board Gerlando Falauto
2012-09-26  8:28 ` [U-Boot] [PATCH v1 1/4] cosmetic: suvd3: align #defines Gerlando Falauto
2012-09-26  8:28 ` [U-Boot] [PATCH v1 2/4] mpc83xx: add support for mpc8309 Gerlando Falauto
2012-09-27  1:22   ` Kim Phillips
2012-09-27  7:21     ` Gerlando Falauto
2012-09-27 23:18       ` Kim Phillips
2012-09-28 14:08         ` Gerlando Falauto [this message]
2012-09-28 15:51           ` Kim Phillips
2012-09-26  8:28 ` [U-Boot] [PATCH v1 3/4] km83xx: add common support for km8309 boards Gerlando Falauto
2012-09-26  8:28 ` [U-Boot] [PATCH v1 4/4] km83xx: add kmvect1 board Gerlando Falauto
2012-10-11  8:13 ` [U-Boot] [PATCH v2 0/6] introducing vect1: mpc8309 keymile board Gerlando Falauto
2012-10-11  8:13   ` [U-Boot] [PATCH v2 1/6] cosmetic: suvd3: align #defines Gerlando Falauto
2012-10-11  8:13   ` [U-Boot] [PATCH v2 2/6] cleanup: use CONFIG_QE instead of CONFIG_MPC8360 || CONFIG_MPC832x Gerlando Falauto
2012-10-11  8:13   ` [U-Boot] [PATCH v2 3/6] cleanup: introduce CONFIG_MPC830x Gerlando Falauto
2012-10-11  8:13   ` [U-Boot] [PATCH v2 4/6] mpc83xx: add support for mpc8309 Gerlando Falauto
2012-10-11  8:13   ` [U-Boot] [PATCH v2 5/6] km83xx: add common support for km8309 boards Gerlando Falauto
2012-10-23 21:10     ` Kim Phillips
2012-10-11  8:13   ` [U-Boot] [PATCH v2 6/6] km83xx: add kmvect1 board Gerlando Falauto

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=5065AF67.9040303@keymile.com \
    --to=gerlando.falauto@keymile.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