From: Tom Rini <trini@kernel.crashing.org>
To: Jerome Glisse <j.glisse@gmail.com>
Cc: Andrew Morton <akpm@osdl.org>,
linuxppc-dev@ozlabs.org, Paul Mackerras <paulus@samba.org>,
linuxppc64-dev@ozlabs.org
Subject: Re: Classic PPC specific ASM (CONFIG_6XX)
Date: Mon, 10 Jan 2005 12:12:48 -0700 [thread overview]
Message-ID: <20050110191248.GB3391@smtp.west.cox.net> (raw)
In-Reply-To: <4240b91605011010593d2f3b3d@mail.gmail.com>
On Mon, Jan 10, 2005 at 07:59:50PM +0100, Jerome Glisse wrote:
> > I have a feeling CONFIG_6xx isn't selected for a good reason. Can you
> > try, as a kludge, removing define_bool PPC_PREP from arch/ppc/Kconfig
> > and seeing if you can build / boot ? Thanks.
> >
> > --
> > Tom Rini
> > http://gate.crashing.org/~trini/
> >
>
> Seems that this flags is linked to many things :) I tried removing PPC_PREP
> bool but the kernel fail to compile with again new errors :
>
One last thing before we just do what you suggested originally, can you
hack it so that PPC_PREP is still set, but on 970 we still set
CONFIG_6xx? Thanks again.
--
Tom Rini
http://gate.crashing.org/~trini/
next prev parent reply other threads:[~2005-01-10 19:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-09 15:40 Classic PPC specific ASM (CONFIG_6XX) Jerome Glisse
2005-01-09 21:03 ` Paul Mackerras
2005-01-10 14:52 ` Tom Rini
2005-01-10 16:39 ` Christoph Hellwig
2005-01-10 16:44 ` Tom Rini
2005-01-10 18:14 ` Jerome Glisse
2005-01-10 18:29 ` Tom Rini
2005-01-10 18:59 ` Jerome Glisse
2005-01-10 19:12 ` Tom Rini [this message]
2005-01-10 19:31 ` Jerome Glisse
[not found] ` <4240b91605011211101ed322a8@mail.gmail.com>
[not found] ` <20050120231442.GE2626@smtp.west.cox.net>
2005-01-21 11:22 ` Jerome Glisse
2005-01-21 12:36 ` Geert Uytterhoeven
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=20050110191248.GB3391@smtp.west.cox.net \
--to=trini@kernel.crashing.org \
--cc=akpm@osdl.org \
--cc=j.glisse@gmail.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=linuxppc64-dev@ozlabs.org \
--cc=paulus@samba.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).