From: Kumar Gala <kumar.gala@motorola•com>
To: Armin Schindler <armin.schindler@sysgo•com>
Cc: Linux/PPC Development <linuxppc-dev@lists•linuxppc.org>
Subject: Re: linuxppc latest ?
Date: Tue, 16 Mar 2004 00:38:15 -0600 [thread overview]
Message-ID: <812B9EB8-7714-11D8-A105-000393DBC2E8@motorola.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0403151120080.4038@acs.sysgo.com>
On Mar 15, 2004, at 4:31 AM, Armin Schindler wrote:
>
> Hi all,
>
> I'm somehow confused with the status of linuxppc.
>
> If I want to patch my 2.4.25 kernel, what should I do to have the
> latest linuxppc code ?
>
> penguinppc.org tells me to use bitkeeper's linuxppc-2.4, but this tree
> seems to be incomplete (directory arch/ppc/8260_io is missing).
> Even together with the main linux-2.4 tree, some features I know from
> the "old" snapshots are missing.
The the arch/ppc/8260_io dir has been renamed to cpm2_io.
- kumar
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-03-16 6:38 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-10 8:41 linuxppc trees, what is going on ? Sven Luther
2004-01-12 1:21 ` Paul Mackerras
2004-01-12 7:32 ` Sven Luther
2004-01-13 17:06 ` Tom Rini
2004-01-13 17:18 ` Sven Luther
2004-01-13 17:35 ` Tom Rini
2004-01-14 8:55 ` Sven Luther
2004-01-18 12:21 ` Sven Luther
2004-01-19 15:29 ` Tom Rini
2004-01-19 15:47 ` Sven Luther
2004-01-19 15:58 ` Tom Rini
2004-01-19 16:38 ` Sven Luther
2004-01-19 16:48 ` Tom Rini
2004-01-19 17:07 ` Sven Luther
2004-01-19 17:22 ` Tom Rini
2004-01-19 17:30 ` Sven Luther
2004-01-19 17:42 ` Geert Uytterhoeven
2004-01-19 17:48 ` Tom Rini
2004-01-19 17:49 ` Sven Luther
2004-01-19 17:53 ` Geert Uytterhoeven
2004-03-15 10:31 ` linuxppc latest ? Armin Schindler
2004-03-16 6:38 ` Kumar Gala [this message]
2004-01-19 17:43 ` linuxppc trees, what is going on ? Tom Rini
[not found] ` <20040123154058.GA15605@work.bitmover.com>
2004-01-23 15:49 ` Tom Rini
2004-01-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=812B9EB8-7714-11D8-A105-000393DBC2E8@motorola.com \
--to=kumar.gala@motorola$(echo .)com \
--cc=armin.schindler@sysgo$(echo .)com \
--cc=linuxppc-dev@lists$(echo .)linuxppc.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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