From: Peter Bergner <bergner@brule.borg.umn.edu>
To: Tom Rini <trini@kernel.crashing.org>
Cc: Adam C Powell IV <hazelsct@mit.edu>, linuxppc-dev@lists.linuxppc.org
Subject: Re: Why require CONFIG_BOOTX_TEXT for so much of offb?
Date: Thu, 13 Dec 2001 10:58:09 -0600 [thread overview]
Message-ID: <20011213105809.A244378@brule.borg.umn.edu> (raw)
In-Reply-To: <20011213020019.GC28967@cpe-24-221-152-185.az.sprintbbd.net>
Tom Rini wrote:
: BOOTX_TEXT != BootX now tho. It's for writing on the screen early on.
: Perhaps some name changing, define moving and a new header for ppc64?
That doesn't seem to be used for prom_prints(), so what early screen
prints would these be? If ppc64 can make use of them, then some
"name changing, define moving and a new header for ppc64" would be the
right thing. If not, then just replacing the #ifdef CONFIG_BOOTX_TEXT
with #ifndef CONFIG_PPC64 would seem to be the right decision.
The later would fix the compile problem for ppc64 and things would
be back to the way they used to work for ppc32.
Peter
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-12-13 16:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-11 4:11 Why require CONFIG_BOOTX_TEXT for so much of offb? Adam C Powell IV
2001-12-12 19:05 ` Peter Bergner
2001-12-13 2:00 ` Tom Rini
2001-12-13 16:58 ` Peter Bergner [this message]
2001-12-13 17:04 ` Tom Rini
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=20011213105809.A244378@brule.borg.umn.edu \
--to=bergner@brule.borg.umn.edu \
--cc=hazelsct@mit.edu \
--cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).