<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="/source/rss.xsl.xml"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
    <title>Changes in dpaa_common.c</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>7a40b8a89e7da2a7e8d8e132bc37885b22e9bfb1 - dpaa: Fix copyright headers</title>
        <link>http://kernelsources.org:8080/source/history/freebsd/sys/dev/dpaa/dpaa_common.c#7a40b8a89e7da2a7e8d8e132bc37885b22e9bfb1</link>
        <description>dpaa: Fix copyright headersReported by:	ziaee@Fixes:	fd8d34ce27 (&quot;dpaa: Migrate from NCSW base to a home-grown driver&quot;)

            List of files:
            /freebsd/sys/dev/dpaa/dpaa_common.c</description>
        <pubDate>Mon, 04 May 2026 03:43:44 +0200</pubDate>
        <dc:creator>Justin Hibbits &lt;jhibbits@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>fd8d34ce272ba40f3e0218198ba542a29c390a4a - dpaa: Migrate from NCSW base to a home-grown driver</title>
        <link>http://kernelsources.org:8080/source/history/freebsd/sys/dev/dpaa/dpaa_common.c#fd8d34ce272ba40f3e0218198ba542a29c390a4a</link>
        <description>dpaa: Migrate from NCSW base to a home-grown driverThe NCSW reference base requires tuning for each target, and currentlyis configured for FMANv2.  This doesn&apos;t readily work on FMANv3 devices,such as the T-series powerpc, or the LS1043 ARM.  Since Freescale/NXPabandoned the NCSW driver a decade ago, it makes sense to abandon itourselves as well.  This new driver uses a combination of the NCSWdriver and the Linux driver (BSD/GPL dual licensed) as a reference, butcontains no actual code from them.The DPAA (Data Path Acceleration Architecture) subsystem consists of thefollowing components:* BMan -- Buffer Manager.  Manages buffer pools of different sizes (one  size per pool, up to 64 pools)* QMan -- Queue Manager.  Manages the interfaces between DPAA-based  components and the CPU(s).* FMan -- Frame Manager.  Responsible for all ethernet-related  processing.  Consists itself of the following components:  * Ports -- interfaces to the QMan.  An ethernet interface consists of    2 ports.    Ports use &quot;Next-invoked action&quot; (NIA) descriptors to form a pipeline    for processing on receive and transmit.  * Parser -- performs protocol header parsing and validation.  Both    hardware and software parsers are available.  * KeyGen -- Key generator, used to start the classification process    (for the Policer), generating FQIDs and other keys based on the    frame input.  * Policer -- performs traffic shaping and classification* MAC -- SoC specific ethernet MAC (dTSEC, TGEC, mEMAC).  Currently  supports dTSEC and mEMAC, along with their MDIO blocks.Additional components not yet handled:SEC -- Security engine (crypto)RE -- RAID engineRapidIODCE -- Decompression/Compression engine, supports ZLIB, DEFLATE, andGZIP, as well as base64 encoding and decoding.BMan and QMan are accessed via cache-coherent portals, using ringbuffers as I/O.  The intent is for portals to be per-CPU (core/thread)to reduce locking contention and improve performance.  This driver pinsinterrupt handlers to the CPU &quot;owning&quot; a given portal, and uses criticalsections to prevent switching while accessing the portal.

            List of files:
            /freebsd/sys/dev/dpaa/dpaa_common.c</description>
        <pubDate>Fri, 24 Apr 2026 05:38:19 +0200</pubDate>
        <dc:creator>Justin Hibbits &lt;jhibbits@FreeBSD.org&gt;</dc:creator>
    </item>
</channel>
</rss>
