From: Matt Porter <mporter@kernel.crashing.org>
To: Phil Thompson <philt@4bridgeworks.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: 440GX Support on Linux v2.4
Date: Wed, 25 Feb 2004 09:32:03 -0700 [thread overview]
Message-ID: <20040225093203.A23663@home.com> (raw)
In-Reply-To: <C18BA5DDB58DD511BD0700C0DF0DD45028B27A@NTSERVER4>; from philt@4bridgeworks.com on Wed, Feb 25, 2004 at 03:54:08PM -0000
On Wed, Feb 25, 2004 at 03:54:08PM -0000, Phil Thompson wrote:
>
> I need to bring up Linux 2.4 on an IBM 440GX evaluation board (Ocotea I
> assume). It is supported on Linux 2.6.
>
> What's my best option for doing this...
>
> Somebody already has a patch for 2.4? :)
>
> Backport the code from 2.6?
>
> Enable 440GP compatibility mode and hack the existing 2.4 Ebony board
> support?
>
> Something else?
Clone linuxppc-2.4 and build using the Ocotea config? :)
-Matt
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-02-25 16:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-25 15:54 440GX Support on Linux v2.4 Phil Thompson
2004-02-25 16:22 ` Eugene Surovegin
2004-02-25 16:32 ` Matt Porter [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-02-25 16:35 Phil Thompson
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=20040225093203.A23663@home.com \
--to=mporter@kernel.crashing.org \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=philt@4bridgeworks.com \
/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).