From: Scott Wood <oss@buserror.net>
To: Alessio Igor Bogani <alessio.bogani@elettra.eu>
Cc: Kumar Gala <galak@kernel.crashing.org>, linuxppc-dev@lists.ozlabs.org
Subject: Re: Question about 86xx
Date: Fri, 05 Feb 2016 14:42:31 -0600 [thread overview]
Message-ID: <1454704951.2486.35.camel@buserror.net> (raw)
In-Reply-To: <CAPk1OjHnF=oi=M5son2vdsZwrhXC6Uy-wTJKpQiZcZMnWLb8KA@mail.gmail.com>
On Thu, 2016-02-04 at 15:26 +0100, Alessio Igor Bogani wrote:
> Scott,
>
> On 27 January 2016 at 15:41, Alessio Igor Bogani
> <alessio.bogani@elettra.eu> wrote:
> > Scott,
> >
> > On 27 January 2016 at 15:27, Scott Wood <oss@buserror.net> wrote:
> > > On Wed, 2016-01-27 at 08:25 -0600, Scott Wood wrote:
> > > > On Wed, 2016-01-27 at 10:24 +0100, Alessio Igor Bogani wrote:
> > [...]
> > > > > I'm wondering if we are allowed to put together configurations of
> > > > > the
> > > > > 86xx base systems
> > [...]
> > > > > mpc86xx_defconfig/mpc86xx_smp_defconfig as like already done for
> > > > > 85xx
> > > > > ones.
> > > > Yes, that would be good.
>
> There are 6 boards into arch/powerpc/configs/86xx directory. Five of
> them are based on dual core 8641 whereas one is based on single core
> 8610. How should I proceed? Use a single file (mpc86xx_defconfig) or
> use two files (mpc86xx_defconfig and mpc86xx_smp_defconfig)?
Use a fragment to enable SMP, like 85xx does.
-Scott
prev parent reply other threads:[~2016-02-05 20:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-27 9:24 Question about 86xx Alessio Igor Bogani
2016-01-27 14:25 ` Scott Wood
2016-01-27 14:27 ` Scott Wood
2016-01-27 14:41 ` Alessio Igor Bogani
2016-02-04 14:26 ` Alessio Igor Bogani
2016-02-05 20:42 ` Scott Wood [this message]
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=1454704951.2486.35.camel@buserror.net \
--to=oss@buserror.net \
--cc=alessio.bogani@elettra.eu \
--cc=galak@kernel.crashing.org \
--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).