<?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>topic Enetc Layer 2 offset in Layerscape</title>
    <link>https://community.nxp.com/t5/Layerscape/Enetc-Layer-2-offset/m-p/1655674#M12531</link>
    <description>&lt;P&gt;We have the possibility to add an offset before MAC address on LS1028a ENETC?&lt;/P&gt;&lt;P&gt;Layer 2 offset. The number of octet pairs from the start of the frame that the parser should expect to see&lt;BR /&gt;before the first byte of the Ethernet DA.&lt;/P&gt;</description>
    <pubDate>Tue, 23 May 2023 11:35:52 GMT</pubDate>
    <dc:creator>suleyrezoaaaa</dc:creator>
    <dc:date>2023-05-23T11:35:52Z</dc:date>
    <item>
      <title>Enetc Layer 2 offset</title>
      <link>https://community.nxp.com/t5/Layerscape/Enetc-Layer-2-offset/m-p/1655674#M12531</link>
      <description>&lt;P&gt;We have the possibility to add an offset before MAC address on LS1028a ENETC?&lt;/P&gt;&lt;P&gt;Layer 2 offset. The number of octet pairs from the start of the frame that the parser should expect to see&lt;BR /&gt;before the first byte of the Ethernet DA.&lt;/P&gt;</description>
      <pubDate>Tue, 23 May 2023 11:35:52 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Layerscape/Enetc-Layer-2-offset/m-p/1655674#M12531</guid>
      <dc:creator>suleyrezoaaaa</dc:creator>
      <dc:date>2023-05-23T11:35:52Z</dc:date>
    </item>
    <item>
      <title>Re: Enetc Layer 2 offset</title>
      <link>https://community.nxp.com/t5/Layerscape/Enetc-Layer-2-offset/m-p/1661407#M12586</link>
      <description>&lt;P&gt;&lt;SPAN&gt;If you expect that the parser to be able to interpret the frame as Ethernet and continue parsing, the answer is that ENETC will stop the parsing process depending on the value that will be found at eth_type position. The parser is not able to parse a custom header that is added in front of the DMAC. You will receive the frame&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;but its type will not be reflected in the parser summary.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;To conclude, parser is not able to go further than L2. It's up to the software layer you have, to decode the received frame&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 01 Jun 2023 02:50:22 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Layerscape/Enetc-Layer-2-offset/m-p/1661407#M12586</guid>
      <dc:creator>yipingwang</dc:creator>
      <dc:date>2023-06-01T02:50:22Z</dc:date>
    </item>
  </channel>
</rss>

