From: Wolfgang Denk <wd@denx.de>
To: Dan Malek <dan@mvista.com>
Cc: paulus@linuxcare.com.au,
Tilmann Bitterberg <tibit-ibm@bitterberg.de>,
Linux/PPC Development <linuxppc-dev@lists.linuxppc.org>
Subject: Re: HIGHMEM now working
Date: Wed, 18 Oct 2000 09:27:56 +0200 [thread overview]
Message-ID: <200010180727.JAA13865@denx.local.net> (raw)
In-Reply-To: Your message of "Wed, 18 Oct 2000 02:11:01 EDT." <39ED3EF5.FF4D52E6@mvista.com>
In message <39ED3EF5.FF4D52E6@mvista.com> Dan Malek wrote:
>
> move this to later. I also use a #define IMMR for a pointer to the
> internal space of the processor. Saves a few cycles, but I should
> really make this a variable. I can use the #define because I know
What do you think about including IMMR in the board info structure,
and using this? That's what we're doing for PPCBoot systems (that
don't use/need a special boot loader).
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
Conceptual integrity in turn dictates that the design must proceed
from one mind, or from a very small number of agreeing resonant
minds. - Frederick Brooks Jr., "The Mythical Man Month"
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-10-18 7:27 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
2000-10-18 6:11 ` Dan Malek
2000-10-18 7:27 ` Wolfgang Denk [this message]
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=200010180727.JAA13865@denx.local.net \
--to=wd@denx.de \
--cc=dan@mvista.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=paulus@linuxcare.com.au \
--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 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.