All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Rigby <jrigby@freescale.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 3/7] Basic Freescale MPC512x support
Date: Tue, 08 Jan 2008 11:25:43 -0700	[thread overview]
Message-ID: <4783C027.8080405@freescale.com> (raw)
In-Reply-To: <200801081907.59052.arnd@arndb.de>

Arnd Bergmann wrote:
> On Tuesday 08 January 2008, John Rigby wrote:
>   
>>  obj-$(CONFIG_PPC_CHRP)         += chrp/
>>  obj-$(CONFIG_40x)              += 40x/
>>  obj-$(CONFIG_44x)              += 44x/
>> +obj-$(CONFIG_PPC_512x)         += 512x/
>>  obj-$(CONFIG_PPC_MPC52xx)      += 52xx/
>>  obj-$(CONFIG_PPC_8xx)          += 8xx/
>>  obj-$(CONFIG_PPC_82xx)         += 82xx/
>>     
>
> Why do you name the directory 512x instead of 51xx, which would be
> more consistent with the others? Do you expect other 51xx chips that
> are mostly incompatible with 512x?
>   
51xx would be confusing because 5100 was a precursor to the 5200.

Adding it to 52xx would is wrong because 5121 is really not that
much like a 5200.  It is really a 83xx minus some networking hw
plus some 5200 peripherals (PSCs and MSCAN).

In the best of possible worlds it would have a 83xx part number
and go in 83xx but that would be confusing since it is targeted
at the automotive market.
> Moreover, is it really so different from 52xx that it needs a separate
> directory? E.g. we often treat the 74xx and 7xx as 6xx variants.
>
> 	Arnd <><
>
>   

  reply	other threads:[~2008-01-08 18:26 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-08 16:01 [PATCH 0/7] mpc5121 support John Rigby
2008-01-08 16:01 ` [PATCH 1/7] mpc5121: Add IPIC config option John Rigby
2008-01-08 16:01   ` [PATCH 2/7] Add mpc512x ipic support John Rigby
2008-01-08 16:01     ` [PATCH 3/7] Basic Freescale MPC512x support John Rigby
2008-01-08 16:01       ` [PATCH 4/7] Device tree for MPC5121 ADS John Rigby
2008-01-08 16:01         ` [PATCH 5/7] Separate MPC52xx PSC FIFO registers from rest of PSC John Rigby
2008-01-08 16:01           ` [PATCH 6/7] Add mpc512x_find_ips_freq John Rigby
2008-01-08 16:01             ` [PATCH 7/7] Add MPC512x PSC serial driver John Rigby
2008-01-08 17:32               ` Grant Likely
2008-01-08 17:47                 ` John Rigby
2008-01-08 20:16                   ` Grant Likely
2008-01-09  3:16               ` Stephen Rothwell
2008-01-09  6:06                 ` Stephen Rothwell
2008-01-08 17:27             ` [PATCH 6/7] Add mpc512x_find_ips_freq Grant Likely
2008-01-08 18:15             ` Arnd Bergmann
2008-01-08 17:26           ` [PATCH 5/7] Separate MPC52xx PSC FIFO registers from rest of PSC Grant Likely
2008-01-08 17:25         ` [PATCH 4/7] Device tree for MPC5121 ADS Grant Likely
2008-01-08 19:22         ` Scott Wood
2008-01-10  2:18         ` David Gibson
2008-01-08 17:19       ` [PATCH 3/7] Basic Freescale MPC512x support Grant Likely
2008-01-08 17:55         ` Scott Wood
2008-01-08 17:56           ` Grant Likely
2008-01-08 19:25             ` Scott Wood
2008-01-08 20:37               ` Generic desktop/server/laptop lable is confusing [Was Re: [PATCH 3/7] Basic Freescale MPC512x support] John Rigby
2008-01-08 21:40                 ` Grant Likely
2008-01-08 21:46                   ` Scott Wood
2008-01-08 17:40       ` [PATCH 3/7] Basic Freescale MPC512x support Olof Johansson
2008-01-08 17:44         ` Jon Loeliger
2008-01-08 18:01         ` John Rigby
2008-01-08 18:13         ` Arnd Bergmann
2008-01-08 18:16         ` John Rigby
2008-01-08 18:07       ` Arnd Bergmann
2008-01-08 18:25         ` John Rigby [this message]
2008-01-09  2:36       ` Stephen Rothwell

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=4783C027.8080405@freescale.com \
    --to=jrigby@freescale.com \
    --cc=arnd@arndb.de \
    --cc=linuxppc-dev@ozlabs.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.