public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Tom Rini <trini@kernel.crashing.org>
Cc: Chris Friesen <cfriesen@nortelnetworks.com>,
	Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: problem with cache flush routine for G5?
Date: Fri, 05 Mar 2004 11:04:26 +1100	[thread overview]
Message-ID: <1078445065.5703.37.camel@gaston> (raw)
In-Reply-To: <20040304235754.GK26065@smtp.west.cox.net>


> 
> ... unless this is a 'G5' that's not in a pmac, it's not my code, and
> the openfirmware bootloaders don't, IIRC, do any cache stuff.

Heh, well, they should. You need to flush the dcache & invalidate the
icache over the kernel image after decompressing it. It's just that
those routines are totally broken as far as I can see, but I don't
think the pmac bootloaders will use them, they probably use a
different implementation that works.

Note that whatever machines are using those routines will probably
have trouble too anyway

Ben.



  reply	other threads:[~2004-03-05  0:04 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-04 21:06 problem with cache flush routine for G5? Chris Friesen
2004-03-04 23:51 ` Benjamin Herrenschmidt
2004-03-04 23:57   ` Tom Rini
2004-03-05  0:04     ` Benjamin Herrenschmidt [this message]
2004-03-05  0:44       ` Chris Friesen
2004-03-05 15:15       ` Tom Rini
2004-03-05 23:51         ` Benjamin Herrenschmidt
2004-03-05  0:37   ` Chris Friesen
2004-03-05  2:10     ` Benjamin Herrenschmidt
2004-03-05  5:39       ` Chris Friesen
2004-03-05  5:46         ` Benjamin Herrenschmidt
2004-03-05 17:21           ` Chris Friesen
2004-03-05 23:53             ` Benjamin Herrenschmidt
2004-03-06  1:34             ` Segher Boessenkool
2004-03-06  2:31             ` Anton Blanchard

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=1078445065.5703.37.camel@gaston \
    --to=benh@kernel.crashing.org \
    --cc=cfriesen@nortelnetworks.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=trini@kernel.crashing.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