From: "T Michael Turney" <tmike@recipes4linux.com>
To: <linuxppc-embedded@lists.linuxppc.org>
Subject: FEC support for 8260 in kernel 2.4.25
Date: Fri, 23 Apr 2004 16:23:37 -0700 [thread overview]
Message-ID: <GEEKLLHMFHLAJOBEEELHGEDNCJAA.tmike@recipes4linux.com> (raw)
Hi Folks,
This is my first posting on this list.
I am working on a kernel port to an 8260 board that
has all three FCCs wired up to PHYs (BCM5221).
The first FCC is working fine, but I haven't been
successful with getting FCC2 and FCC3 going yet.
Is anybody out there successfully using the 2.4.x
fcc_enet.c code with all three channels active?
Cheers,
T.mike
Tools Made Tough
Project Consultant
(o) 760.728.5401
(c) 760.415.8792
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2004-04-23 23:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-23 23:23 T Michael Turney [this message]
2004-04-24 0:18 ` FEC support for 8260 in kernel 2.4.25 Ricardo Scop
2004-04-24 3:10 ` Dan Malek
2004-04-25 8:32 ` Jaap-Jan Boor
-- strict thread matches above, loose matches on Subject: below --
2004-04-26 18:48 Andrew Williams
2004-04-28 2:22 ` T Michael Turney
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=GEEKLLHMFHLAJOBEEELHGEDNCJAA.tmike@recipes4linux.com \
--to=tmike@recipes4linux.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).