From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Simon Richter <Simon.Richter@hogyros.de>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: APUS and IOs question
Date: Fri, 10 Nov 2006 09:48:39 +1100 [thread overview]
Message-ID: <1163112519.4982.50.camel@localhost.localdomain> (raw)
In-Reply-To: <45533C79.70404@hogyros.de>
> My plan for moving APUS to arch/powerpc involves writing a new
> bootloader (I'm currently hacking binutils to support AmigaOS binaries)
> that builds a proper flattened device tree and calls the kernel, but I'm
> not sure where the kernel virtual mapping that allows the kernel to run
> from a fixed address should be set up -- if in the bootloader, the
> kernel needs to be aware that changing the MMU settings will yield
> interesting results, and if in the kernel, we need some platform
> specific init code to handle that.
Well, the problem is that you basially have to hack the linear mapping,
thus hitting anything that relies on __pa/__va or operating in real mode
indeed.
How do you do for exception vectors ? Since those have to be either at 0
or at ff* ? You stick branches at 0 to jump to where the kernel
resides ?
Ben.
next prev parent reply other threads:[~2006-11-09 22:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-05 22:55 APUS and IOs question Benjamin Herrenschmidt
2006-11-06 15:18 ` Simon Richter
2006-11-06 16:45 ` Segher Boessenkool
2006-11-06 20:14 ` Benjamin Herrenschmidt
[not found] ` <454F5E44.4040301@genesi-usa.com>
[not found] ` <1162844529.28571.327.camel@localhost.localdomain>
[not found] ` <455081AC.3010301@hogyros.de>
[not found] ` <1162931605.28571.491.camel@localhost.localdomain>
2006-11-09 14:34 ` Simon Richter
2006-11-09 22:48 ` Benjamin Herrenschmidt [this message]
2006-11-10 1:39 ` Geert Uytterhoeven
2006-11-10 2:02 ` Roman Zippel
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=1163112519.4982.50.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=Simon.Richter@hogyros.de \
--cc=linuxppc-dev@ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.