From: Scott Wood <scottwood@freescale.com>
To: <madalin.bucur@freescale.com>
Cc: <netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linuxppc-dev@lists.ozlabs.org>,
Igal.Liberman <igal.liberman@freescale.com>
Subject: Re: [PATCH 00/12] Freescale DPAA FMan
Date: Wed, 10 Jun 2015 13:52:12 -0500 [thread overview]
Message-ID: <1433962332.2477.118.camel@freescale.com> (raw)
In-Reply-To: <1433949712-5648-1-git-send-email-madalin.bucur@freescale.com>
On Wed, 2015-06-10 at 18:21 +0300, Madalin Bucur wrote:
> 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 introduced the FMan driver code that configures
> and initializes the FMan hardware blocks, offering support for
> three different types of MACs (DTSEC, TGEC, MEMAC).
>
> The first 6 patches present the FMan Foundation Libraries (FLIBs).
> The FMan drivers make use of the basic API the FMan FLib provides
> to configure and control the FMan hardware. The remaining patches
> present the required FMan hardware module drivers.
>
> The driver structure and a hint on file naming:
> --------------------------------
> > FMan MAC driver | mac* files
> ------ ------ ----- ------- ----
> > FMan | Port | MAC | MURAM | SP | fm_* files
> ------ ------ ----- ------- ----
> : : FLib : : fman_* files
> -------------------
>
> This submission is based on the prior Freescale DPAA FMan V3,RFC
> submission. Several issues addresses in this submission:
> - Reduced MAC layering and complexity
> - Reduced code base
> - T1024/T2080 10G best effort support
How is this different from the patchset Igal posted 7 hours earlier?
Please don't use the chained reply option in git send-email (and the
patches are in the wrong order, which makes the chained reply
especially bad).
I don't see any mention of a dependency on the qbman patches.
Where is the actual ethernet driver -- the part that sends and
receives packets?
-Scott
prev parent reply other threads:[~2015-06-10 19:08 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-10 15:21 [PATCH 00/12] Freescale DPAA FMan Madalin Bucur
2015-06-10 15:21 ` [PATCH 07/12] fsl/fman: Add FMan MURAM support Madalin Bucur
2015-06-10 15:21 ` [PATCH 01/12] fsl/fman: Add the FMan FLIB headers Madalin Bucur
2015-06-10 15:21 ` [PATCH 08/12] fsl/fman: Add Frame Manager support Madalin Bucur
2015-06-10 15:21 ` [PATCH 02/12] fsl/fman: Add the FMan FLIB Madalin Bucur
2015-06-10 15:21 ` [PATCH 09/12] fsl/fman: Add FMan MAC support Madalin Bucur
2015-06-10 15:21 ` [PATCH 03/12] fsl/fman: Add the FMan port FLIB headers Madalin Bucur
2015-06-10 15:21 ` [PATCH 10/12] fsl/fman: Add FMan SP support Madalin Bucur
2015-06-10 15:21 ` [PATCH 04/12] fsl/fman: Add the FMan port FLIB Madalin Bucur
2015-06-10 15:21 ` [PATCH 11/12] fsl/fman: Add FMan Port Support Madalin Bucur
2015-06-10 15:21 ` [PATCH 05/12] fsl/fman: Add the FMan MAC FLIB headers Madalin Bucur
2015-06-10 15:21 ` [PATCH 12/12] fsl/fman: Add FMan MAC driver Madalin Bucur
2015-06-10 15:21 ` [PATCH 06/12] fsl/fman: Add the FMan MAC FLIB Madalin Bucur
2015-06-11 8:55 ` [PATCH 08/12] fsl/fman: Add Frame Manager support Paul Bolle
2015-06-11 9:37 ` Paul Bolle
2015-06-15 14:23 ` Liberman Igal
2015-06-16 3:42 ` Bob Cochran
2015-06-16 4:33 ` Scott Wood
2015-06-10 18:54 ` [PATCH 01/12] fsl/fman: Add the FMan FLIB headers Scott Wood
2015-06-17 14:59 ` Liberman Igal
2015-06-17 17:57 ` Scott Wood
2015-06-10 18:52 ` Scott Wood [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=1433962332.2477.118.camel@freescale.com \
--to=scottwood@freescale.com \
--cc=igal.liberman@freescale.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=madalin.bucur@freescale.com \
--cc=netdev@vger.kernel.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).