Building qt5 using Yocto+meta-ti possible for Beaglebone?

Building qt5 using Yocto+meta-ti possible for Beaglebone?

[Ulf Samuelsson]

Anyone succeded with this?

Which version of Yocto (dora/daisy?)

Which kernel

Any extra patches needed?

Any image recipe which can be shared?

BR
Ulf Samuelsson

Re: Building qt5 using Yocto+meta-ti possible for Beaglebone?

[Denys Dmytriyenko]

On June 6, 2014 5:58:21 PM EDT, Ulf Samuelsson <meta-ti@emagii.com> wrote:
>
>Anyone succeded with this?
>
>Which version of Yocto (dora/daisy?)
>
>Which kernel
>
>Any extra patches needed?
>
>Any image recipe which can be shared?
>
>BR
>Ulf Samuelsson

I have the necessary recipes and images in meta-arago. And you'd obviously need meta-qt5. Do you need any specific features out of it?

-- 
Denys

Re: Building qt5 using Yocto+meta-ti possible for Beaglebone?

[Ulf Samuelsson]

2014-06-07 00:38, Denys Dmytriyenko skrev:
> On June 6, 2014 5:58:21 PM EDT, Ulf Samuelsson <meta-ti@emagii.com> wrote:
>> Anyone succeded with this?
>>
>> Which version of Yocto (dora/daisy?)
>>
>> Which kernel
>>
>> Any extra patches needed?
>>
>> Any image recipe which can be shared?
>>
>> BR
>> Ulf Samuelsson
> I have the necessary recipes and images in meta-arago. And you'd obviously need meta-qt5. Do you need any specific features out of it?
>
Could you send me your

* local.conf
* bblayers.conf

  for building qt5?

BR
Ulf

Re: Building qt5 using Yocto+meta-ti possible for Beaglebone?

[Ulf Samuelsson]

2014-06-07 09:24, Ulf Samuelsson skrev:
>
> 2014-06-07 00:38, Denys Dmytriyenko skrev:
>> On June 6, 2014 5:58:21 PM EDT, Ulf Samuelsson <meta-ti@emagii.com> 
>> wrote:
>>> Anyone succeded with this?
>>>
>>> Which version of Yocto (dora/daisy?)
>>>
>>> Which kernel
>>>
>>> Any extra patches needed?
>>>
>>> Any image recipe which can be shared?
>>>
>>> BR
>>> Ulf Samuelsson
>> I have the necessary recipes and images in meta-arago. And you'd 
>> obviously need meta-qt5. Do you need any specific features out of it?
>>
> Could you send me your
>
> * local.conf
> * bblayers.conf
>
>  for building qt5?
>
Have managed to build meta-arago/meta-ti/meta-qt5,
and I am now running a Beaglebone Black with a 4Dsystems 4.3" LCD.

This is all black.

Created my own image, based on arago-qt5-test-image

This does not add libgles-omap3, which seems to be needed.

Also built the qtbase-examples.

The resulting filesystem did not find the modules, but after depmod -a,
this is OK.


root@beaglebone:/usr/share/qt5/examples/widgets/widgets/calculator# lsmod
Module                  Size  Used by
bufferclass_ti          5405  0
omaplfb                11414  0
pvrsrvkm              175499  2 bufferclass_ti,omaplfb

  and I can run several Qt applications, but:

Screen is all black.

I did not change any










> BR
> Ulf
>
>

Re: Building qt5 using Yocto+meta-ti possible for Beaglebone?

[Ulf Samuelsson]

2014-06-07 09:24, Ulf Samuelsson skrev:
>
> 2014-06-07 00:38, Denys Dmytriyenko skrev:
>> On June 6, 2014 5:58:21 PM EDT, Ulf Samuelsson <meta-ti@emagii.com> 
>> wrote:
>>> Anyone succeded with this?
>>>
>>> Which version of Yocto (dora/daisy?)
>>>
>>> Which kernel
>>>
>>> Any extra patches needed?
>>>
>>> Any image recipe which can be shared?
>>>
>>> BR
>>> Ulf Samuelsson
>> I have the necessary recipes and images in meta-arago. And you'd 
>> obviously need meta-qt5. Do you need any specific features out of it?
>>
> Could you send me your
>
> * local.conf
> * bblayers.conf
>
>  for building qt5?
>
> BR
> Ulf
>
>
Have managed to build meta-arago/meta-ti/meta-qt5,

Build Configuration:
BB_VERSION        = "1.20.0"
BUILD_SYS         = "x86_64-linux"
NATIVELSBSTRING   = "Ubuntu-12.04"
TARGET_SYS        = "arm-oe-linux-gnueabi"
MACHINE           = "beaglebone"
DISTRO            = "arago"
DISTRO_VERSION    = "2014.05"
TUNE_FEATURES     = "armv7a vfp thumb neon callconvention-hard cortexa8"
TARGET_FPU        = "vfp-neon"
meta-bugfix       = "master:d61c6e5c9074383ae90ec8ae4b9724f3ea82f5e6"
meta-arago-distro
meta-arago-extras = "master:6a6e742536ed367dc0565d665bc1ea49a2074adc"
meta-qt5          = "dora:5b5616b63bdf163ea3eb2ca8857c56a393435fe3"
toolchain-layer
meta-networking
meta-ruby
meta-oe           = "dora:ee173678383683e972c7d4d6f0ef5790bfa50274"
meta-ti           = "dora:72def59ce0da8f20638086e9fe6c9f9f4c9dd6f4"
meta-linaro-toolchain = "dora:503b1fe68f90a8e2b43c456ddd17a0a90816cf9c"
meta              = "dora:68da848e0f7f026bf18707d8d59143177ff66f9b"

