From: Tom Rini <trini@kernel.crashing.org>
To: Val Henson <val@nmt.edu>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: [PATCH] Make Gemini boot
Date: Sat, 9 Feb 2002 10:10:29 -0700 [thread overview]
Message-ID: <20020209171029.GL20094@opus.bloom.county> (raw)
In-Reply-To: <20020208185019.G28166@boardwalk>
On Fri, Feb 08, 2002 at 06:50:19PM -0700, Val Henson wrote:
> This patch consists of all the bits that didn't really impact
> non-Gemini machines. If you apply all of it, Gemini will boot in the
> linuxppc_2_4_devel tree.
Erm, can you fix the current code to work on all of the various gemini
boards? I really don't want to bring back the piggyback bits (which are
only slightly better than the size/offset hacks). There's nothing wrong
w/ adding #ifdef CONFIG_GEMINI in a place or two. In fact, the
'setup_legacy()' call in misc-simple.c is for exactly the same problem
the gemini_console_baud_fixup(port) call is for (and since the others
are in asm, just change the prototype to take an arg, which they will
ignore).
--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2002-02-09 17:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-09 1:50 [PATCH] Make Gemini boot Val Henson
2002-02-09 17:10 ` Tom Rini [this message]
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=20020209171029.GL20094@opus.bloom.county \
--to=trini@kernel.crashing.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=val@nmt.edu \
/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