<?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: PREEMPT_RT on Linux QoriQ in Layerscape</title>
    <link>https://community.nxp.com/t5/Layerscape/PREEMPT-RT-on-Linux-QoriQ/m-p/2418187#M16904</link>
    <description>&lt;P class="p8i6j03 paragraph"&gt;So, if you mean the next 6.18-based RT update, the current roadmap points to &lt;STRONG&gt;Real-Time Edge 3.6 in December 2026&lt;/STRONG&gt;. &lt;A id="base-ui-:r5j3:" class="wdbi343 wdbi341 _1ibi0s3ei _1ibi0s38m" tabindex="0" role="button" href="https://nxp1.sharepoint.com/teams/210_48/Shared%20Documents/Partners/Partner%20Calls/2026/Q2%202026%20Partner%20Update%20Call/Q2%202026%20Partner%20Update%20for%20MCU%20%26%20MPU%20(slides).pdf?web=1" rel="noreferrer" aria-expanded="false" aria-haspopup="dialog" data-base-ui-click-trigger="" data-label="3" aria-label="Citation 3" target="_blank"&gt;&lt;/A&gt;&lt;/P&gt;
&lt;P class="p8i6j03 paragraph"&gt;Note that the standard i.MX Linux BSP—not RT—already has newer 6.18 releases, including &lt;STRONG&gt;6.18.37 on September 24, 2026&lt;/STRONG&gt;. &lt;A id="base-ui-:r5j6:" class="wdbi343 wdbi341 _1ibi0s3ei _1ibi0s38m" tabindex="0" role="button" href="https://www.nxp.com/docs/en/release-note/RN00210.pdf" rel="noreferrer" aria-expanded="false" aria-haspopup="dialog" data-base-ui-click-trigger="" data-label="4" aria-label="Citation 4" target="_blank"&gt;&lt;/A&gt;&lt;/P&gt;
&lt;P class="p8i6j03 paragraph"&gt;Regards&lt;/P&gt;</description>
    <pubDate>Fri, 02 Oct 2026 15:48:02 GMT</pubDate>
    <dc:creator>Bio_TICFSL</dc:creator>
    <dc:date>2026-10-02T15:48:02Z</dc:date>
    <item>
      <title>PREEMPT_RT on Linux QoriQ</title>
      <link>https://community.nxp.com/t5/Layerscape/PREEMPT-RT-on-Linux-QoriQ/m-p/2417891#M16901</link>
      <description>&lt;P&gt;&lt;SPAN&gt;Hi,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;we are currently using the NXP QorIQ Linux kernel from the &lt;/SPAN&gt;&lt;SPAN&gt;linux-6.12-rt&lt;/SPAN&gt;&lt;SPAN&gt; branch, but we would like to move to a newer kernel version, possibly Linux 6.18.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;I have a few questions regarding the RT kernel support and branch strategy:&lt;/SPAN&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;&lt;SPAN&gt;What exactly is the difference between &lt;/SPAN&gt;&lt;SPAN&gt;linux-6.12-rt&lt;/SPAN&gt;&lt;SPAN&gt; and &lt;/SPAN&gt;&lt;SPAN&gt;lf-6.12.y&lt;/SPAN&gt;&lt;SPAN&gt;?&lt;/SPAN&gt;&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;SPAN&gt;Is a separate &lt;/SPAN&gt;&lt;SPAN&gt;linux-6.18-rt&lt;/SPAN&gt;&lt;SPAN&gt; branch planned, similarly to &lt;/SPAN&gt;&lt;SPAN&gt;linux-6.12-rt&lt;/SPAN&gt;&lt;SPAN&gt;?&lt;/SPAN&gt;&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;SPAN&gt;If not, is &lt;/SPAN&gt;&lt;SPAN&gt;lf-6.18.y&lt;/SPAN&gt;&lt;SPAN&gt; intended to be used directly with &lt;/SPAN&gt;&lt;SPAN&gt;CONFIG_PREEMPT_RT=y&lt;/SPAN&gt;&lt;SPAN&gt;?&lt;/SPAN&gt;&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;SPAN&gt;My understanding is that &lt;/SPAN&gt;&lt;SPAN&gt;linux-6.12-rt&lt;/SPAN&gt;&lt;SPAN&gt; contains additional PREEMPT_RT-related changes compared to &lt;/SPAN&gt;&lt;SPAN&gt;lf-6.12.y&lt;/SPAN&gt;&lt;SPAN&gt;. However, starting with Linux 6.12, the core PREEMPT_RT support has been merged into the upstream kernel:&lt;/SPAN&gt;&lt;BR /&gt;&lt;A href="https://kernel-internals.org/locking/preempt-rt/" target="_blank" rel="noopener"&gt;&lt;SPAN&gt;https://kernel-internals.org/locking/preempt-rt/&lt;/SPAN&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;At the same time, I can see that RT-specific development and stable RT patch releases still continue separately upstream.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Given this, I would like to understand how this is handled in the newer NXP QorIQ releases.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;For Linux 6.18, should we simply use the &lt;/SPAN&gt;&lt;SPAN&gt;lf-6.18.y&lt;/SPAN&gt;&lt;SPAN&gt; branch with &lt;/SPAN&gt;&lt;SPAN&gt;CONFIG_PREEMPT_RT=y&lt;/SPAN&gt;&lt;SPAN&gt;, with all NXP-specific changes required for PREEMPT_RT already included there?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Or is a separate QorIQ RT branch/release still planned, containing additional RT patches on top of &lt;/SPAN&gt;&lt;SPAN&gt;lf-6.18.y&lt;/SPAN&gt;&lt;SPAN&gt;?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;If no separate RT branch is planned, are there any additional RT patches that NXP recommends applying on top of &lt;/SPAN&gt;&lt;SPAN&gt;lf-6.18.y&lt;/SPAN&gt;&lt;SPAN&gt;?&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 01 Oct 2026 17:53:40 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Layerscape/PREEMPT-RT-on-Linux-QoriQ/m-p/2417891#M16901</guid>
      <dc:creator>pb3</dc:creator>
      <dc:date>2026-10-01T17:53:40Z</dc:date>
    </item>
    <item>
      <title>Re: PREEMPT_RT on Linux QoriQ</title>
      <link>https://community.nxp.com/t5/Layerscape/PREEMPT-RT-on-Linux-QoriQ/m-p/2418165#M16902</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;For &lt;STRONG&gt;QorIQ/Layerscape&lt;/STRONG&gt;, do not assume that &lt;CODE class="p8i6j0h"&gt;lf-6.18.y&lt;/CODE&gt; plus &lt;CODE class="p8i6j0h"&gt;CONFIG_PREEMPT_RT=y&lt;/CODE&gt; is equivalent to NXP’s supported RT release. NXP’s current Real-Time Edge material shows Linux PREEMPT_RT 6.18 releases based on LF 6.18, while internal development tracks a separate downstream RT patch stack. &lt;A id="base-ui-:rp2:" class="wdbi343 wdbi341 _1ibi0s3ei _1ibi0s38m" tabindex="0" role="button" href="https://www.nxp.com/docs/en/release-note/RN00161.pdf" rel="noreferrer" aria-expanded="false" aria-haspopup="dialog" data-base-ui-click-trigger="" data-label="1" aria-label="Citation 1" target="_blank"&gt;&lt;/A&gt;&lt;/P&gt;
