From: Pantelis Antoniou <panto@intracom.gr>
To: Sanjeev R <sanjeevr@myw.ltindia.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Configuring Both the FECs in MPC880: FEC driver
Date: Fri, 30 Apr 2004 13:46:04 +0300 [thread overview]
Message-ID: <40922E6C.6070209@intracom.gr> (raw)
In-Reply-To: <s0926a35.058@EMAIL>
Sanjeev R wrote:
>Hi,
>
>There are two FECs availbale in MPC880, and i need to use/configure both of them.
>I saw the driver code fec.c available in the ELDK distribution, but it supports only one. It has the provision to adapt when an SCC is configured as ethernet,
>but when I have to configure two FECs available ?? how do i proceed?
>
>Thanks
>Sanjeev
>
>
>
>
>
>
Wait a little bit, I have it my pipeline.
Regards
Pantelis
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2004-04-30 10:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-30 9:31 Configuring Both the FECs in MPC880: FEC driver Sanjeev R
2004-04-30 10:46 ` Pantelis Antoniou [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=40922E6C.6070209@intracom.gr \
--to=panto@intracom.gr \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=sanjeevr@myw.ltindia.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).