From: Matt Porter <mporter@mvista.com>
To: Dustin Byford <dustin@firein.net>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: which kernel should I modify?
Date: Wed, 17 Apr 2002 07:53:06 -0700 [thread overview]
Message-ID: <20020417075306.A15647@home.com> (raw)
In-Reply-To: <200204170503.29940.dustin@firein.net>; from dustin@firein.net on Wed, Apr 17, 2002 at 05:03:29AM -0600
On Wed, Apr 17, 2002 at 05:03:29AM -0600, Dustin Byford wrote:
>
> I am about to start modifying a linux kernel to run on a custom mpc8240 board
> that has a uart, boot rom, a pair of amd 32Mbit roms, and a PCI bus. It is
> intended to act as an IP router.
>
> I was wondering, can anyone recommend which kernel tree I should start with?
> Should I begin with the standard PPC 2.4 tree or the 2.4_devel tree?
2_4_devel
--
Matt Porter
MontaVista Software, Inc.
mporter@mvista.com
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2002-04-17 14:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-17 11:03 which kernel should I modify? Dustin Byford
2002-04-17 14:53 ` Matt Porter [this message]
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=20020417075306.A15647@home.com \
--to=mporter@mvista.com \
--cc=dustin@firein.net \
--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.