<?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>i.MX ProcessorsのトピックRe: Chromium browser on 4.14 Kernel</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/Chromium-browser-on-4-14-Kernel/m-p/749531#M116652</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi vishwanath,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can check with yocto community since nxp release going on yocto morty.&amp;nbsp; Do not think chromium will have the patches.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 06 Jun 2018 14:46:10 GMT</pubDate>
    <dc:creator>Bio_TICFSL</dc:creator>
    <dc:date>2018-06-06T14:46:10Z</dc:date>
    <item>
      <title>Chromium browser on 4.14 Kernel</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Chromium-browser-on-4-14-Kernel/m-p/749530#M116651</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;BR /&gt;We are using&amp;nbsp;using mainline bsp with&amp;nbsp;&lt;A data-pjax="true" href="https://github.com/Freescale/linux-fslc/commit/fe88b0b06a4a31bf9477bfc219229a715eda4be7" style="color: #0366d6; background-color: #f6f8fa; text-decoration: underline;" title="Merge tag 'v4.14.22' into 4.14.x+fslc  This is the 4.14.22 stable release  * tag 'v4.14.22': (770 commits)   Linux 4.14.22   vmalloc: fix __GFP_HIGHMEM usage for vmalloc_32 on 32b systems   mei: me: add cannon point device ids for 4th device   mei: me: add cannon point device ids   crypto: s5p-sss - Fix kernel Oops in AES-ECB mode   drm/i915: fix intel_backlight_device_register declaration   crypto: talitos - fix Kernel Oops on hashing an empty file   hippi: Fix a Fix a possible sleep-in-atomic bug in rr_close   powerpc/perf/imc: Fix nest-imc cpuhotplug callback failure   PCI: rcar: Fix use-after-free in probe error path   xen: XEN_ACPI_PROCESSOR is Dom0-only   platform/x86: dell-laptop: Fix keyboard max lighting for Dell Latitude E6410   x86/mm/kmmio: Fix mmiotrace for page unaligned addresses   mm/early_ioremap: Fix boot hang with earlyprintk=efi,keep   usb: dwc3: of-simple: fix missing clk_disable_unprepare   usb: dwc3: gadget: Wait longer for controller to end command processing   dmaengine: jz4740: disable/unprepare clk if probe fails   drm/vc4: Release fence after signalling   ASoC: rsnd: ssi: fix race condition in rsnd_ssi_pointer_update   drm/armada: fix leak of crtc structure   ..."&gt;4.14.x+fslc&lt;/A&gt;&amp;nbsp;,and We are trying chromium with&amp;nbsp; X11 .We have few queries&lt;/P&gt;&lt;P&gt;1)Chromum-imx patch's&amp;nbsp;for&amp;nbsp;latest meta-browser (rocko branch).&lt;/P&gt;&lt;P&gt;2)Since mainline bsp uses mesa graphics library instead of imx-viv-gpu .Does chromum-imx patches required to integrate .&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 04 Jun 2018 22:08:27 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Chromium-browser-on-4-14-Kernel/m-p/749530#M116651</guid>
      <dc:creator>vishwanchandapu</dc:creator>
      <dc:date>2018-06-04T22:08:27Z</dc:date>
    </item>
    <item>
      <title>Re: Chromium browser on 4.14 Kernel</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Chromium-browser-on-4-14-Kernel/m-p/749531#M116652</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi vishwanath,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can check with yocto community since nxp release going on yocto morty.&amp;nbsp; Do not think chromium will have the patches.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 06 Jun 2018 14:46:10 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Chromium-browser-on-4-14-Kernel/m-p/749531#M116652</guid>
      <dc:creator>Bio_TICFSL</dc:creator>
      <dc:date>2018-06-06T14:46:10Z</dc:date>
    </item>
  </channel>
</rss>

