<?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: imx6qsabresd hardware gpu acceleration  in i.MX Processors</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/imx6qsabresd-hardware-gpu-acceleration/m-p/401708#M59355</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Aida,&lt;/P&gt;&lt;P&gt;it occurs when you write larger than fb mem size. The framebuffer is a buffer of n bytes. If you write more than n bytes to it, you'll get that error. You can get the contents of the framebuffer, and also see the size of it by looking at the file size, by cat /dev/graphics/fb0 &amp;gt; foo But that doesn't explain why you don't see anything on the LCD. You can take a look at the kernel log, if any case how do you configure the video mode.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 27 Oct 2015 16:23:05 GMT</pubDate>
    <dc:creator>Bio_TICFSL</dc:creator>
    <dc:date>2015-10-27T16:23:05Z</dc:date>
    <item>
      <title>imx6qsabresd hardware gpu acceleration</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/imx6qsabresd-hardware-gpu-acceleration/m-p/401707#M59354</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello everyone,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm trying to build an image according to those parameters : &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- iMX : MCIMX6Q-SDB&lt;/P&gt;&lt;P&gt;- Using Yocto&lt;/P&gt;&lt;P&gt;- Need of QtWebkit&lt;/P&gt;&lt;P&gt;- Using the hardware GPU acceleration of Vivante &lt;/P&gt;&lt;P&gt;- With Wayland/Weston&lt;/P&gt;&lt;P&gt;- We're using a EETI eGalax Touch Screen for testing&lt;/P&gt;&lt;P&gt;- On a sdcard&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The actual purpose is to obtain the best performance possible with a HTML5 app... (400/500 FPS would be perfect :-))&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here's the problem, nothing is displayed on my screen, it's like the "Vivante driver" stops my weston server (I also tried with x-server, it stops it too).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm using &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;MACHINE="imx6qsabresd"&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;DISTRO_FEATURES += " opengl glibc ..."&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;IMAGE_INSTALL += " qt4-embedded qtwebkit qtwebkit-examples"&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;"require recipes-graphics/images/core-image-weston.bb"&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;PREFERRED_PROVIDER_virtual/kernel = "linux-imx"&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I don't know what I'm doing wrong but nothing is happening on my display. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When I try "cat /dev/urandom &amp;gt; /dev/fb0" I get a "No space left on device /dev/fb0".&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there something to change in the "imx6qsabresd.conf" ? Maybe it's a question of partition space in the sdcard ? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Aïda&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 15 Oct 2015 14:07:13 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/imx6qsabresd-hardware-gpu-acceleration/m-p/401707#M59354</guid>
      <dc:creator>aidameriem</dc:creator>
      <dc:date>2015-10-15T14:07:13Z</dc:date>
    </item>
    <item>
      <title>Re: imx6qsabresd hardware gpu acceleration</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/imx6qsabresd-hardware-gpu-acceleration/m-p/401708#M59355</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Aida,&lt;/P&gt;&lt;P&gt;it occurs when you write larger than fb mem size. The framebuffer is a buffer of n bytes. If you write more than n bytes to it, you'll get that error. You can get the contents of the framebuffer, and also see the size of it by looking at the file size, by cat /dev/graphics/fb0 &amp;gt; foo But that doesn't explain why you don't see anything on the LCD. You can take a look at the kernel log, if any case how do you configure the video mode.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 27 Oct 2015 16:23:05 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/imx6qsabresd-hardware-gpu-acceleration/m-p/401708#M59355</guid>
      <dc:creator>Bio_TICFSL</dc:creator>
      <dc:date>2015-10-27T16:23:05Z</dc:date>
    </item>
  </channel>
</rss>