&lt;P class="p8i6j03 paragraph"&gt;Use the matching NXP 6.18 RT release, preferably the latest one available for your QorIQ platform. Compare your current &lt;CODE class="p8i6j0h"&gt;linux-6.12-rt&lt;/CODE&gt; tree against the corresponding LF 6.18 base, but do not assume that enabling &lt;CODE class="p8i6j0h"&gt;CONFIG_PREEMPT_RT=y&lt;/CODE&gt; alone includes all NXP-specific RT changes.&lt;/P&gt;
&lt;P class="p8i6j03 paragraph"&gt;Also validate:&lt;/P&gt;
&lt;UL class="p8i6j09 p8i6j04"&gt;
&lt;LI class="p8i6j0c"&gt;architecture support for &lt;CODE class="p8i6j0h"&gt;ARCH_SUPPORTS_RT&lt;/CODE&gt;;&lt;/LI&gt;
&lt;LI class="p8i6j0c"&gt;NXP networking, DPAA/DPAA2, ENETC, DSA, TSN, PTP, and interrupt behavior;&lt;/LI&gt;
&lt;LI class="p8i6j0c"&gt;latency under representative load;&lt;/LI&gt;
&lt;LI class="p8i6j0c"&gt;any driver-specific RT patches in the NXP downstream stack.&lt;/LI&gt;
&lt;/UL&gt;
&lt;P class="p8i6j03 paragraph"&gt;The upstream article’s main qualification is also relevant: PREEMPT_RT became mainline-selectable in 6.12, but support is architecture-dependent and does not imply that every vendor driver has been validated for deterministic behavior&lt;/P&gt;
&lt;P class="p8i6j03 paragraph"&gt;Regards&lt;/P&gt;</description>
      <pubDate>Fri, 02 Oct 2026 13:24:04 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Layerscape/PREEMPT-RT-on-Linux-QoriQ/m-p/2418165#M16902</guid>
      <dc:creator>Bio_TICFSL</dc:creator>
      <dc:date>2026-10-02T13:24:04Z</dc:date>
    </item>
    <item>
      <title>Re: PREEMPT_RT on Linux QoriQ</title>
      <link>https://community.nxp.com/t5/Layerscape/PREEMPT-RT-on-Linux-QoriQ/m-p/2418178#M16903</link>
      <description>Thanks for clarification. Do you know when, more or less can we expect the NXP Linux 6.18 RT support release?</description>
      <pubDate>Fri, 02 Oct 2026 14:20:51 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Layerscape/PREEMPT-RT-on-Linux-QoriQ/m-p/2418178#M16903</guid>
      <dc:creator>pb3</dc:creator>
      <dc:date>2026-10-02T14:20:51Z</dc:date>
    </item>
    <item>
      <title>Re: PREEMPT_RT on Linux QoriQ</title>
      <link>https://community.nxp.com/t5/Layerscape/PREEMPT-RT-on-Linux-QoriQ/m-p/2418187#M16904</link>
      <description>&lt;P class="p8i6j03 paragraph"&gt;So, if you mean the next 6.18-based RT update, the current roadmap points to &lt;STRONG&gt;Real-Time Edge 3.6 in December 2026&lt;/STRONG&gt;. &lt;A id="base-ui-:r5j3:" class="wdbi343 wdbi341 _1ibi0s3ei _1ibi0s38m" tabindex="0" role="button" href="https://nxp1.sharepoint.com/teams/210_48/Shared%20Documents/Partners/Partner%20Calls/2026/Q2%202026%20Partner%20Update%20Call/Q2%202026%20Partner%20Update%20for%20MCU%20%26%20MPU%20(slides).pdf?web=1" rel="noreferrer" aria-expanded="false" aria-haspopup="dialog" data-base-ui-click-trigger="" data-label="3" aria-label="Citation 3" target="_blank"&gt;&lt;/A&gt;&lt;/P&gt;
&lt;P class="p8i6j03 paragraph"&gt;Note that the standard i.MX Linux BSP—not RT—already has newer 6.18 releases, including &lt;STRONG&gt;6.18.37 on September 24, 2026&lt;/STRONG&gt;. &lt;A id="base-ui-:r5j6:" class="wdbi343 wdbi341 _1ibi0s3ei _1ibi0s38m" tabindex="0" role="button" href="https://www.nxp.com/docs/en/release-note/RN00210.pdf" rel="noreferrer" aria-expanded="false" aria-haspopup="dialog" data-base-ui-click-trigger="" data-label="4" aria-label="Citation 4" target="_blank"&gt;&lt;/A&gt;&lt;/P&gt;
&lt;P class="p8i6j03 paragraph"&gt;Regards&lt;/P&gt;</description>
      <pubDate>Fri, 02 Oct 2026 15:48:02 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Layerscape/PREEMPT-RT-on-Linux-QoriQ/m-p/2418187#M16904</guid>
      <dc:creator>Bio_TICFSL</dc:creator>
      <dc:date>2026-10-02T15:48:02Z</dc:date>
    </item>
  </channel>
</rss>

