<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>T-SeriesのトピックRe: USDPAA Linux SDK 1.6</title>
    <link>https://community.nxp.com/t5/T-Series/USDPAA-Linux-SDK-1-6/m-p/612391#M1499</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Ok .. so contradicting&amp;nbsp; documentation ... speechless ...&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 23 Nov 2016 13:05:30 GMT</pubDate>
    <dc:creator>bogdantanasa</dc:creator>
    <dc:date>2016-11-23T13:05:30Z</dc:date>
    <item>
      <title>USDPAA Linux SDK 1.6</title>
      <link>https://community.nxp.com/t5/T-Series/USDPAA-Linux-SDK-1-6/m-p/612389#M1497</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am using SDK 1.6 and there seems to be a contradiction in the manual (i.e. Freescale SDK 1.6 Document Number: QORIQSDK RevB, Sept 2014) about the use of USDPAA.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I section 9.1.1.3.2.2 there is a paragraph saying that the tree property "fsl, usdpaa-portal" must be used in the device tree to indicate to the kernel that a given portal is to be used by USDPAA. However, later in the document in section 9.1.2.1.3 there is a paragraph saying that for sdk 1.2 and later versions the portals do not need to have the tree property "fsl, usdpaa-portal".&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So what I want to ask&amp;nbsp;is do I have to use "fsl, usdpaa-portal" and&amp;nbsp;"cpu-handle" to reserve some portals for USDPAA and declare their affinity or this will be done automatically when invoking b/qman_global_init?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Moreover, I am using a T4240 which has 15 QMAN pool channels. All the applications that are in the usdpaa packet come with defines like NUM_POOL_CHANNELS 4. Why is this the case? There is any way to query the number of pool&lt;/P&gt;&lt;P&gt;channels from application?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;PS: I also attach the manual to make it easy.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any help is appreciated.&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Bogdan.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 22 Nov 2016 12:51:42 GMT</pubDate>
      <guid>https://community.nxp.com/t5/T-Series/USDPAA-Linux-SDK-1-6/m-p/612389#M1497</guid>
      <dc:creator>bogdantanasa</dc:creator>
      <dc:date>2016-11-22T12:51:42Z</dc:date>
    </item>
    <item>
      <title>Re: USDPAA Linux SDK 1.6</title>
      <link>https://community.nxp.com/t5/T-Series/USDPAA-Linux-SDK-1-6/m-p/612390#M1498</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Statements in Section 9.1.2.1.3 of the SDK 1.6 Manual shall be trusted,&lt;BR /&gt;"fsl, usdpaa-portal" properties are no longer used and don't appear in &lt;BR /&gt;the Device Tree source files in newer SDKs . As of pool channels,&lt;BR /&gt;which are now allocated by a single allocator in the kernel space,&lt;BR /&gt;one (pretty straightforward)method to see how many of them are available is to call &lt;BR /&gt;qman_alloc_pool_range() with the count parameter higher than the&lt;BR /&gt;value in the "pool-channel-range" property, see what is returned,&lt;BR /&gt;deallocate unneeded. See include/usdpaa/fsl_qman.h&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Have a great day,&lt;BR /&gt;Platon&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-----------------------------------------------------------------------------------------------------------------------&lt;BR /&gt;Note: If this post answers your question, please click the Correct Answer button. Thank you!&lt;BR /&gt;-----------------------------------------------------------------------------------------------------------------------&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 23 Nov 2016 12:53:04 GMT</pubDate>
      <guid>https://community.nxp.com/t5/T-Series/USDPAA-Linux-SDK-1-6/m-p/612390#M1498</guid>
      <dc:creator>bpe</dc:creator>
      <dc:date>2016-11-23T12:53:04Z</dc:date>
    </item>
    <item>
      <title>Re: USDPAA Linux SDK 1.6</title>
      <link>https://community.nxp.com/t5/T-Series/USDPAA-Linux-SDK-1-6/m-p/612391#M1499</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Ok .. so contradicting&amp;nbsp; documentation ... speechless ...&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 23 Nov 2016 13:05:30 GMT</pubDate>
      <guid>https://community.nxp.com/t5/T-Series/USDPAA-Linux-SDK-1-6/m-p/612391#M1499</guid>
      <dc:creator>bogdantanasa</dc:creator>
      <dc:date>2016-11-23T13:05:30Z</dc:date>
    </item>
    <item>
      <title>Re: USDPAA Linux SDK 1.6</title>
      <link>https://community.nxp.com/t5/T-Series/USDPAA-Linux-SDK-1-6/m-p/612392#M1500</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Does this means that even cpu-handle&amp;nbsp;in the definition of a q/b man portal has been removed or only usdpaa-portal?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;/Bog.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 25 Nov 2016 07:46:24 GMT</pubDate>
      <guid>https://community.nxp.com/t5/T-Series/USDPAA-Linux-SDK-1-6/m-p/612392#M1500</guid>
      <dc:creator>bogdantanasa</dc:creator>
      <dc:date>2016-11-25T07:46:24Z</dc:date>
    </item>
  </channel>
</rss>

