public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Jerome Glisse <j.glisse@gmail•com>
To: Tom Rini <trini@kernel•crashing.org>
Cc: linuxppc-dev@ozlabs•org
Subject: Re: linux 2.6.12-rc1-bk5 compilation error
Date: Fri, 8 Apr 2005 11:13:19 +0100	[thread overview]
Message-ID: <4240b91605040803137e9e7ddc@mail.gmail.com> (raw)
In-Reply-To: <20050407171026.GO3396@smtp.west.cox.net>

> I think you're the only person building a zImage for a 32bit kernel with
> a 64bit toolchain for MULTIPLATFORM, yes. :)

I should move to 64bits :)
 
> This is a valid problem, however.  Does the following also work for you?

It partly works (correct the problem with disable_6xx_mmu)
but i still have to the following for resolving __flush_disable_L1

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

Jerome Glisse

  reply	other threads:[~2005-04-08 10:13 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
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 [this message]
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=4240b91605040803137e9e7ddc@mail.gmail.com \
    --to=j.glisse@gmail$(echo .)com \
    --cc=linuxppc-dev@ozlabs$(echo .)org \
    --cc=trini@kernel$(echo .)crashing.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