From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Dave Weis <djweis@sjdjweis.com>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: new 601 port starting point?
Date: 03 Jun 2003 09:13:27 +0200 [thread overview]
Message-ID: <1054624406.541.70.camel@gaston> (raw)
In-Reply-To: <Pine.LNX.4.21.0306021217270.19576-100000@oliver.internal.sjdjweis.com>
On Mon, 2003-06-02 at 19:19, Dave Weis wrote:
> I'm going to be working on the mca rs/6000 machines again. The kernel has
> changed a bit since I last tried, so I need some advice.
>
> Which platform should I base my work on? It's a 601 machine, no pci or isa
> bus.
>
> I have downloaded the 2.4.20-benh rsync-able tree to start with.
I don't recommend using my tree for developing a new platform,
you should rather start from either the official 2.4.x tree in
kernel.org or the linuxppc_2_4, though the later is probably
what you want.
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-06-03 7:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-02 17:19 new 601 port starting point? Dave Weis
2003-06-03 7:13 ` Benjamin Herrenschmidt [this message]
2003-06-03 7:39 ` Remco Post
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=1054624406.541.70.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=djweis@sjdjweis.com \
--cc=linuxppc-dev@lists.linuxppc.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).