Trying to build LTIB Linux kernel with GPU disabled / HDMI enabled on imx6 platform

[dandriscoll]

We are doing some work / integration in an AMP environment on the imx6 sabre lite board where we want one Linux kernel instance running on 1 core of the imx6q SoC configured with LVDS/Touchpanel support and GPU/hardware acceleration and another Linux kernel instance running on a different core that uses HDMI for a display and does NOT have the GPU enabled.

Basically just looking for some device / resource partitioning advice on how to build our 2 kernel images - we seem to have the kernel image with the LVDS/Touchpanel/GPU configured and working appropriately, but we are having issues building and running with the HDMI/no GPU configuration.

We are using LTIB L3.0.35_1.1.0_121218.

Any help is appreciated.

[dandriscoll · Accepted solution]

Looks like we have solved this problem internally... thanks for the help

[LeonardoSandova]

naive question: why do you need two Linux kernel instances running? I believe one kernel can manage all what you want. For the displays, you can enable the correct setting on the kernel command line (two video arguments, one for LVDS and another for HDMI) and for the with/without GPU configuration I am sure there must be ways to turn on/off the GPU (not 100% sure). What is the user-space application you are trying to run? BTW, there is a newer BSP/LTIB version on Freescale site.

Leo

[patmurray]

Hi ,

could you post a link to the LTIB BSP that you mentioned was on the Freescale site.

regards

Pat

[LeonardoSandova]

Link: i.MX6Q Product Summary Page Look for L3.0.35_4.0.0 tarballs.

Leo

[dandriscoll]

This is really for demonstration purposes related to using a hypervisor... we realize a single kernel with all the functionality enabled could do this same work, but we want to show a supervised AMP environment working to solve a semi-realistic problem.

The user-space application we are trying to run is Mentor's proprietary UI package called Inflexion.  An Inflexion based application will run on each Linux instance and support 2 different UIs for the demo - one is a 3D UI that requires hardware acceleration via OpenGL/ES (LVDS with GPU support) while the other UI is 2D and requires no acceleration (HDMI).

As for the newer version of LTIB, thanks for the heads up... since this is for a demo, we aren't totally concerned about using the latest and greatest support available, but if it does address a specific problem we are having, we will consider moving to the newer version.

Forgot to mention, configuring the display support via command-line settings seems to be fairly straight-forward, our development team working on this seems to be having problems disabling the GPU as it doesn't seem quite as well documented or straight-forward.