From: Benjamin Herrenschmidt <benh@kernel•crashing.org>
To: Jerome Glisse <j.glisse@gmail•com>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs•org>
Subject: Re: linux 2.6.12-rc1-bk5 compilation error
Date: Mon, 04 Apr 2005 22:41:48 +1000 [thread overview]
Message-ID: <1112618509.26086.68.camel@gaston> (raw)
In-Reply-To: <4240b916050404033230db0551@mail.gmail.com>
On Mon, 2005-04-04 at 11:32 +0100, Jerome Glisse wrote:
> Hi,
>
> Once again i face an error that i got with a previous
> 2.6 kernel (i already posted about this in january
> i think).
>
> My config G5 bi 2Ghz and you can grab my kernel
> config here : http://dj.planet-d.net/config
>
> When compiling 2.6.12-rc1-bk5 i first get unknown
> symbol _flush_disable_L1. This is in arch/ppc/kernel/l2cr.S
> I changed the makefile in arch/ppc/kernel to have this :
> obj-$(CONFIG_POWER4) += cpu_setup_power4.o
> into :
> obj-$(CONFIG_POWER4) += l2cr.o cpu_setup_power4.o
>
> .../...
You should really be using a 64 bits kernel :)
Ben.
next prev parent reply other threads:[~2005-04-04 12:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-04 10:32 linux 2.6.12-rc1-bk5 compilation error Jerome Glisse
2005-04-04 10:51 ` Jerome Glisse
2005-04-04 11:52 ` Jerome Glisse
2005-04-04 12:41 ` Benjamin Herrenschmidt [this message]
2005-04-04 19:11 ` Jerome Glisse
2005-04-04 23:12 ` Benjamin Herrenschmidt
2005-04-05 11:52 ` Jerome Glisse
2005-04-05 12:39 ` Andreas Schwab
2005-04-05 15:17 ` Jerome Glisse
2005-04-05 23:12 ` Benjamin Herrenschmidt
2005-04-05 23:25 ` Andreas Schwab
2005-04-05 23:11 ` Benjamin Herrenschmidt
2005-04-07 17:10 ` Tom Rini
2005-04-08 10:13 ` Jerome Glisse
2005-04-08 15:34 ` [PATCH 2.6.12-rc2] ppc32: Fix building 32bit kernel for 64bit machines (Was: Re: linux 2.6.12-rc1-bk5 compilation error) Tom Rini
2005-04-08 22:27 ` Jerome Glisse
2005-04-08 23:47 ` Benjamin Herrenschmidt
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=1112618509.26086.68.camel@gaston \
--to=benh@kernel$(echo .)crashing.org \
--cc=j.glisse@gmail$(echo .)com \
--cc=linuxppc-dev@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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