From: David Miller <davem@davemloft.net>
To: igal.liberman@freescale.com
Cc: netdev@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
linux-kernel@vger.kernel.org, scottwood@freescale.com,
madalin.bucur@freescale.com, pebolle@tiscali.nl,
joakim.tjernlund@transmode.se, ppc@mindchasers.com,
stephen@networkplumber.org, afleming@gmail.com, knneth@gmail.com
Subject: Re: [v10, 0/6] Freescale DPAA FMan
Date: Sun, 27 Dec 2015 21:14:03 -0500 (EST) [thread overview]
Message-ID: <20151227.211403.242539822762320022.davem@davemloft.net> (raw)
In-Reply-To: <1450657290-6644-1-git-send-email-igal.liberman@freescale.com>
From: <igal.liberman@freescale.com>
Date: Mon, 21 Dec 2015 02:21:24 +0200
> The Freescale Data Path Acceleration Architecture (DPAA) is a set
> of hardware components on specific QorIQ multicore processors.
> This architecture provides the infrastructure to support
> simplified sharing of networking interfaces and accelerators
> by multiple CPU cores and the accelerators.
>
> One of the DPAA accelerators is the Frame Manager (FMan)
> which contains a series of hardware blocks: ports, Ethernet MACs,
> a multi user RAM (MURAM) and Storage Profile (SP).
>
> This patch set introduce the FMan drivers.
> Each driver configures and initializes the corresponding
> FMan hardware module (described above).
> The MAC driver offers support for three different
> types of MACs (eTSEC, TGEC, MEMAC).
Series applied, thanks.
prev parent reply other threads:[~2015-12-28 2:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-21 0:21 [v10, 0/6] Freescale DPAA FMan igal.liberman
2015-12-21 0:21 ` [v10, 1/6] fsl/fman: Add FMan MURAM support igal.liberman
2015-12-21 0:21 ` [v10, 2/6] fsl/fman: Add FMan support igal.liberman
2015-12-21 0:21 ` [v10, 3/6] fsl/fman: Add FMan MAC support igal.liberman
2015-12-21 0:21 ` [v10, 4/6] fsl/fman: Add FMan SP support igal.liberman
2015-12-21 0:21 ` [v10, 5/6] fsl/fman: Add FMan Port Support igal.liberman
2015-12-21 0:21 ` [v10, 6/6] fsl/fman: Add FMan MAC driver igal.liberman
2015-12-28 2:14 ` David Miller [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=20151227.211403.242539822762320022.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=afleming@gmail.com \
--cc=igal.liberman@freescale.com \
--cc=joakim.tjernlund@transmode.se \
--cc=knneth@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=madalin.bucur@freescale.com \
--cc=netdev@vger.kernel.org \
--cc=pebolle@tiscali.nl \
--cc=ppc@mindchasers.com \
--cc=scottwood@freescale.com \
--cc=stephen@networkplumber.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).