All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Stephen Williams" <612dlag102@sneakemail.com>
To: linuxppc-embedded@lists.linuxppc.org
Subject: Which kernel tree
Date: Thu, 05 Feb 2004 19:01:08 -0800	[thread overview]
Message-ID: <10045-28297@sneakemail.com> (raw)


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
a year ago, or there are the kernels at www.kernel.org,
that may not have the up to date parts, or there's the
bkbits.net bitkeeper tree.

--
Steve Williams                "The woods are lovely, dark and deep.
steve at icarus.com           But I have promises to keep,
http://www.icarus.com         and lines to code before I sleep,
http://www.picturel.com       And lines to code before I sleep."


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

             reply	other threads:[~2004-02-06  3:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-06  3:01 Stephen Williams [this message]
2004-02-06  3:11 ` Which kernel tree Eugene Surovegin
2004-02-06  3:56   ` Stephen Williams
2004-02-06  8:37     ` Andrei Konovalov
2004-02-06  7:42 ` Wolfgang Denk
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=10045-28297@sneakemail.com \
    --to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.