NOTE: Preparing runqueue
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
NOTE: Tasks Summary: Attempted 3564 tasks of which 3561 didn't need to 
be rerun and all succeeded.
-------------------------------------------------------------------------------------------------------------------------------------------

I am now running a Beaglebone Black with a 4Dsystems 4.3" LCD.

The LCD  is all black.

Created my own image, based on arago-qt5-test-image

This does not add libgles-omap3, which seems to be needed.

Also built the qtbase-examples.

The resulting filesystem did not find the modules, but after depmod -a, 
this is OK.

root@beaglebone:/usr/share/qt5/examples/widgets/widgets/calculator# lsmod
Module                  Size  Used by
bufferclass_ti          5405  0
omaplfb                11414  0
pvrsrvkm              175499  2 bufferclass_ti,omaplfb

I can run several Qt applications, but: Screen is all black.

I do not get a splash screen,  and I did not change any device-tree files,
so I assume this is the problem.

Anyone has a working device tree file for this?

Romber Nelson and some other people mention that the 3.12 kernel used is 
not compatible with the advanced capes like LCDs.
Do I need to revert to the 3.8 kernel?

Re: Building qt5 using Yocto+meta-ti possible for Beaglebone?

[Diego Sueiro]

[-- Attachment #1: Type: text/plain, Size: 617 bytes --]

Ulf,

On Sun, Jun 8, 2014 at 9:24 PM, Ulf Samuelsson <meta-ti@emagii.com> wrote:

> Romber Nelson and some other people mention that the 3.12 kernel used is
> not compatible with the advanced capes like LCDs.
> Do I need to revert to the 3.8 kernel?
>

Kernel 3.12 does not have cape manager capabilities, as far as I know.
Did you tested it in a HDMI monitor/TV?


Regrads,

--
*dS
Diego Sueiro

Administrador do Embarcados
www.embarcados.com.br
<http://www.embarcados.com.br/?utm_source=assinatura_diego&utm_medium=e-mail&utm_campaign=Assinatura%20Email%20Diego>

/*long live rock 'n roll*/

[-- Attachment #2: Type: text/html, Size: 1189 bytes --]

Re: Building qt5 using Yocto+meta-ti possible for Beaglebone?

[Denys Dmytriyenko]

On Mon, Jun 09, 2014 at 07:04:17AM -0300, Diego Sueiro wrote:
> Ulf,
> 
> On Sun, Jun 8, 2014 at 9:24 PM, Ulf Samuelsson <meta-ti@emagii.com> wrote:
> 
> > Romber Nelson and some other people mention that the 3.12 kernel used is
> > not compatible with the advanced capes like LCDs.
> > Do I need to revert to the 3.8 kernel?
> >
> 
> Kernel 3.12 does not have cape manager capabilities, as far as I know.
> Did you tested it in a HDMI monitor/TV?

Correct, cape support is not available in 3.12.

-- 
Denys

Re: Building qt5 using Yocto+meta-ti possible for Beaglebone?

[Cooper Jr., Franklin]

> -----Original Message-----
> From: meta-ti-bounces@yoctoproject.org [mailto:meta-ti-
> bounces@yoctoproject.org] On Behalf Of Dmytriyenko, Denys
> Sent: Monday, June 09, 2014 12:35 PM
> To: Diego Sueiro
> Cc: meta-ti mailing list
> Subject: Re: [meta-ti] Building qt5 using Yocto+meta-ti possible for
> Beaglebone?
> 
> On Mon, Jun 09, 2014 at 07:04:17AM -0300, Diego Sueiro wrote:
> > Ulf,
> >
> > On Sun, Jun 8, 2014 at 9:24 PM, Ulf Samuelsson <meta-ti@emagii.com>
> wrote:
> >
> > > Romber Nelson and some other people mention that the 3.12 kernel
> > > used is not compatible with the advanced capes like LCDs.
> > > Do I need to revert to the 3.8 kernel?
> > >
> >
> > Kernel 3.12 does not have cape manager capabilities, as far as I know.
> > Did you tested it in a HDMI monitor/TV?
> 
> Correct, cape support is not available in 3.12.
[Franklin] I don't believe any >3.2 kernel within meta-ti includes support for capes. I believe linux-ti33x-psp_3.2.bb included cape support since I think it was used in Angstrom but I never used it before so I could be wrong.
> 
> --
> Denys
> --
> _______________________________________________
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti

Re: Building qt5 using Yocto+meta-ti possible for Beaglebone?

[Ulf Samuelsson]

[-- Attachment #1: Type: text/plain, Size: 4144 bytes --]


2014-06-09 12:04, Diego Sueiro skrev:
> Ulf,
>
> On Sun, Jun 8, 2014 at 9:24 PM, Ulf Samuelsson <meta-ti@emagii.com 
> <mailto:meta-ti@emagii.com>> wrote:
>
>     Romber Nelson and some other people mention that the 3.12 kernel
>     used is not compatible with the advanced capes like LCDs.
>     Do I need to revert to the 3.8 kernel?
>
>
> Kernel 3.12 does not have cape manager capabilities, as far as I know.
> Did you tested it in a HDMI monitor/TV?
>
>
I have a 4,3" LCD display and HDMI connected.

"Romber Nelson" = Robert C Nelson.

I replaced the  meta-ti kernel with his patched 3.8.13 kernel.
If I understand this correctly, this has backported the Graphics 
acceleration.

Made sure that kernel-modules and libgles-omap3 are included in the build.
Also made sure that qtbase-5.1.1 is built with qtbaseexamples for testing.

I also enabled the LCD in the bootargs.

Now I get a splash screen and I can run the qt examples,
but only if I supply the linux frame buffer

"$ calculator"   fails, due not no X-windowa

Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, 
offscreen.

"$ calculator -platform linuxfb" works, but is of course not accelerated.

"$ calculator -platform eglfs" fails.

Could not initialize egl display
EGL error
Aborted

I assume that this is either a faulty kernel, or lack of libraries.

My libraires related to EGL are:

root@beaglebone:/usr/lib# ls | grep EGL
libEGL.so
libEGL.so.1
libEGL.so.1.10
libEGL.so.1.10.2359475
libEGL_eglimage.so
libEGL_eglimage.so.1
libEGL_eglimage.so.1.10
libEGL_eglimage.so.1.10.2359475
libpvrPVR2D_BLITWSEGL.so
libpvrPVR2D_BLITWSEGL.so.1
libpvrPVR2D_BLITWSEGL.so.1.10
libpvrPVR2D_BLITWSEGL.so.1.10.2359475
libpvrPVR2D_FLIPWSEGL.so
libpvrPVR2D_FLIPWSEGL.so.1
libpvrPVR2D_FLIPWSEGL.so.1.10
libpvrPVR2D_FLIPWSEGL.so.1.10.2359475
libpvrPVR2D_FRONTWSEGL.so
libpvrPVR2D_FRONTWSEGL.so.1
libpvrPVR2D_FRONTWSEGL.so.1.10
libpvrPVR2D_FRONTWSEGL.so.1.10.2359475
libpvrPVR2D_LINUXFBWSEGL.so
libpvrPVR2D_LINUXFBWSEGL.so.1
libpvrPVR2D_LINUXFBWSEGL.so.1.10
libpvrPVR2D_LINUXFBWSEGL.so.1.10.2359475

Any other library, I should be looking for?

-----------------------------------------------------------------------

The kernel options have set
CONFIG_DRM_TILCDC=y
CONFIG_DRM is not set
CONFIG_FIRMWARE_EDID=y
CONFIG_FB_MODE_HELPERS=y
CONFIG_FB_TILEBLITTING=y
CONFIG_FB_DA8XX=y
CONFIG_FB_ST7735=y
FB_BOTH_ENDIAN=y

CONFIG_OMAP2_DSS_DPI=y
CONFIG_OMAP2_DSS_RFBI=y
CONFIG_OMAP2_DSS_VENC=y
CONFIG_OMAP4_DSS_HDMI=y
CONFIG_OMAP2_DSS_SDI=y
CONFIG_OMAP2_DSS_DSL=y

CONFIG_FB_OMAP2_DEBUG_SUPPORT=y


CONFIG_FB_OMAP2_NUM_FBS=3

CONFIG_PANEL_GENERIC_DPI=m
CONFIG_PANEL_SHARP_LS037V7DW01=m
CONFIG_PANEL_NEC_NL8048HL11_01B=m

CONFIG_PANEL_TAAL=y
CONFIG_PANEL_TPO_TD043MTEA1=y
CONFIG_PANEL_ACX565AKM=y
CONFIG_LCD_ILI9320=y


CONFIG_LCD_PLATFORM=y
CONFIG_FRAMEBUFFER_CONSOLE=y
CONFIG_FONTS=y
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=y
FONT_MINI_4x6=y
LOGO_LINUX_MONO=y
LOGO_LINUX_VGA16=y
LOGO_LINUX_CLUT224=y

Checked the 3.12 meta-ti kernel and it does not seem to have a lot of 
extra config options.

Should I focus on the kernel or the libraries to get an EGL display?
---------------------------------------------------------------------

BTW: What is the reason that there is no cape support

1.It is considered a bad idea, and rejected?
2.Beaglebone specific, and thus of no interest to anyone with real money?
3.Noone bothered to submit to mainstream?
4.There is another API in the works, which will allow similar functionality.
5.Other reason?

Seems that every system on a chip with programmable I/O would need 
something similar.

Is there any other easy way to get the LCD running.
Customized device-tree fille?

Any such file available off the shelf?


BR
Ulf Samuelsson

> Regrads,
>
> --
> *dS
> Diego Sueiro
>
> Administrador do Embarcados
> www.embarcados.com.br 
> <http://www.embarcados.com.br/?utm_source=assinatura_diego&utm_medium=e-mail&utm_campaign=Assinatura%20Email%20Diego>
>
> /*long live rock 'n roll*/


[-- Attachment #2: Type: text/html, Size: 6888 bytes --]

Re: Building qt5 using Yocto+meta-ti possible for Beaglebone?

[Robert Nelson]

>
> The kernel options have set
> CONFIG_DRM_TILCDC=y
> CONFIG_DRM is not set
> CONFIG_FIRMWARE_EDID=y
> CONFIG_FB_MODE_HELPERS=y
> CONFIG_FB_TILEBLITTING=y
> CONFIG_FB_DA8XX=y
> CONFIG_FB_ST7735=y
> FB_BOTH_ENDIAN=y
>
> CONFIG_OMAP2_DSS_DPI=y
> CONFIG_OMAP2_DSS_RFBI=y
> CONFIG_OMAP2_DSS_VENC=y
> CONFIG_OMAP4_DSS_HDMI=y
> CONFIG_OMAP2_DSS_SDI=y
> CONFIG_OMAP2_DSS_DSL=y
>
> CONFIG_FB_OMAP2_DEBUG_SUPPORT=y
>
>
> CONFIG_FB_OMAP2_NUM_FBS=3

If this is just for the beaglebone you can drop these OMAP*_DSS configs..

>
> CONFIG_PANEL_GENERIC_DPI=m
> CONFIG_PANEL_SHARP_LS037V7DW01=m
> CONFIG_PANEL_NEC_NL8048HL11_01B=m
>
> CONFIG_PANEL_TAAL=y
> CONFIG_PANEL_TPO_TD043MTEA1=y
> CONFIG_PANEL_ACX565AKM=y
> CONFIG_LCD_ILI9320=y
>
>
> CONFIG_LCD_PLATFORM=y
> CONFIG_FRAMEBUFFER_CONSOLE=y
> CONFIG_FONTS=y
> CONFIG_FONT_8x8=y
> CONFIG_FONT_8x16=y
> FONT_MINI_4x6=y
> LOGO_LINUX_MONO=y
> LOGO_LINUX_VGA16=y
> LOGO_LINUX_CLUT224=y
>
> Checked the 3.12 meta-ti kernel and it does not seem to have a lot of extra
> config options.
>
> Should I focus on the kernel or the libraries to get an EGL display?
>
> ---------------------------------------------------------------------
>
> BTW: What is the reason that there is no cape support
>
> 1.It is considered a bad idea, and rejected?
> 2.Beaglebone specific, and thus of no interest to anyone with real money?
> 3.Noone bothered to submit to mainstream?

Patch series 1 (overlays) is stuck in never-ending "review", here is
the latest submission:

https://lkml.org/lkml/2014/5/28/280

> 4.There is another API in the works, which will allow similar functionality.
> 5.Other reason?

Regards,

-- 
Robert Nelson
http://www.rcn-ee.com/

Re: Building qt5 using Yocto+meta-ti possible for Beaglebone?

[Denys Dmytriyenko]

On Tue, Jun 10, 2014 at 12:54:10AM +0200, Ulf Samuelsson wrote:
> 
> 2014-06-09 12:04, Diego Sueiro skrev:
> >Ulf,
> >
> >On Sun, Jun 8, 2014 at 9:24 PM, Ulf Samuelsson <meta-ti@emagii.com
> ><mailto:meta-ti@emagii.com>> wrote:
> >
> >    Romber Nelson and some other people mention that the 3.12 kernel
> >    used is not compatible with the advanced capes like LCDs.
> >    Do I need to revert to the 3.8 kernel?
> >
> >
> >Kernel 3.12 does not have cape manager capabilities, as far as I know.
> >Did you tested it in a HDMI monitor/TV?
> >
> >
> I have a 4,3" LCD display and HDMI connected.
> 
> "Romber Nelson" = Robert C Nelson.
> 
> I replaced the  meta-ti kernel with his patched 3.8.13 kernel.
> If I understand this correctly, this has backported the Graphics
> acceleration.
> 
> Made sure that kernel-modules and libgles-omap3 are included in the build.
> Also made sure that qtbase-5.1.1 is built with qtbaseexamples for testing.
> 
> I also enabled the LCD in the bootargs.
> 
> Now I get a splash screen and I can run the qt examples,
> but only if I supply the linux frame buffer
> 
> "$ calculator"   fails, due not no X-windowa
> 
> Available platform plugins are: eglfs, linuxfb, minimal, minimalegl,
> offscreen.
> 
> "$ calculator -platform linuxfb" works, but is of course not accelerated.
> 
> "$ calculator -platform eglfs" fails.
> 
> Could not initialize egl display
> EGL error
> Aborted

IIRC, there were some additional patches for libgles-omap3 and Qt5 in 
meta-arago... I don't remember the version of Qt5 when I played with it and 
got it working - it was either 5.1.1 or 5.2...


> I assume that this is either a faulty kernel, or lack of libraries.
> 
> My libraires related to EGL are:
> 
> root@beaglebone:/usr/lib# ls | grep EGL
> libEGL.so
> libEGL.so.1
> libEGL.so.1.10
> libEGL.so.1.10.2359475
> libEGL_eglimage.so
> libEGL_eglimage.so.1
> libEGL_eglimage.so.1.10
> libEGL_eglimage.so.1.10.2359475
> libpvrPVR2D_BLITWSEGL.so
> libpvrPVR2D_BLITWSEGL.so.1
> libpvrPVR2D_BLITWSEGL.so.1.10
> libpvrPVR2D_BLITWSEGL.so.1.10.2359475
> libpvrPVR2D_FLIPWSEGL.so
> libpvrPVR2D_FLIPWSEGL.so.1
> libpvrPVR2D_FLIPWSEGL.so.1.10
> libpvrPVR2D_FLIPWSEGL.so.1.10.2359475
> libpvrPVR2D_FRONTWSEGL.so
> libpvrPVR2D_FRONTWSEGL.so.1
> libpvrPVR2D_FRONTWSEGL.so.1.10
> libpvrPVR2D_FRONTWSEGL.so.1.10.2359475
> libpvrPVR2D_LINUXFBWSEGL.so
> libpvrPVR2D_LINUXFBWSEGL.so.1
> libpvrPVR2D_LINUXFBWSEGL.so.1.10
> libpvrPVR2D_LINUXFBWSEGL.so.1.10.2359475
> 
> Any other library, I should be looking for?
> 
> -----------------------------------------------------------------------
> 
> The kernel options have set
> CONFIG_DRM_TILCDC=y
> CONFIG_DRM is not set
> CONFIG_FIRMWARE_EDID=y
> CONFIG_FB_MODE_HELPERS=y
> CONFIG_FB_TILEBLITTING=y
> CONFIG_FB_DA8XX=y
> CONFIG_FB_ST7735=y
> FB_BOTH_ENDIAN=y
> 
> CONFIG_OMAP2_DSS_DPI=y
> CONFIG_OMAP2_DSS_RFBI=y
> CONFIG_OMAP2_DSS_VENC=y
> CONFIG_OMAP4_DSS_HDMI=y
> CONFIG_OMAP2_DSS_SDI=y
> CONFIG_OMAP2_DSS_DSL=y
> 
> CONFIG_FB_OMAP2_DEBUG_SUPPORT=y
> 
> 
> CONFIG_FB_OMAP2_NUM_FBS=3
> 
> CONFIG_PANEL_GENERIC_DPI=m
> CONFIG_PANEL_SHARP_LS037V7DW01=m
> CONFIG_PANEL_NEC_NL8048HL11_01B=m
> 
> CONFIG_PANEL_TAAL=y
> CONFIG_PANEL_TPO_TD043MTEA1=y
> CONFIG_PANEL_ACX565AKM=y
> CONFIG_LCD_ILI9320=y
> 
> 
> CONFIG_LCD_PLATFORM=y
> CONFIG_FRAMEBUFFER_CONSOLE=y
> CONFIG_FONTS=y
> CONFIG_FONT_8x8=y
> CONFIG_FONT_8x16=y
> FONT_MINI_4x6=y
> LOGO_LINUX_MONO=y
> LOGO_LINUX_VGA16=y
> LOGO_LINUX_CLUT224=y
> 
> Checked the 3.12 meta-ti kernel and it does not seem to have a lot
> of extra config options.
> 
> Should I focus on the kernel or the libraries to get an EGL display?
> ---------------------------------------------------------------------
> 
> BTW: What is the reason that there is no cape support
> 
> 1.It is considered a bad idea, and rejected?
> 2.Beaglebone specific, and thus of no interest to anyone with real money?
> 3.Noone bothered to submit to mainstream?
> 4.There is another API in the works, which will allow similar functionality.
> 5.Other reason?

5. Other reason - it's been in the works for some time now, but is still not 
merged upstream, as it's not trivial. You can google for capebus, capemgr and 
devtree overlays for the latest set of patches...


> Seems that every system on a chip with programmable I/O would need
> something similar.
> 
> Is there any other easy way to get the LCD running.
> Customized device-tree fille?
> 
> Any such file available off the shelf?
> 
> 
> BR
> Ulf Samuelsson
> 
> >Regrads,
> >
> >--
> >*dS
> >Diego Sueiro
> >
> >Administrador do Embarcados
> >www.embarcados.com.br <http://www.embarcados.com.br/?utm_source=assinatura_diego&utm_medium=e-mail&utm_campaign=Assinatura%20Email%20Diego>
> >
> >/*long live rock 'n roll*/
> 

> -- 
> _______________________________________________
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti

Re: Building qt5 using Yocto+meta-ti possible for Beaglebone?

[Ulf Samuelsson]

2014-06-10 02:35, Denys Dmytriyenko skrev:
> On Tue, Jun 10, 2014 at 12:54:10AM +0200, Ulf Samuelsson wrote:
>> 2014-06-09 12:04, Diego Sueiro skrev:
>>> Ulf,
>>>
>>> On Sun, Jun 8, 2014 at 9:24 PM, Ulf Samuelsson <meta-ti@emagii.com
>>> <mailto:meta-ti@emagii.com>> wrote:
>>>
>>>     Romber Nelson and some other people mention that the 3.12 kernel
>>>     used is not compatible with the advanced capes like LCDs.
>>>     Do I need to revert to the 3.8 kernel?
>>>
>>>
>>> Kernel 3.12 does not have cape manager capabilities, as far as I know.
>>> Did you tested it in a HDMI monitor/TV?
>>>
>>>
>> I have a 4,3" LCD display and HDMI connected.
>>
>> "Romber Nelson" = Robert C Nelson.
>>
>> I replaced the  meta-ti kernel with his patched 3.8.13 kernel.
>> If I understand this correctly, this has backported the Graphics
>> acceleration.
>>
>> Made sure that kernel-modules and libgles-omap3 are included in the build.
>> Also made sure that qtbase-5.1.1 is built with qtbaseexamples for testing.
>>
>> I also enabled the LCD in the bootargs.
>>
>> Now I get a splash screen and I can run the qt examples,
>> but only if I supply the linux frame buffer
>>
>> "$ calculator"   fails, due not no X-windowa
>>
>> Available platform plugins are: eglfs, linuxfb, minimal, minimalegl,
>> offscreen.
>>
>> "$ calculator -platform linuxfb" works, but is of course not accelerated.
>>
>> "$ calculator -platform eglfs" fails.
>>
>> Could not initialize egl display
>> EGL error
>> Aborted
> IIRC, there were some additional patches for libgles-omap3 and Qt5 in
> meta-arago... I don't remember the version of Qt5 when I played with it and
> got it working - it was either 5.1.1 or 5.2...
>
meta-arago (dora) has 5.1.1
master has 5.2.0

meta-qt5 uses 5.2.1



>> I assume that this is either a faulty kernel, or lack of libraries.
>>
>> My libraires related to EGL are:
>>
>> root@beaglebone:/usr/lib# ls | grep EGL
>> libEGL.so
>> libEGL.so.1
>> libEGL.so.1.10
>> libEGL.so.1.10.2359475
>> libEGL_eglimage.so
>> libEGL_eglimage.so.1
>> libEGL_eglimage.so.1.10
>> libEGL_eglimage.so.1.10.2359475
>> libpvrPVR2D_BLITWSEGL.so
>> libpvrPVR2D_BLITWSEGL.so.1
>> libpvrPVR2D_BLITWSEGL.so.1.10
>> libpvrPVR2D_BLITWSEGL.so.1.10.2359475
>> libpvrPVR2D_FLIPWSEGL.so
>> libpvrPVR2D_FLIPWSEGL.so.1
>> libpvrPVR2D_FLIPWSEGL.so.1.10
>> libpvrPVR2D_FLIPWSEGL.so.1.10.2359475
>> libpvrPVR2D_FRONTWSEGL.so
>> libpvrPVR2D_FRONTWSEGL.so.1
>> libpvrPVR2D_FRONTWSEGL.so.1.10
>> libpvrPVR2D_FRONTWSEGL.so.1.10.2359475
>> libpvrPVR2D_LINUXFBWSEGL.so
>> libpvrPVR2D_LINUXFBWSEGL.so.1
>> libpvrPVR2D_LINUXFBWSEGL.so.1.10
>> libpvrPVR2D_LINUXFBWSEGL.so.1.10.2359475
>>
>> Any other library, I should be looking for?
>>
>> -----------------------------------------------------------------------
>>
>> The kernel options have set
>> CONFIG_DRM_TILCDC=y
>> CONFIG_DRM is not set
>> CONFIG_FIRMWARE_EDID=y
>> CONFIG_FB_MODE_HELPERS=y
>> CONFIG_FB_TILEBLITTING=y
>> CONFIG_FB_DA8XX=y
>> CONFIG_FB_ST7735=y
>> FB_BOTH_ENDIAN=y
>>
>> CONFIG_OMAP2_DSS_DPI=y
>> CONFIG_OMAP2_DSS_RFBI=y
>> CONFIG_OMAP2_DSS_VENC=y
>> CONFIG_OMAP4_DSS_HDMI=y
>> CONFIG_OMAP2_DSS_SDI=y
>> CONFIG_OMAP2_DSS_DSL=y
>>
>> CONFIG_FB_OMAP2_DEBUG_SUPPORT=y
>>
>>
>> CONFIG_FB_OMAP2_NUM_FBS=3
>>
>> CONFIG_PANEL_GENERIC_DPI=m
>> CONFIG_PANEL_SHARP_LS037V7DW01=m
>> CONFIG_PANEL_NEC_NL8048HL11_01B=m
>>
>> CONFIG_PANEL_TAAL=y
>> CONFIG_PANEL_TPO_TD043MTEA1=y
>> CONFIG_PANEL_ACX565AKM=y
>> CONFIG_LCD_ILI9320=y
>>
>>
>> CONFIG_LCD_PLATFORM=y
>> CONFIG_FRAMEBUFFER_CONSOLE=y
>> CONFIG_FONTS=y
>> CONFIG_FONT_8x8=y
>> CONFIG_FONT_8x16=y
>> FONT_MINI_4x6=y
>> LOGO_LINUX_MONO=y
>> LOGO_LINUX_VGA16=y
>> LOGO_LINUX_CLUT224=y
>>
>> Checked the 3.12 meta-ti kernel and it does not seem to have a lot
>> of extra config options.
>>
>> Should I focus on the kernel or the libraries to get an EGL display?
>> ---------------------------------------------------------------------
>>
>> BTW: What is the reason that there is no cape support
>>
>> 1.It is considered a bad idea, and rejected?
>> 2.Beaglebone specific, and thus of no interest to anyone with real money?
>> 3.Noone bothered to submit to mainstream?
>> 4.There is another API in the works, which will allow similar functionality.
>> 5.Other reason?
> 5. Other reason - it's been in the works for some time now, but is still not
> merged upstream, as it's not trivial. You can google for capebus, capemgr and
> devtree overlays for the latest set of patches...
Thanks!

Wouldn't a customized device-tree work?
BR
Ulf

>
>> Seems that every system on a chip with programmable I/O would need
>> something similar.
>>
>> Is there any other easy way to get the LCD running.
>> Customized device-tree fille?
>>
>> Any such file available off the shelf?
>>
>>
>> BR
>> Ulf Samuelsson
>>
>>> Regrads,
>>>
>>> --
>>> *dS
>>> Diego Sueiro
>>>
>>> Administrador do Embarcados
>>> www.embarcados.com.br <http://www.embarcados.com.br/?utm_source=assinatura_diego&utm_medium=e-mail&utm_campaign=Assinatura%20Email%20Diego>
>>>
>>> /*long live rock 'n roll*/
>> -- 
>> _______________________________________________
>> meta-ti mailing list
>> meta-ti@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/meta-ti

Re: Building qt5 using Yocto+meta-ti possible for Beaglebone?

[Denys Dmytriyenko]

On Tue, Jun 10, 2014 at 08:36:39AM +0200, Ulf Samuelsson wrote:
> 
> 2014-06-10 02:35, Denys Dmytriyenko skrev:
> >On Tue, Jun 10, 2014 at 12:54:10AM +0200, Ulf Samuelsson wrote:
> >>2014-06-09 12:04, Diego Sueiro skrev:
> >>>Ulf,
> >>>
> >>>On Sun, Jun 8, 2014 at 9:24 PM, Ulf Samuelsson <meta-ti@emagii.com
> >>><mailto:meta-ti@emagii.com>> wrote:
> >>>
> >>>    Romber Nelson and some other people mention that the 3.12 kernel
> >>>    used is not compatible with the advanced capes like LCDs.
> >>>    Do I need to revert to the 3.8 kernel?
> >>>
> >>>
> >>>Kernel 3.12 does not have cape manager capabilities, as far as I know.
> >>>Did you tested it in a HDMI monitor/TV?
> >>>
> >>>
> >>I have a 4,3" LCD display and HDMI connected.
> >>
> >>"Romber Nelson" = Robert C Nelson.
> >>
> >>I replaced the  meta-ti kernel with his patched 3.8.13 kernel.
> >>If I understand this correctly, this has backported the Graphics
> >>acceleration.
> >>
> >>Made sure that kernel-modules and libgles-omap3 are included in the build.
> >>Also made sure that qtbase-5.1.1 is built with qtbaseexamples for testing.
> >>
> >>I also enabled the LCD in the bootargs.
> >>
> >>Now I get a splash screen and I can run the qt examples,
> >>but only if I supply the linux frame buffer
> >>
> >>"$ calculator"   fails, due not no X-windowa
> >>
> >>Available platform plugins are: eglfs, linuxfb, minimal, minimalegl,
> >>offscreen.
> >>
> >>"$ calculator -platform linuxfb" works, but is of course not accelerated.
> >>
> >>"$ calculator -platform eglfs" fails.
> >>
> >>Could not initialize egl display
> >>EGL error
> >>Aborted
> >IIRC, there were some additional patches for libgles-omap3 and Qt5 in
> >meta-arago... I don't remember the version of Qt5 when I played with it and
> >got it working - it was either 5.1.1 or 5.2...
> >
> meta-arago (dora) has 5.1.1
> master has 5.2.0
> 
> meta-qt5 uses 5.2.1

Can you please try the patches from meta-arago with qt 5.1.1?


> >>I assume that this is either a faulty kernel, or lack of libraries.
> >>
> >>My libraires related to EGL are:
> >>
> >>root@beaglebone:/usr/lib# ls | grep EGL
> >>libEGL.so
> >>libEGL.so.1
> >>libEGL.so.1.10
> >>libEGL.so.1.10.2359475
> >>libEGL_eglimage.so
> >>libEGL_eglimage.so.1
> >>libEGL_eglimage.so.1.10
> >>libEGL_eglimage.so.1.10.2359475
> >>libpvrPVR2D_BLITWSEGL.so
> >>libpvrPVR2D_BLITWSEGL.so.1
> >>libpvrPVR2D_BLITWSEGL.so.1.10
> >>libpvrPVR2D_BLITWSEGL.so.1.10.2359475
> >>libpvrPVR2D_FLIPWSEGL.so
> >>libpvrPVR2D_FLIPWSEGL.so.1
> >>libpvrPVR2D_FLIPWSEGL.so.1.10
> >>libpvrPVR2D_FLIPWSEGL.so.1.10.2359475
> >>libpvrPVR2D_FRONTWSEGL.so
> >>libpvrPVR2D_FRONTWSEGL.so.1
> >>libpvrPVR2D_FRONTWSEGL.so.1.10
> >>libpvrPVR2D_FRONTWSEGL.so.1.10.2359475
> >>libpvrPVR2D_LINUXFBWSEGL.so
> >>libpvrPVR2D_LINUXFBWSEGL.so.1
> >>libpvrPVR2D_LINUXFBWSEGL.so.1.10
> >>libpvrPVR2D_LINUXFBWSEGL.so.1.10.2359475
> >>
> >>Any other library, I should be looking for?
> >>
> >>-----------------------------------------------------------------------
> >>
> >>The kernel options have set
> >>CONFIG_DRM_TILCDC=y
> >>CONFIG_DRM is not set
> >>CONFIG_FIRMWARE_EDID=y
> >>CONFIG_FB_MODE_HELPERS=y
> >>CONFIG_FB_TILEBLITTING=y
> >>CONFIG_FB_DA8XX=y
> >>CONFIG_FB_ST7735=y
> >>FB_BOTH_ENDIAN=y
> >>
> >>CONFIG_OMAP2_DSS_DPI=y
> >>CONFIG_OMAP2_DSS_RFBI=y
> >>CONFIG_OMAP2_DSS_VENC=y
> >>CONFIG_OMAP4_DSS_HDMI=y
> >>CONFIG_OMAP2_DSS_SDI=y
> >>CONFIG_OMAP2_DSS_DSL=y
> >>
> >>CONFIG_FB_OMAP2_DEBUG_SUPPORT=y
> >>
> >>
> >>CONFIG_FB_OMAP2_NUM_FBS=3
> >>
> >>CONFIG_PANEL_GENERIC_DPI=m
> >>CONFIG_PANEL_SHARP_LS037V7DW01=m
> >>CONFIG_PANEL_NEC_NL8048HL11_01B=m
> >>
> >>CONFIG_PANEL_TAAL=y
> >>CONFIG_PANEL_TPO_TD043MTEA1=y
> >>CONFIG_PANEL_ACX565AKM=y
> >>CONFIG_LCD_ILI9320=y
> >>
> >>
> >>CONFIG_LCD_PLATFORM=y
> >>CONFIG_FRAMEBUFFER_CONSOLE=y
> >>CONFIG_FONTS=y
> >>CONFIG_FONT_8x8=y
> >>CONFIG_FONT_8x16=y
> >>FONT_MINI_4x6=y
> >>LOGO_LINUX_MONO=y
> >>LOGO_LINUX_VGA16=y
> >>LOGO_LINUX_CLUT224=y
> >>
> >>Checked the 3.12 meta-ti kernel and it does not seem to have a lot
> >>of extra config options.
> >>
> >>Should I focus on the kernel or the libraries to get an EGL display?
> >>---------------------------------------------------------------------
> >>
> >>BTW: What is the reason that there is no cape support
> >>
> >>1.It is considered a bad idea, and rejected?
> >>2.Beaglebone specific, and thus of no interest to anyone with real money?
> >>3.Noone bothered to submit to mainstream?
> >>4.There is another API in the works, which will allow similar functionality.
> >>5.Other reason?
> >5. Other reason - it's been in the works for some time now, but is still not
> >merged upstream, as it's not trivial. You can google for capebus, capemgr and
> >devtree overlays for the latest set of patches...
> Thanks!
> 
> Wouldn't a customized device-tree work?
> BR
> Ulf
> 
> >
> >>Seems that every system on a chip with programmable I/O would need
> >>something similar.
> >>
> >>Is there any other easy way to get the LCD running.
> >>Customized device-tree fille?
> >>
> >>Any such file available off the shelf?
> >>
> >>
> >>BR
> >>Ulf Samuelsson
> >>
> >>>Regrads,
> >>>
> >>>--
> >>>*dS
> >>>Diego Sueiro
> >>>
> >>>Administrador do Embarcados
> >>>www.embarcados.com.br <http://www.embarcados.com.br/?utm_source=assinatura_diego&utm_medium=e-mail&utm_campaign=Assinatura%20Email%20Diego>
> >>>
> >>>/*long live rock 'n roll*/
> >>-- 
> >>_______________________________________________
> >>meta-ti mailing list
> >>meta-ti@yoctoproject.org
> >>https://lists.yoctoproject.org/listinfo/meta-ti
> 

Building qt5 using Yocto+meta-ti possible for Beaglebone?

[DUMAZ Aymeric]

Sorry if this message doesn't add to the original thread, I just suscribbed to the ML.

> 2014-06-10 02:35, Denys Dmytriyenko skrev:
>> On Tue, Jun 10, 2014 at 12:54:10AM +0200, Ulf Samuelsson wrote:
>>> 2014-06-09 12:04, Diego Sueiro skrev:
>>> I have a 4,3" LCD display and HDMI connected.
>>>
>>> "Romber Nelson" = Robert C Nelson.
>>>
>>> I replaced the  meta-ti kernel with his patched 3.8.13 kernel.
>>> If I understand this correctly, this has backported the Graphics
>>> acceleration.
>>>
>>> Made sure that kernel-modules and libgles-omap3 are included in the build.
>>> Also made sure that qtbase-5.1.1 is built with qtbaseexamples for testing.
>>>
>>> I also enabled the LCD in the bootargs.
>>>
>>> Now I get a splash screen and I can run the qt examples,
>>> but only if I supply the linux frame buffer
>>>
>>> "$ calculator"   fails, due not no X-windowa
>>>
>>> Available platform plugins are: eglfs, linuxfb, minimal, minimalegl,
>>> offscreen.
>>>
>>> "$ calculator -platform linuxfb" works, but is of course not accelerated.
>>>
>>> "$ calculator -platform eglfs" fails.
>>>
>>> Could not initialize egl display
>>> EGL error
>>> Aborted
>> IIRC, there were some additional patches for libgles-omap3 and Qt5 in
>> meta-arago... I don't remember the version of Qt5 when I played with it and
>> got it working - it was either 5.1.1 or 5.2...
>
> meta-arago (dora) has 5.1.1
> master has 5.2.0
>
> meta-qt5 uses 5.2.1

I'm using an AM335x-evmsk and I get the same errors about EGL.
I just checked the patches on the master branch of meta-arago; turns out
it's not for 5.2.0!
In fact, you can find the same patches inside the "qt5_1_1_Sep13" folder
here: https://github.com/prabindh/qt-configs
I tried to see if I could adapt them but the source changed too much between
5.1 and 5.2.