From: "Robert P. J. Day" <rpjday@mindspring.com>
To: Tom Rini <trini@kernel.crashing.org>
Cc: Linuxppc-dev mailing list <linuxppc-dev@ozlabs.org>
Subject: Re: Linux 2.6.x on 8xx status
Date: Mon, 20 Sep 2004 14:02:43 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.60.0409201400030.5204@dell.enoriver.com> (raw)
In-Reply-To: <20040920174914.GM27914@smtp.west.cox.net>
On Mon, 20 Sep 2004, Tom Rini wrote:
> Note that the old SCC enet driver, in linuxppc-2.5 at least is 'OK'.
> Not that it couldn't do with a cleanup and netdev person audit, but it's
> functional enough for me and my rpxlite to mount a root fs.
sorry to jump into this conversation late -- which "2.6.x" source tree
is being used here?
for quite some time, i've just used the linuxppx-2.5 tree at
ppc.bkbits.net. but when someone refers to a 2.6.x tree, which one
specifically is this? just the latest BK update from www.kernel.org?
or is this a PPC-specific tree?
rday
next prev parent reply other threads:[~2004-09-20 18:09 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040916201505.E723B2BDB2@ozlabs.org>
2004-09-17 10:06 ` Linux 2.6.x on 8xx status Song Sam
2004-09-17 9:55 ` Pantelis Antoniou
2004-09-18 20:11 ` Song Sam
2004-09-20 6:02 ` Pantelis Antoniou
2004-09-20 11:47 ` Song Sam
2004-09-20 17:49 ` Tom Rini
2004-09-20 18:02 ` Robert P. J. Day [this message]
2004-09-20 18:17 ` Tom Rini
2004-09-21 1:38 ` Song Sam
2004-09-21 6:12 ` Pantelis Antoniou
2004-09-21 10:35 ` Song Sam
2004-09-21 10:41 ` Pantelis Antoniou
2004-10-15 15:47 ` Marcelo Tosatti
2005-02-22 11:20 Joakim Tjernlund
-- strict thread matches above, loose matches on Subject: below --
2004-10-25 15:00 Sam Song
2004-09-21 11:59 Smith, Craig
2004-09-21 11:53 ` Pantelis Antoniou
2004-09-21 16:54 ` Dan Malek
2004-09-21 17:03 ` Dan Malek
2004-09-22 11:09 ` Sam Song
2004-10-15 15:49 ` Marcelo Tosatti
2004-10-16 2:13 ` Marcelo Tosatti
2004-10-16 9:08 ` Sam Song
2004-10-18 5:59 ` Pantelis Antoniou
2004-10-18 6:22 ` Sam Song
2004-10-18 3:10 ` Dan Malek
2005-02-10 15:04 ` Marcelo Tosatti
2005-02-10 19:26 ` Dan Malek
2005-02-10 17:06 ` Marcelo Tosatti
2005-02-10 17:08 ` Marcelo Tosatti
2005-03-21 21:45 ` Guillaume Autran
2005-03-21 21:53 ` Robert P. J. Day
2005-03-22 13:04 ` Marcelo Tosatti
2005-03-22 20:57 ` Dan Malek
2005-03-22 17:58 ` Marcelo Tosatti
2005-03-22 22:53 ` Dan Malek
2005-03-23 10:25 ` Marcelo Tosatti
2005-03-23 16:12 ` Dan Malek
2005-03-23 16:05 ` Marcelo Tosatti
2005-03-24 14:05 ` Pantelis Antoniou
2005-03-23 14:06 ` Guillaume Autran
2005-02-11 3:42 ` Dan Malek
2005-02-21 21:12 ` Armin Schindler
2005-02-21 23:45 ` Guillaume Autran
2004-09-17 13:57 Smith, Craig
2004-09-17 13:50 ` Pantelis Antoniou
2004-09-16 18:56 Smith, Craig
2004-09-16 20:07 ` Dan Malek
2004-09-17 5:43 ` Pantelis Antoniou
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=Pine.LNX.4.60.0409201400030.5204@dell.enoriver.com \
--to=rpjday@mindspring.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=trini@kernel.crashing.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).