<?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 Re: Linux imx change MTU size &amp;gt; 1500 in i.MX Processors</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/Linux-imx-change-MTU-size-gt-1500/m-p/833839#M128040</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;Hello,&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;&amp;nbsp; Generally, from software point of view, frame length can be configured up to &lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;16K size. According to section 22.6.4.5 (Frame length/type verification: frame length &lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;check) of the i.MX 6UL Reference Manual:&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;&amp;nbsp; “When the receive frame length exceeds MAX_FL bytes, the BABR interrupt is generated&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;and the RxBD[LG] bit is set.&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;&amp;nbsp; The frame is not truncated unless the frame length exceeds the value programmed in&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;ENETn_FTRL[TRUNC_FL].” &lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;&amp;nbsp; Bit fields MAX_FL of Receive Control Register (ENETx_RCR) and TRUNC_FL of &lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;Frame Truncation Length (ENETx_FTRL) are 14-bit values. &lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;&amp;nbsp; The problem is that ENET hardware does not support Jumbo frames directly. &lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;In particular, FIFO is not sized for jumbo frames. This means data lost can take place&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;with high probability.&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&amp;nbsp;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;Have a great day,&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;Yuri&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;------------------------------------------------------------------------------&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;Note: If this post answers your question, please click the Correct Answer &lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;button. Thank you!&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 15 Aug 2018 05:17:55 GMT</pubDate>
    <dc:creator>Yuri</dc:creator>
    <dc:date>2018-08-15T05:17:55Z</dc:date>
    <item>
      <title>Linux imx change MTU size &gt; 1500</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Linux-imx-change-MTU-size-gt-1500/m-p/833837#M128038</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;we&amp;nbsp; need to change MTU size more than 1500 default on imx6ull/ul&amp;nbsp; &amp;nbsp;linux&amp;nbsp;imx&lt;/P&gt;&lt;P&gt;ifconfig&amp;nbsp;eth0 mtu&amp;nbsp;2000&lt;/P&gt;&lt;P&gt;we get&lt;/P&gt;&lt;P&gt;ifconfig&amp;nbsp;: SIOCSIFMTU invalid argument&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please explain how to change MTU size in linux&amp;nbsp;imx?&lt;/P&gt;&lt;P&gt;How can we can add Jumbo packet support on imx6?&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Vladimir&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 09 Aug 2018 09:33:21 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Linux-imx-change-MTU-size-gt-1500/m-p/833837#M128038</guid>
      <dc:creator>vladimirchernin</dc:creator>
      <dc:date>2018-08-09T09:33:21Z</dc:date>
    </item>
    <item>
      <title>Re: Linux imx change MTU size &gt; 1500</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Linux-imx-change-MTU-size-gt-1500/m-p/833838#M128039</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The original IEEE 802.3 Ethernet standard defines the Ethernet frame structure with MTU (i.e. frame payload size in bytes) in range of 46 to 1500. The higher values of MTU can be achieved using so-called Jumbo frames. However, this type of frames is not defined by the IEEE 802.3 standard and depends on the particular network equipment vendor. So, the ENET controllers of the i.MX series processors do not support the Jumbo frames and their highest MTU value is 1500 according to the IEEE 802.3 standard.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Have a great day,&lt;BR /&gt;Artur&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>Tue, 14 Aug 2018 09:20:43 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Linux-imx-change-MTU-size-gt-1500/m-p/833838#M128039</guid>
      <dc:creator>art</dc:creator>
      <dc:date>2018-08-14T09:20:43Z</dc:date>
    </item>
    <item>
      <title>Re: Linux imx change MTU size &gt; 1500</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Linux-imx-change-MTU-size-gt-1500/m-p/833839#M128040</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;Hello,&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;&amp;nbsp; Generally, from software point of view, frame length can be configured up to &lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;16K size. According to section 22.6.4.5 (Frame length/type verification: frame length &lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;check) of the i.MX 6UL Reference Manual:&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;&amp;nbsp; “When the receive frame length exceeds MAX_FL bytes, the BABR interrupt is generated&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;and the RxBD[LG] bit is set.&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;&amp;nbsp; The frame is not truncated unless the frame length exceeds the value programmed in&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;ENETn_FTRL[TRUNC_FL].” &lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;&amp;nbsp; Bit fields MAX_FL of Receive Control Register (ENETx_RCR) and TRUNC_FL of &lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;Frame Truncation Length (ENETx_FTRL) are 14-bit values. &lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;&amp;nbsp; The problem is that ENET hardware does not support Jumbo frames directly. &lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;In particular, FIFO is not sized for jumbo frames. This means data lost can take place&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;with high probability.&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&amp;nbsp;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;Have a great day,&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;Yuri&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;------------------------------------------------------------------------------&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;Note: If this post answers your question, please click the Correct Answer &lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;button. Thank you!&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 15 Aug 2018 05:17:55 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Linux-imx-change-MTU-size-gt-1500/m-p/833839#M128040</guid>
      <dc:creator>Yuri</dc:creator>
      <dc:date>2018-08-15T05:17:55Z</dc:date>
    </item>
    <item>
      <title>Re: Linux imx change MTU size &gt; 1500</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Linux-imx-change-MTU-size-gt-1500/m-p/833840#M128041</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi!&lt;/P&gt;&lt;P&gt;Yuri thank you for your answer.&lt;/P&gt;&lt;P&gt;If we need to get one Jumbo&amp;nbsp; in second for example&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is it will work? Can i support Jumbo packets at 10&amp;nbsp;Mbps or 5&amp;nbsp;&lt;SPAN style="background-color: #f6d5d9;"&gt;Mbps?&amp;nbsp;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="background-color: #f6d5d9;"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="background-color: #f6d5d9;"&gt;&lt;SPAN&gt;Thanks&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="background-color: #f6d5d9;"&gt;&lt;SPAN&gt;Vladimir&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 15 Aug 2018 07:50:10 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Linux-imx-change-MTU-size-gt-1500/m-p/833840#M128041</guid>
      <dc:creator>vladimirchernin</dc:creator>
      <dc:date>2018-08-15T07:50:10Z</dc:date>
    </item>
    <item>
      <title>Re: Linux imx change MTU size &gt; 1500</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Linux-imx-change-MTU-size-gt-1500/m-p/833841#M128042</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;&amp;nbsp; It would be possible in store and forward disable mode (defined by bit STRFWD in &lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;Transmit FIFO Watermark Register [ENETx_TFWR]. But section 22.6.8.4&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class=""&gt;(Received &lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;frame discard) of the 6UL RM states, that the receive FIFO must be operated &lt;/SPAN&gt;&lt;SPAN class=""&gt;in store &lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;and forward mode. &lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;&amp;nbsp; Nevertheless, customers can try the store and forward disable mode. &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Yuri.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 15 Aug 2018 08:00:48 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Linux-imx-change-MTU-size-gt-1500/m-p/833841#M128042</guid>
      <dc:creator>Yuri</dc:creator>
      <dc:date>2018-08-15T08:00:48Z</dc:date>
    </item>
    <item>
      <title>Re: Linux imx change MTU size &gt; 1500</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Linux-imx-change-MTU-size-gt-1500/m-p/833842#M128043</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello!&lt;/P&gt;&lt;P&gt;Do i need to change the&amp;nbsp;&amp;nbsp;&lt;SPAN style="color: #51626f; background-color: #ffffff;"&gt;ENETx_RCR&amp;nbsp;&lt;SPAN&gt;ENETx_FTRL&amp;nbsp;&lt;SPAN style="background-color: #ffffff;"&gt;ENETx_TFWR registers&amp;nbsp; only to allow Jumbo packets&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626f; background-color: #ffffff;"&gt;&lt;SPAN style="background-color: #ffffff;"&gt;Do i need to patch Freescale&amp;nbsp;FEC driver?&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626f; background-color: #ffffff;"&gt;&lt;SPAN style="background-color: #ffffff;"&gt;if you know any patch like this please&amp;nbsp;find out!&amp;nbsp;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626f; background-color: #ffffff;"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626f; background-color: #ffffff;"&gt;&lt;SPAN style="background-color: #ffffff;"&gt;Regards&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626f; background-color: #ffffff;"&gt;&lt;SPAN style="background-color: #ffffff;"&gt;Vladimir&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 16 Aug 2018 08:57:24 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Linux-imx-change-MTU-size-gt-1500/m-p/833842#M128043</guid>
      <dc:creator>vladimirchernin</dc:creator>
      <dc:date>2018-08-16T08:57:24Z</dc:date>
    </item>
    <item>
      <title>Re: Linux imx change MTU size &gt; 1500</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Linux-imx-change-MTU-size-gt-1500/m-p/833843#M128044</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp; Yes, it is needed to disable&amp;nbsp;&lt;SPAN style="color: #51626f; background-color: #ffffff;"&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;store and forward mode, configure&amp;nbsp;&lt;SPAN&gt;FIFO watermarks&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626f; background-color: #ffffff;"&gt;&lt;SPAN&gt;and provide enough buffers for data (to load the jumbo frames). It will require&amp;nbsp;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626f; background-color: #ffffff;"&gt;&lt;SPAN&gt;to modify NXP ENET / FEC driver. We do not have patches for the Jumbo, sorry.&amp;nbsp;&amp;nbsp;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Yuri.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 17 Aug 2018 04:10:33 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Linux-imx-change-MTU-size-gt-1500/m-p/833843#M128044</guid>
      <dc:creator>Yuri</dc:creator>
      <dc:date>2018-08-17T04:10:33Z</dc:date>
    </item>
    <item>
      <title>Re: Linux imx change MTU size &gt; 1500</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Linux-imx-change-MTU-size-gt-1500/m-p/833844#M128045</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello&lt;/P&gt;&lt;P&gt;I have done the patch I&amp;nbsp;can receive a frame of 2002 bytes with the disabled store and forward.&lt;/P&gt;&lt;P&gt;i&amp;nbsp; have changed registries&amp;nbsp;&lt;SPAN style="color: #51626f; background-color: #ffffff;"&gt;ENETx_RCR&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN style="color: #51626f; border: 0px; font-size: 14px;"&gt;ENETx_FTRL&amp;nbsp;&lt;SPAN style="background-color: #ffffff; border: 0px; font-weight: inherit; font-size: 14px;"&gt;ENETx_TFWR&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;plus&amp;nbsp;FEC_ENET_RX_FRSIZE&amp;nbsp;&lt;/P&gt;&lt;P&gt;FEC_ENET_TX_FRSIZE&lt;/P&gt;&lt;P&gt;What did i miss?&lt;/P&gt;&lt;P&gt;2000 bytes is FIFO maximum on imx6ul?&lt;/P&gt;&lt;P&gt;i&amp;nbsp;haven't&amp;nbsp;found config of Maximum Receive Buffer Size Register ENETx_MRBR its located in ref. manual&amp;nbsp;22.5.23&amp;nbsp;&lt;/P&gt;&lt;P&gt;but i don't&amp;nbsp;see it in the code&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Vladimir&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 20 Aug 2018 14:28:09 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Linux-imx-change-MTU-size-gt-1500/m-p/833844#M128045</guid>
      <dc:creator>vladimirchernin</dc:creator>
      <dc:date>2018-08-20T14:28:09Z</dc:date>
    </item>
    <item>
      <title>Re: Linux imx change MTU size &gt; 1500</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Linux-imx-change-MTU-size-gt-1500/m-p/833845#M128046</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Vladimir,&lt;/P&gt;&lt;P&gt;I'm interested in your patch to support jumbo frames. Can I have a look at it, please?&lt;/P&gt;&lt;P&gt;Kind regards&lt;/P&gt;&lt;P&gt;F B&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 08 May 2020 08:24:15 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Linux-imx-change-MTU-size-gt-1500/m-p/833845#M128046</guid>
      <dc:creator>fbre</dc:creator>
      <dc:date>2020-05-08T08:24:15Z</dc:date>
    </item>
    <item>
      <title>Re: Linux imx change MTU size &gt; 1500</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Linux-imx-change-MTU-size-gt-1500/m-p/833846#M128047</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi!&lt;/P&gt;&lt;P&gt;It works you can get 2000 mtu but i cannot give it for free.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 18 May 2020 15:07:59 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Linux-imx-change-MTU-size-gt-1500/m-p/833846#M128047</guid>
      <dc:creator>vladimirchernin</dc:creator>
      <dc:date>2020-05-18T15:07:59Z</dc:date>
    </item>
    <item>
      <title>Re: Linux imx change MTU size &gt; 1500</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Linux-imx-change-MTU-size-gt-1500/m-p/833847#M128048</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;As far as I know changes to this driver have to be public by license.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 25 May 2020 09:20:53 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Linux-imx-change-MTU-size-gt-1500/m-p/833847#M128048</guid>
      <dc:creator>fbre</dc:creator>
      <dc:date>2020-05-25T09:20:53Z</dc:date>
    </item>
    <item>
      <title>Re: Linux imx change MTU size &gt; 1500</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Linux-imx-change-MTU-size-gt-1500/m-p/1229804#M169381</link>
      <description>&lt;P&gt;We are streaming raw images to the board through ethernet and for us it is very important to be able to run jumbo packets to lower the overhead. In the i.MX8 reference manual (IMX8MDQLQRM.pdf) chapter 11.5.4.1 the 9000 octets&amp;nbsp; packets are mentioned in multiple tables and there is a note stating:&lt;BR /&gt;"Although the IEEE specification defines a maximum frame length, the MAC core provides the flexibility to program any value for the frame maximum length."&lt;/P&gt;&lt;P&gt;So my question is if the limitation not valid for i.MX8 and only i.MX6 and earlier? Jumbo packets is crucial for our selection of platform. Secondly I wonder if the solution above is enough for running jumbo pakets.&lt;/P&gt;&lt;P&gt;Thank you!&lt;/P&gt;</description>
      <pubDate>Thu, 11 Feb 2021 10:30:35 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Linux-imx-change-MTU-size-gt-1500/m-p/1229804#M169381</guid>
      <dc:creator>carl_ex</dc:creator>
      <dc:date>2021-02-11T10:30:35Z</dc:date>
    </item>
  </channel>
</rss>

