From: Scott Wood <scottwood@freescale.com>
To: Jimi Xenidis <jimix@pobox.com>
Cc: linuxppc-dev <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH v2] powerpc: book3e: WSP: Add Chroma as a new WSP/PowerEN platform.
Date: Thu, 27 Oct 2011 15:48:42 -0500 [thread overview]
Message-ID: <4EA9C3AA.6000807@freescale.com> (raw)
In-Reply-To: <DD04A5E8-2850-4DDC-9E7A-B899B0EEEF11@pobox.com>
On 10/11/2011 09:47 AM, Jimi Xenidis wrote:
> On Tue Oct 4 05:02:41 EST 2011, Scott Wood wrote:
>
> Looking at your comments below, will the following be acceptable
>
>> On 09/29/2011 09:27 PM, Jimi Xenidis wrote:
>>> diff --git a/arch/powerpc/platforms/wsp/Kconfig b/arch/powerpc/platforms/wsp/Kconfig
>>> index ea2811c..a3eef8e 100644
>>> --- a/arch/powerpc/platforms/wsp/Kconfig
>>> +++ b/arch/powerpc/platforms/wsp/Kconfig
>>> @@ -1,6 +1,7 @@
>>> config PPC_WSP
>>> bool
>>> select PPC_A2
>>> + select GENERIC_TBSYNC
>>> select PPC_ICSWX
>>> select PPC_SCOM
>>> select PPC_XICS
>>> @@ -8,14 +9,20 @@ config PPC_WSP
>>> select PCI
>>> select PPC_IO_WORKAROUNDS if PCI
>>> select PPC_INDIRECT_PIO if PCI
>>> + select PPC_WSP_COPRO
>>> default n
>>>
>>> menu "WSP platform selection"
>>> depends on PPC_BOOK3E_64
>
> add "&& SMP"
>
>>>
>>> config PPC_PSR2
>>> - bool "PSR-2 platform"
>>> - select GENERIC_TBSYNC
>>> + bool "PowerEN System Reference Platform 2"
>>> + select EPAPR_BOOT
>>> + select PPC_WSP
>>> + default y
>
> Make these "default n"
>
> Will that address everything?
It should address the issues I've seen, though someone (IIRC Timur) said
that he saw a dependency on some PCI error detection code as well.
-Scott
next prev parent reply other threads:[~2011-10-27 20:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-11 14:47 [PATCH v2] powerpc: book3e: WSP: Add Chroma as a new WSP/PowerEN platform Jimi Xenidis
2011-10-27 20:48 ` Scott Wood [this message]
2012-10-26 17:26 ` Scott Wood
-- strict thread matches above, loose matches on Subject: below --
2011-09-30 2:27 Jimi Xenidis
2011-10-03 18:02 ` Scott Wood
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=4EA9C3AA.6000807@freescale.com \
--to=scottwood@freescale.com \
--cc=jimix@pobox.com \
--cc=linuxppc-dev@lists.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).