From: Matt Porter <mporter@embeddedalley.com>
To: Haruki Dai-r35557 <Dai.Haruki@freescale.com>
Cc: Prashant Yendigeri <Prashant.Yendigeri@lntinfotech.com>,
linuxppc-embedded@ozlabs.org
Subject: Re: Gianfar eth driver on 8540 ppc - for 2.4 and 2.6 : differentoutputs
Date: Fri, 11 Aug 2006 13:35:17 -0500 [thread overview]
Message-ID: <20060811183517.GA14324@gate.crashing.org> (raw)
In-Reply-To: <18AEF66AFDF06F4CAAA1D419D000FD3380B85B@az33exm24.fsl.freescale.net>
On Fri, Aug 11, 2006 at 11:08:59AM -0700, Haruki Dai-r35557 wrote:
> Why there are three TSEC on the MPC8540??
There aren't. There are two TSECs and one FEC on the MPC8540.
gianfar drives them all (all the non-CPM enets, that is).
-Matt
prev parent reply other threads:[~2006-08-11 18:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-10 11:18 Gianfar eth driver on 8540 ppc - for 2.4 and 2.6 : different outputs Prashant Yendigeri
2006-08-11 4:10 ` Kumar Gala
2006-08-11 11:21 ` Prashant Yendigeri
2006-08-11 12:37 ` Kumar Gala
2006-08-11 12:43 ` Prashant Yendigeri
2006-08-11 14:30 ` Matthew McClintock
2006-08-11 18:08 ` Gianfar eth driver on 8540 ppc - for 2.4 and 2.6 : differentoutputs Haruki Dai-r35557
2006-08-11 18:35 ` Matt Porter [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=20060811183517.GA14324@gate.crashing.org \
--to=mporter@embeddedalley.com \
--cc=Dai.Haruki@freescale.com \
--cc=Prashant.Yendigeri@lntinfotech.com \
--cc=linuxppc-embedded@ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.