From: Paul Mackerras <paulus@linuxcare.com.au>
To: Dan Malek <dan@mvista.com>
Cc: Tilmann Bitterberg <tibit-ibm@bitterberg.de>,
Linux/PPC Development <linuxppc-dev@lists.linuxppc.org>
Subject: Re: HIGHMEM now working
Date: Wed, 18 Oct 2000 16:36:47 +1100 (EST) [thread overview]
Message-ID: <14829.14063.44449.96097@argo.linuxcare.com.au> (raw)
In-Reply-To: <39EBE0E7.B9313EEE@mvista.com>
Dan Malek writes:
> Right, but that is just the most recent implementation for something
> we have to admit exists and we integrate into your HIGHMEM and other
> changes. We have to allow, somehow, mapping of board control registers
> or other resources that must be used prior to page tables or other
> VM initialization. Right now we map things in BATs or large TLB
OK, that means you need to access these things in the bootloader, or
inside identify_machine() (which calls m8xx_init in your case) or
MMU_init(). Once we get into setup_arch (and then m8xx_setup_arch) we
can just ioremap as normal.
What do you have to initialize that can't wait until m8xx_setup_arch?
Can you give me an example of what sorts of physical addresses you
need to access?
Thanks,
Paul.
--
Paul Mackerras, Senior Open Source Researcher, Linuxcare, Inc.
+61 2 6262 8990 tel, +61 2 6262 8991 fax
paulus@linuxcare.com.au, http://www.linuxcare.com.au/
Linuxcare. Support for the revolution.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-10-18 5:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-16 21:13 HIGHMEM now working Tilmann Bitterberg
2000-10-17 4:52 ` Paul Mackerras
2000-10-17 5:17 ` Dan Malek
2000-10-18 5:36 ` Paul Mackerras [this message]
2000-10-18 6:11 ` Dan Malek
2000-10-18 7:27 ` Wolfgang Denk
2000-10-18 15:41 ` Dan Malek
2000-10-17 15:05 ` Tilmann Bitterberg
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=14829.14063.44449.96097@argo.linuxcare.com.au \
--to=paulus@linuxcare.com.au \
--cc=dan@mvista.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=tibit-ibm@bitterberg.de \
/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;
as well as URLs for NNTP newsgroup(s).