From: Sam Ravnborg <sam@ravnborg.org>
To: Jon Loeliger <jdl@freescale.com>
Cc: Scott Wood <scottwood@freescale.com>,
linuxppc-dev list <linuxppc-dev@ozlabs.org>,
"Kernel, Linux" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCHv2 0/8] [POWERPC] 8xx cleanups
Date: Wed, 23 Jan 2008 19:00:12 +0100 [thread overview]
Message-ID: <20080123180012.GA23313@uranus.ravnborg.org> (raw)
In-Reply-To: <47977A02.40506@freescale.com>
On Wed, Jan 23, 2008 at 11:31:46AM -0600, Jon Loeliger wrote:
> Sam Ravnborg wrote:
> >>What impact do the have on boards in arch/ppc being able to build?
> >
> >Byt the way what are the plans for powerpc?
> >We have:
> >arch/ppc
> >arch/ppc64
> >arch/powerpc
> >
> >It was my understanding that arch/powerpc was supposed
> >to be the future unified powerpc architecture but it
> >does not even provide a defconfig.
> >
> >And I do not see too much happening to do so - but that maybe
> >because I looked at a wrong place.
>
> You must have looked in the wrong place. :-)
>
> arch/ppc is scheduled for removal from mainline in June.
Good to hear.
> arch/powerpc is under significant development, with lots
> of defconfigs in arch/powerpc/configs.
Double checked - it was my build script that used ARCH=ppc
Now I just need to build another toolchain as the ppc750 could not build
the defconfig. crosstool is my friend here.
Sam
next prev parent reply other threads:[~2008-01-23 18:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-23 15:58 [PATCHv2 0/8] [POWERPC] 8xx cleanups Jochen Friedrich
2008-01-23 16:11 ` Kumar Gala
2008-01-23 17:12 ` Sam Ravnborg
2008-01-23 17:31 ` Jon Loeliger
2008-01-23 18:00 ` Sam Ravnborg [this message]
2008-01-23 19:35 ` Josh Boyer
2008-01-23 20:12 ` Sam Ravnborg
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=20080123180012.GA23313@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=jdl@freescale.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=scottwood@freescale.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).