linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: "Stephen Williams" <612dlag102@sneakemail.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Which kernel tree
Date: Fri, 06 Feb 2004 08:42:01 +0100	[thread overview]
Message-ID: <20040206074206.3F669C10B2@atlas.denx.de> (raw)
In-Reply-To: Your message of "Thu, 05 Feb 2004 19:01:08 PST." <10045-28297@sneakemail.com>


In message <10045-28297@sneakemail.com> you wrote:
>
> I've got u-boot working on my custom board, so now it's getting
> time to build a working kernel for my system-to-be.
>
> I have a PPC405GPr. I'll be writing drivers for the SystemACE
> and custom chips on the board, but I might as well do that work
> on a kernel that I'll be able to use for a while. So that begs
> the question, which kernel tree should I be following?
>
> There's the one at denx, that seems to be 2.4.4 from over

There is also linuxppc_2_4_devel on our CVS server, which is 2.4.24-preX


Best regards,

Wolfgang Denk

--
See us @ Embedded World, Nuremberg, Feb 17 - 19,  Hall 12.0 Booth 440
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
"An open mind has but one disadvantage: it collects dirt."
                                                    - a saying at RPI

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  parent reply	other threads:[~2004-02-06  7:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-06  3:01 Which kernel tree Stephen Williams
2004-02-06  3:11 ` Eugene Surovegin
2004-02-06  3:56   ` Stephen Williams
2004-02-06  8:37     ` Andrei Konovalov
2004-02-06  7:42 ` Wolfgang Denk [this message]
2004-02-06 15:50   ` song sam
2004-02-06 16:00     ` Wolfgang Denk
  -- strict thread matches above, loose matches on Subject: below --
2004-02-06 16:06 Kerl, John
2004-02-06 17:00 ` Christopher R. Johnson

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=20040206074206.3F669C10B2@atlas.denx.de \
    --to=wd@denx.de \
    --cc=612dlag102@sneakemail.com \
    --cc=linuxppc-embedded@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).