From: Benjamin Herrenschmidt <benh@kernel•crashing.org>
To: Jason Gunthorpe <jgunthorpe@obsidianresearch•com>
Cc: linuxppc-embedded@ozlabs•org
Subject: Re: [PATCH 2.6.15-rc4] ppc32: Fixes for non-zero PPC_MEMSTART on PPC440
Date: Mon, 05 Dec 2005 11:22:37 +1100 [thread overview]
Message-ID: <1133742158.6100.119.camel@gaston> (raw)
In-Reply-To: <20051202080711.GA32759@obsidianresearch.com>
On Fri, 2005-12-02 at 01:07 -0700, Jason Gunthorpe wrote:
> I have a custom embedded system with a 440GP derived CPU that places the
> memory starting at 0xc0000000 which requires a non-zero PPC_MEMSTART. There
> are a couple of places that assume PPC_MEMSTART is 0. This results in
> various tricky crashing during booting. Most of the problems are
> not accounting for PPC_MEMSTART during va/pa translations. My fixes
> convert these places to use pre-existing macros instead of duplicating
> the calculation.
Just out of curiosity: why did you do such a bogus setup in the first
place ?
Ben.
next prev parent reply other threads:[~2005-12-05 0:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-02 8:07 [PATCH 2.6.15-rc4] ppc32: Fixes for non-zero PPC_MEMSTART on PPC440 Jason Gunthorpe
2005-12-02 21:14 ` Josh Boyer
2005-12-05 0:22 ` Benjamin Herrenschmidt [this message]
2005-12-05 4:08 ` Jason Gunthorpe
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=1133742158.6100.119.camel@gaston \
--to=benh@kernel$(echo .)crashing.org \
--cc=jgunthorpe@obsidianresearch$(echo .)com \
--cc=linuxppc-embedded@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