netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: akpm@osdl.org
Cc: netdev@vger.kernel.org, tie-fei.zang@freescale.com,
	Alexandre.Bounine@tundra.com
Subject: Re: [patch 4/5] Add tsi108/9 On Chip Ethernet device driver support
Date: Tue, 14 Nov 2006 10:41:04 -0500	[thread overview]
Message-ID: <4559E390.4050205@garzik.org> (raw)
In-Reply-To: <200611090349.kA93nDBl003600@shell0.pdx.osdl.net>

akpm@osdl.org wrote:
> From: Zang Roy-r61911 <tie-fei.zang@freescale.com>
> 
> Add tsi108/9 on chip Ethernet controller driver support.
> 
> The driver code collects the feedback of previous posting form the mailing
> list and gives the update.
> 
> MPC7448HPC2 platform in arch/powerpc uses tsi108 bridge.
> 
> The following is a brief description of the Ethernet controller:
> 
> The Tsi108/9 Ethernet Controller connects Switch Fabric to two independent
> Gigabit Ethernet ports,E0 and E1.  It uses a single Management interface to
> manage the two physical connection devices (PHYs).  Each Ethernet port has
> its own statistics monitor that tracks and reports key interface
> statistics.  Each port supports a 256-entry hash table for address
> filtering.  In addition, each port is bridged to the Switch Fabric through
> a 2-Kbyte transmit FIFO and a 4-Kbyte Receive FIFO.
> 
> Each Ethernet port also has a pair of internal Ethernet DMA channels to
> support the transmit and receive data flows.  The Ethernet DMA channels use
> descriptors set up in memory, the memory map of the device, and access via
> the Switch Fabric.  The Ethernet Controller’s DMA arbiter handles
> arbitration for the Switch Fabric.  The Controller also has a register bus
> interface for register accesses and status monitor control.
> 
> The PMD (Physical Media Device) interface operates in MII, GMII, or TBI
> modes.  The MII mode is used for connecting with 10 or 100 Mbit/s PMDs. 
> The GMII and TBI modes are used to connect with Gigabit PMDs.  Internal
> data flows to and from the Ethernet Controller through the Switch Fabric. 
> Each
> 
> Ethernet port uses its transmit and receive DMA channels to manage data
> flows through buffer descriptors that are predefined by the system (the
> descriptors can exist anywhere in the system memory map).  These
> descriptors are data structures that point to buffers filled with data
> ready to transmit over Ethernet, or they point to empty buffers ready to
> receive data from Ethernet.
> 
> Signed-off-by: Alexandre Bounine <Alexandre.Bounine@tundra.com>
> Signed-off-by: Roy Zang	<tie-fei.zang@freescale.com>
> Signed-off-by: Andrew Morton <akpm@osdl.org>

applied


      reply	other threads:[~2006-11-14 15:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-09  3:49 [patch 4/5] Add tsi108/9 On Chip Ethernet device driver support akpm
2006-11-14 15:41 ` Jeff Garzik [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=4559E390.4050205@garzik.org \
    --to=jeff@garzik.org \
    --cc=Alexandre.Bounine@tundra.com \
    --cc=akpm@osdl.org \
    --cc=netdev@vger.kernel.org \
    --cc=tie-fei.zang@freescale.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).