From: Josh Boyer <jwboyer@linux.vnet.ibm.com>
To: Tirumala Marri <tmarri@apm.com>
Cc: Olof Johansson <olof@lixom.net>, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] APM821xx: Add support for new SoC APM821xx
Date: Mon, 6 Sep 2010 10:15:13 -0400 [thread overview]
Message-ID: <20100906141513.GA15942@hansolo.jdub.homelinux.org> (raw)
In-Reply-To: <01bb9090932e6984c887273078fd586f@mail.gmail.com>
On Sun, Sep 05, 2010 at 10:19:53PM -0700, Tirumala Marri wrote:
>>
>> Then the device tree identifier, and the cpu setup functions, etc,
>> should indicate
>> 464, not APM821xx.
>This is new SoC based on 464 cpu core. All the previous SoC device tree
>CPU portion uses SoC name.
>
>>
>> Also, why add yet another defconfig? Isn't the eval board similar to
>> many others and can be supported with just a tweak of some existing
>> common defconfig instead?
>>
>Every new board needs new defconfig. And it is not same as others. It has
>Different features from other.
You make it sound as if that is a hard and fixed rule. It's not. Not all
boards need a defconfig. Also, there was recent work to trim the defconfigs
that exist today down so they are not so large. I suggest you do the same
if you want the defconfig included.
josh
next prev parent reply other threads:[~2010-09-06 14:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-02 21:57 [PATCH] APM821xx: Add support for new SoC APM821xx tmarri
2010-09-03 2:08 ` Josh Boyer
2010-09-03 20:38 ` Tirumala Marri
2010-09-05 22:23 ` Olof Johansson
2010-09-06 5:19 ` Tirumala Marri
2010-09-06 14:15 ` Josh Boyer [this message]
2010-09-06 14:43 ` Tirumala Marri
2010-09-06 15:45 ` Olof Johansson
2010-09-08 17:27 ` Tirumala Marri
2010-09-13 13:44 ` Josh Boyer
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=20100906141513.GA15942@hansolo.jdub.homelinux.org \
--to=jwboyer@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=olof@lixom.net \
--cc=tmarri@apm.com \
/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;
as well as URLs for NNTP newsgroup(s).