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 _______________________________________________ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev