From: Victor Gallardo <vgallardo@amcc.com>
To: linuxppc-embedded@ozlabs.org
Subject: Re: [PATCH] Add AMCC Arches 460GT eval board support to platforms/44x
Date: Fri, 18 Jul 2008 15:31:33 -0700 (PDT) [thread overview]
Message-ID: <18538794.post@talk.nabble.com> (raw)
In-Reply-To: <20080716075025.0bca152c@zod.rchland.ibm.com>
> From what I can tell, you don't even need this patch or the defconfig.
> Nothing differs at this point from Glacier other than the DTS. Since
> U-Boot is your loader, it should be able to pass the different DTS to a
> kernel that supports Cayonlands and have no issues.
>
> ...
>
> If you do want to have explicit support for Arches, that's fine. Look
> at how Yosemite is supported. It just reuses Bamboo. You could do the
> same.
Yes, I like this idea. I'll do this.
>> +config 460GT
>> + bool
>> + select PPC_FPU
>> + select IBM_NEW_EMAC_EMAC4
>> + select IBM_NEW_EMAC_RGMII
>> + select IBM_NEW_EMAC_ZMII
>> + select IBM_NEW_EMAC_TAH
>
> I don't see a reason to add this at all. 460EX and 460GT select the
> same set of options.
OK. I agree.
> Here you would just have:
>
> obj-$(CONFIG_ARCHES) += cayonlands.o
>> diff --git a/arch/powerpc/platforms/44x/arches.c
>> b/arch/powerpc/platforms/44x/arches.c
>> new file mode 100644
>> index 0000000..6d6aa66
>> --- /dev/null
>> +++ b/arch/powerpc/platforms/44x/arches.c
>
> And then you don't need this file at all. Just add a
> "amcc,canyonlands" string to your root node compatible property.
OK. Will update
Thanks,
Victor Gallardo
--
View this message in context: http://www.nabble.com/-PATCH--Add-AMCC-Arches-460GT-eval-board-support-to-platforms-44x-tp18480745p18538794.html
Sent from the linuxppc-embedded mailing list archive at Nabble.com.
next prev parent reply other threads:[~2008-07-18 22:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-16 5:33 [PATCH] Add AMCC Arches 460GT eval board support to platforms/44x fkan
2008-07-16 11:50 ` Josh Boyer
2008-07-16 14:15 ` Grant Likely
2008-07-16 14:37 ` Josh Boyer
2008-07-16 15:43 ` Grant Likely
2008-07-17 3:15 ` Segher Boessenkool
2008-07-16 14:46 ` Arnd Bergmann
2008-07-16 15:46 ` Grant Likely
2008-07-16 22:58 ` Arnd Bergmann
2008-07-17 2:15 ` Josh Boyer
2008-07-17 3:24 ` Segher Boessenkool
2008-07-17 3:19 ` Segher Boessenkool
2008-07-18 22:31 ` Victor Gallardo [this message]
2008-07-19 13:44 ` Josh Boyer
2008-07-22 19:35 ` Victor Gallardo
2008-07-18 14:24 ` Stefan Roese
2008-07-18 22:24 ` Victor Gallardo
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=18538794.post@talk.nabble.com \
--to=vgallardo@amcc.com \
--cc=linuxppc-embedded@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 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).