From: Tom Rini <trini@kernel.crashing.org>
To: Val Henson <val@nmt.edu>
Cc: linuxppc-commit@source.mvista.com, linuxppc-dev@lists.linuxppc.org
Subject: Re: Incoming to hostme.bitkeeper.com:/ua/repos/p/ppc/bk/linuxppc_2_4_devel
Date: Thu, 2 Aug 2001 16:51:02 -0700 [thread overview]
Message-ID: <20010802165102.N13516@opus.bloom.county> (raw)
In-Reply-To: <20010802174236.A3183@boardwalk>
On Thu, Aug 02, 2001 at 05:42:36PM -0600, Val Henson wrote:
> Didn't we just have a huge arch/ppc/boot reorganization?
Who said it's done? We made it a lot less of a problem, and at least a
bit less ugly. Now I'm getting around to finishing it up. For example,
there's no reason really that pmon, pcore, spruce, menf1, pp3 and sandpoint
along with 'PReP' and quite probably even gemini can't share the same
very early init code. 8xx/4xx can use almost all of head.S and probably
other code too. So why should we have 6-7 different copies of the same
code? For example, the L1 bits that everyone copied weren't wholly
correct. This wasn't noticed until Dan Malek did some sandpoint work and
I got him to look at others. With everyone sharing the same file(s) everyone
gets the same fixes.
--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
parent reply other threads:[~2001-08-02 23:51 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20010802174236.A3183@boardwalk>]
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=20010802165102.N13516@opus.bloom.county \
--to=trini@kernel.crashing.org \
--cc=linuxppc-commit@source.mvista.com \
--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