From: Matt Porter <mporter@kernel.crashing.org>
To: Matt Porter <mporter@kernel.crashing.org>
Cc: eric lescouet <eric.lescouet@Jaluna.COM>,
Michele.Pallaro@alcatel.it,
linuxppc-embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Linux kernel and u-boot for mpc8540
Date: Thu, 5 Feb 2004 13:47:17 -0700 [thread overview]
Message-ID: <20040205134717.A17211@home.com> (raw)
In-Reply-To: <20040205091232.A15092@home.com>; from mporter@kernel.crashing.org on Thu, Feb 05, 2004 at 09:12:32AM -0700
On Thu, Feb 05, 2004 at 09:12:32AM -0700, Matt Porter wrote:
>
> On Thu, Feb 05, 2004 at 10:32:48AM +0100, eric lescouet wrote:
> >
> > Michele,
> >
> > Support for mpc8540 is already in linuxppc-2.4 tree.
> > see ppc.bkbits.net
>
> Actually, the linuxppc-2.4 support is incomplete, there's no TSEC/FEC
> driver or other on-chip peripheral drivers in that tree to make it
> really useful. You could just use a PCI network card to nfsroot a
> filesystem and get started, though.
Ooops...gotta correct this before I confuse somebody. The TSEC/FEC
gianfar driver is in the tree...I missed that changeset. :)
-Matt
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-02-05 20:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-05 7:45 Linux kernel and u-boot for mpc8540 Michele.Pallaro
2004-02-05 9:32 ` eric lescouet
2004-02-05 16:12 ` Matt Porter
2004-02-05 16:36 ` Michele.Pallaro
2004-02-05 20:47 ` Matt Porter [this message]
2004-02-06 6:00 ` Kumar Gala
-- strict thread matches above, loose matches on Subject: below --
2004-02-05 7:55 Klaus Popp
2004-02-05 8:27 ` Wolfgang Denk
2004-02-05 8:35 Klaus Popp
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=20040205134717.A17211@home.com \
--to=mporter@kernel.crashing.org \
--cc=Michele.Pallaro@alcatel.it \
--cc=eric.lescouet@Jaluna.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).