fsl framebuffer image ?

fsl framebuffer image ?

[David Hill]

Hi,
    I am interested in using imx6 in accelerated framebuffer mode. Currently I have a running fsl-image-gui, but that does not have the two accelerated framebuffer versions of libEGL.so & libGAL.so installed (at least that I could find.

I have heard that there is a fsl-image-fb in the works. Is that likely to be mainlined anytime soon ?

Any other suggestions on how to obtain the two shared libs ?

thanks!

-- 
David Hill <David.Hill@Oracle.com>
Java Embedded Development

"To err is human... to really foul up requires the root password."

Re: fsl framebuffer image ?

[Otavio Salvador]

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

Hello David,

On Tue, Jan 14, 2014 at 6:22 PM, David Hill <David.Hill@oracle.com> wrote:

>    I am interested in using imx6 in accelerated framebuffer mode.
> Currently I have a running fsl-image-gui, but that does not have the two
> accelerated framebuffer versions of libEGL.so & libGAL.so installed (at
> least that I could find.
>
> I have heard that there is a fsl-image-fb in the works. Is that likely to
> be mainlined anytime soon ?
>
> Any other suggestions on how to obtain the two shared libs ?
>

Adding:

DISTRO_FEATURES_remove = "x11 wayland"

to your local.conf should do the trick. If you want directfb, use:

DISTRO_FEATURES += "directfb"

I hope it works for you.

-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750

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

Re: fsl framebuffer image ?

[Lauren Post]

You can use the one in our meta-fsl-bsp-release layer.  There is one being reviewed based on the one Freescale released in the meta-fsl-bsp-release layer.  Our current 3.10.17-1.0.0 beta has support for all the graphical backends including the related image recipes for each backend.

Get meta-fsl-release-layer from git.freescale.com.

Lauren

-----Original Message-----
From: meta-freescale-bounces@yoctoproject.org [mailto:meta-freescale-bounces@yoctoproject.org] On Behalf Of David Hill
Sent: Tuesday, January 14, 2014 2:23 PM
To: meta-freescale Mailing List
Subject: [meta-freescale] fsl framebuffer image ?



Hi,
    I am interested in using imx6 in accelerated framebuffer mode. Currently I have a running fsl-image-gui, but that does not have the two accelerated framebuffer versions of libEGL.so & libGAL.so installed (at least that I could find.

I have heard that there is a fsl-image-fb in the works. Is that likely to be mainlined anytime soon ?

Any other suggestions on how to obtain the two shared libs ?

thanks!

-- 
David Hill <David.Hill@Oracle.com>
Java Embedded Development

"To err is human... to really foul up requires the root password."

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

Re: fsl framebuffer image ?

[David Hill]

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

On 1/14/14, Jan 14, 8:39 PM, Otavio Salvador wrote:
> Hello David,
>
> On Tue, Jan 14, 2014 at 6:22 PM, David Hill <David.Hill@oracle.com <mailto:David.Hill@oracle.com>> wrote:
>
>      I am interested in using imx6 in accelerated framebuffer mode. Currently I have a running fsl-image-gui, but that does not have the two accelerated framebuffer versions of libEGL.so & libGAL.so installed (at least that I could find.
>
>     I have heard that there is a fsl-image-fb in the works. Is that likely to be mainlined anytime soon ?
>
>     Any other suggestions on how to obtain the two shared libs ?
>
>
> Adding:
>
> DISTRO_FEATURES_remove = "x11 wayland"
>
> to your local.conf should do the trick. If you want directfb, use:
>
> DISTRO_FEATURES += "directfb"
>
> I hope it works for you.

Otavio,
   Not quite...
$ bitbake $ bitbake fsl-image-gui

ERROR: Nothing PROVIDES 'virtual/libx11' (but /home/ddhill/yocto/sources/poky/meta/recipes-qt/qt4/qt4-x11-free_4.8.5.bb DEPENDS on or otherwise requires it)
ERROR: nativesdk-libx11 PROVIDES virtual/libx11 but was skipped: 'x11' not in DISTRO_FEATURES
ERROR: libx11 PROVIDES virtual/libx11 but was skipped: 'x11' not in DISTRO_FEATURES
ERROR: libx11-diet PROVIDES virtual/libx11 but was skipped: 'x11' not in DISTRO_FEATURES
NOTE: Runtime target 'qt4-plugin-phonon-backend-gstreamer' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['qt4-plugin-phonon-backend-gstreamer', 'virtual/libx11']
ERROR: Required build target 'fsl-image-gui' has no buildable providers.
Missing or unbuildable dependency chain was: ['fsl-image-gui', 'qt4-plugin-phonon-backend-gstreamer', 'virtual/libx11']

"fsl-image-gui" seems odd here of course, but did not know what else to use, and you did not mention another target. Looks like this is more complicated than just pulling a couple of features out.

As I am not doing a production image, I would be happy just adding the to fb libraries to an X11 image. Guess I will have to try Lauren stuff next (again as I could not get it to build last year).

Dave


>
> -- 
> Otavio Salvador                             O.S. Systems
> http://www.ossystems.com.br http://code.ossystems.com.br
> Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750


-- 
David Hill <David.Hill@Oracle.com>
Java Embedded Development

"The problm with computers is they do what you tell them."


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

Re: fsl framebuffer image ?

[Gary Thomas]

On 2014-01-15 09:08, David Hill wrote:
> On 1/14/14, Jan 14, 8:39 PM, Otavio Salvador wrote:
>> Hello David,
>>
>> On Tue, Jan 14, 2014 at 6:22 PM, David Hill <David.Hill@oracle.com <mailto:David.Hill@oracle.com>> wrote:
>>
>>      I am interested in using imx6 in accelerated framebuffer mode. Currently I have a running fsl-image-gui, but that does not have the two accelerated framebuffer versions of
>>     libEGL.so & libGAL.so installed (at least that I could find.
>>
>>     I have heard that there is a fsl-image-fb in the works. Is that likely to be mainlined anytime soon ?
>>
>>     Any other suggestions on how to obtain the two shared libs ?
>>
>>
>> Adding:
>>
>> DISTRO_FEATURES_remove = "x11 wayland"
>>
>> to your local.conf should do the trick. If you want directfb, use:
>>
>> DISTRO_FEATURES += "directfb"
>>
>> I hope it works for you.
>
> Otavio,
>    Not quite...
> $ bitbake $ bitbake fsl-image-gui
>
> ERROR: Nothing PROVIDES 'virtual/libx11' (but /home/ddhill/yocto/sources/poky/meta/recipes-qt/qt4/qt4-x11-free_4.8.5.bb DEPENDS on or otherwise requires it)
> ERROR: nativesdk-libx11 PROVIDES virtual/libx11 but was skipped: 'x11' not in DISTRO_FEATURES
> ERROR: libx11 PROVIDES virtual/libx11 but was skipped: 'x11' not in DISTRO_FEATURES
> ERROR: libx11-diet PROVIDES virtual/libx11 but was skipped: 'x11' not in DISTRO_FEATURES
> NOTE: Runtime target 'qt4-plugin-phonon-backend-gstreamer' is unbuildable, removing...
> Missing or unbuildable dependency chain was: ['qt4-plugin-phonon-backend-gstreamer', 'virtual/libx11']
> ERROR: Required build target 'fsl-image-gui' has no buildable providers.
> Missing or unbuildable dependency chain was: ['fsl-image-gui', 'qt4-plugin-phonon-backend-gstreamer', 'virtual/libx11']
>
> "fsl-image-gui" seems odd here of course, but did not know what else to use, and you did not mention another target. Looks like this is more complicated than just pulling a couple
> of features out.
>
> As I am not doing a production image, I would be happy just adding the to fb libraries to an X11 image. Guess I will have to try Lauren stuff next (again as I could not get it to
> build last year).

If you remove X11 you need to build (& use) QT-embedded as the
normal QT is X11 based.

Try using qt4e-demo-image instead which will build & use QT-embedded.

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

Re: fsl framebuffer image ?

[David Hill]

On 1/14/14, Jan 14, 9:25 PM, Lauren Post wrote:
> You can use the one in our meta-fsl-bsp-release layer.  There is one being reviewed based on the one Freescale released in the meta-fsl-bsp-release layer.  Our current 3.10.17-1.0.0 beta has support for all the graphical backends including the related image recipes for each backend.
>
> Get meta-fsl-release-layer from git.freescale.com.


Hi Lauren,
    could I trouble you for a quick question ? I am getting a build failure and have not a clue how to proceed.

meta-fsl-bsp-release & git checkout origin/dora_3.10.17-1.0.0_beta

MACHINE=imx6qsabrelite
bitbake fsl-iamge-fb

| arm-poky-linux-gnueabi-gcc  --sysroot=/home/ddhill/yocto/fsl3/fsl-community-bsp/imx6qsabrelite/tmp/sysroots/imx6qsabrelite  -g  -Os   -fno-common -ffixed-r8 -msoft-float  -D__KERNEL__ -DCONFIG_SYS_TEXT_BASE=0x17800000 -I/home/ddhill/yocto/fsl3/fsl-community-bsp/imx6qsabrelite/tmp/work/imx6qsabrelite-poky-linux-gnueabi/u-boot-imx/2013.04-r0/git/include -fno-builtin -ffreestanding -nostdinc -isystem /home/ddhill/yocto/fsl3/fsl-community-bsp/imx6qsabrelite/tmp/sysroots/i686-linux/usr/lib/cortexa9hf-vfp-neon-poky-linux-gnueabi/gcc/arm-poky-linux-gnueabi/4.8.1/include -pipe  -DCONFIG_ARM -D__ARM__ -marm -mno-thumb-interwork -mabi=aapcs-linux -march=armv7-a -Wall -Wstrict-prototypes -fno-stack-protector -Wno-format-nonliteral -Wno-format-security -fstack-usage     -o syslib.o syslib.c -c
| soc.c: In function 'v7_outer_cache_enable':
| soc.c:527:24: error: 'CONFIG_SYS_PL310_BASE' undeclared (first use in this function)
|    (struct pl310_regs *)CONFIG_SYS_PL310_BASE;
|                         ^
| soc.c:527:24: note: each undeclared identifier is reported only once for each function it appears in
| soc.c: In function 'v7_outer_cache_disable':
| soc.c:535:24: error: 'CONFIG_SYS_PL310_BASE' undeclared (first use in this function)
|    (struct pl310_regs *)CONFIG_SYS_PL310_BASE;
|                         ^
| make[1]: *** [soc.o] Error 1
| make[1]: Leaving directory `/home/ddhill/yocto/fsl3/fsl-community-bsp/imx6qsabrelite/tmp/work/imx6qsabrelite-poky-linux-gnueabi/u-boot-imx/2013.04-r0/git/arch/arm/cpu/armv7/mx6'
| make: *** [arch/arm/cpu/armv7/mx6/libmx6.o] Error 2
| make: *** Waiting for unfinished jobs....
| arm-poky-linux-gnueabi-ld.bfd  -r -o libarmv7.o  cache_v7.o cpu.o syslib.o lowlevel_init.o
| make[1]: Leaving directory `/home/ddhill/yocto/fsl3/fsl-community-bsp/imx6qsabrelite/tmp/work/imx6qsabrelite-poky-linux-gnueabi/u-boot-imx/2013.04-r0/git/arch/arm/cpu/armv7'
| ERROR: oe_runmake failed
| WARNING: exit code 1 from a shell command.
| ERROR: Function failed: do_compile (log file is located at /home/ddhill/yocto/fsl3/fsl-community-bsp/imx6qsabrelite/tmp/work/imx6qsabrelite-poky-linux-gnueabi/u-boot-imx/2013.04-r0/temp/log.do_compile.4418)


>
> Lauren
>
> -----Original Message-----
> From: meta-freescale-bounces@yoctoproject.org [mailto:meta-freescale-bounces@yoctoproject.org] On Behalf Of David Hill
> Sent: Tuesday, January 14, 2014 2:23 PM
> To: meta-freescale Mailing List
> Subject: [meta-freescale] fsl framebuffer image ?
>
>
>
> Hi,
>      I am interested in using imx6 in accelerated framebuffer mode. Currently I have a running fsl-image-gui, but that does not have the two accelerated framebuffer versions of libEGL.so & libGAL.so installed (at least that I could find.
>
> I have heard that there is a fsl-image-fb in the works. Is that likely to be mainlined anytime soon ?
>
> Any other suggestions on how to obtain the two shared libs ?
>
> thanks!
>


-- 
David Hill <David.Hill@Oracle.com>
Java Embedded Development

There cannot be a crisis next week. My schedule is already full.
-- Henry Kissinger (1923 - )

Re: fsl framebuffer image ?

[Otavio Salvador]

Hello David,

On Thu, Jan 30, 2014 at 7:55 PM, David Hill <David.Hill@oracle.com> wrote:
> On 1/14/14, Jan 14, 9:25 PM, Lauren Post wrote:
>>
>> You can use the one in our meta-fsl-bsp-release layer.  There is one being
>> reviewed based on the one Freescale released in the meta-fsl-bsp-release
>> layer.  Our current 3.10.17-1.0.0 beta has support for all the graphical
>> backends including the related image recipes for each backend.
>>
>> Get meta-fsl-release-layer from git.freescale.com.
>
>
>
> Hi Lauren,
>    could I trouble you for a quick question ? I am getting a build failure
> and have not a clue how to proceed.
>
> meta-fsl-bsp-release & git checkout origin/dora_3.10.17-1.0.0_beta
>
> MACHINE=imx6qsabrelite
> bitbake fsl-iamge-fb
...

Personally I don't use the meta-fsl-bsp-release layer as it's not a
community layer, and we cannot contribute back patches and fixes to
it.

The  release layer is the official way Freescale is using to release
its new source code on top of meta-fsl-arm. The supported board list
is limited and is usually available in its release notes. But I don't
believe sabrelite is supported, as it's not a board from Freescale.

I recommend you to use the fsl-community-bsp as is as sabrelite is
properly supported in there by Boundary Devices. You can see a blog
post[1] about how to build an image for Nitrogen6x (which works for
sabrelite board too). Just change "dylan" to "dora", the latest stable
release.

If you need kernel 3.10.17 you can have an early snapshot on
master-next, although it's a work in progress, so far.

1. http://www.ossystems.com.br/blog/2013/04/15/yocto-with-boundary-devices-nitrogen6x-5-steps-only.html

Regards,

-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750

Re: fsl framebuffer image ?

[David Hill]

Thanks Otavio,
   I see now that I picked the wrong machine type for the SDP in this build, which now make clear to me why I had a failure building u-boot. Unfortunately I don't need to do a lot of this so it is easy to stumble on which board is which.

    My need is for fsl-image-fb (or something close to it). Any recent kernel will do as long as I can get the accelerated framebuffer rendering stuff with a handful of other useful items like sshd.

We have several different boards in my group, Freescale and Boundry and maybe even a Wandboard, so I would really prefer not to use the meta-fsl-bsp-release if there is an easier, mainline way that I can understand. (And I guess follow directions).

Any suggestions as to how I should proceed with to get accelerated fb support with fsl-community-bsp other than the earlier suggestion of  qt4e-demo-image?

I really wish that fsl-image-x11 just contained the two needed GL libraries with different postfixes like it used to. (libEGL-fb.so) I don't care about the image size because I am not distributing it.

thanks,
     Dave


On 1/31/14, Jan 31, 11:11 AM, Otavio Salvador wrote:
> Hello David,
>
> On Thu, Jan 30, 2014 at 7:55 PM, David Hill <David.Hill@oracle.com> wrote:
>> On 1/14/14, Jan 14, 9:25 PM, Lauren Post wrote:
>>> You can use the one in our meta-fsl-bsp-release layer.  There is one being
>>> reviewed based on the one Freescale released in the meta-fsl-bsp-release
>>> layer.  Our current 3.10.17-1.0.0 beta has support for all the graphical
>>> backends including the related image recipes for each backend.
>>>
>>> Get meta-fsl-release-layer from git.freescale.com.
>>
>>
>> Hi Lauren,
>>     could I trouble you for a quick question ? I am getting a build failure
>> and have not a clue how to proceed.
>>
>> meta-fsl-bsp-release & git checkout origin/dora_3.10.17-1.0.0_beta
>>
>> MACHINE=imx6qsabrelite
>> bitbake fsl-iamge-fb
> ...
>
> Personally I don't use the meta-fsl-bsp-release layer as it's not a
> community layer, and we cannot contribute back patches and fixes to
> it.
>
> The  release layer is the official way Freescale is using to release
> its new source code on top of meta-fsl-arm. The supported board list
> is limited and is usually available in its release notes. But I don't
> believe sabrelite is supported, as it's not a board from Freescale.
>
> I recommend you to use the fsl-community-bsp as is as sabrelite is
> properly supported in there by Boundary Devices. You can see a blog
> post[1] about how to build an image for Nitrogen6x (which works for
> sabrelite board too). Just change "dylan" to "dora", the latest stable
> release.
>
> If you need kernel 3.10.17 you can have an early snapshot on
> master-next, although it's a work in progress, so far.
>
> 1. http://www.ossystems.com.br/blog/2013/04/15/yocto-with-boundary-devices-nitrogen6x-5-steps-only.html
>
> Regards,
>


-- 
David Hill <David.Hill@Oracle.com>
Java Embedded Development

Any society that would give up a little liberty to gain a little security will deserve neither and lose both.
-- Benjamin Franklin

Re: fsl framebuffer image ?

[Daiane Angolini]

On 31-01-2014 19:47, David Hill wrote:
>
> Thanks Otavio,
>    I see now that I picked the wrong machine type for the SDP in this
> build, which now make clear to me why I had a failure building u-boot.
> Unfortunately I don't need to do a lot of this so it is easy to stumble
> on which board is which.
>
>     My need is for fsl-image-fb (or something close to it). Any recent
> kernel will do as long as I can get the accelerated framebuffer
> rendering stuff with a handful of other useful items like sshd.

You could copy only the fsl-image-fb image file, for your first tests.

But, the piece of code you need is:

DISTRO_FEATURES_remove = "x11 wayland"

x11 and wayland are the default DISTRO_FEATURES backend, if you remove 
both, you have framebuffer.


Daiane

>
> We have several different boards in my group, Freescale and Boundry and
> maybe even a Wandboard, so I would really prefer not to use the
> meta-fsl-bsp-release if there is an easier, mainline way that I can
> understand. (And I guess follow directions).
>
> Any suggestions as to how I should proceed with to get accelerated fb
> support with fsl-community-bsp other than the earlier suggestion of
> qt4e-demo-image?
>
> I really wish that fsl-image-x11 just contained the two needed GL
> libraries with different postfixes like it used to. (libEGL-fb.so) I
> don't care about the image size because I am not distributing it.
>
> thanks,
>      Dave
>
>
> On 1/31/14, Jan 31, 11:11 AM, Otavio Salvador wrote:
>> Hello David,
>>
>> On Thu, Jan 30, 2014 at 7:55 PM, David Hill <David.Hill@oracle.com>
>> wrote:
>>> On 1/14/14, Jan 14, 9:25 PM, Lauren Post wrote:
>>>> You can use the one in our meta-fsl-bsp-release layer.  There is one
>>>> being
>>>> reviewed based on the one Freescale released in the
>>>> meta-fsl-bsp-release
>>>> layer.  Our current 3.10.17-1.0.0 beta has support for all the
>>>> graphical
>>>> backends including the related image recipes for each backend.
>>>>
>>>> Get meta-fsl-release-layer from git.freescale.com.
>>>
>>>
>>> Hi Lauren,
>>>     could I trouble you for a quick question ? I am getting a build
>>> failure
>>> and have not a clue how to proceed.
>>>
>>> meta-fsl-bsp-release & git checkout origin/dora_3.10.17-1.0.0_beta
>>>
>>> MACHINE=imx6qsabrelite
>>> bitbake fsl-iamge-fb
>> ...
>>
>> Personally I don't use the meta-fsl-bsp-release layer as it's not a
>> community layer, and we cannot contribute back patches and fixes to
>> it.
>>
>> The  release layer is the official way Freescale is using to release
>> its new source code on top of meta-fsl-arm. The supported board list
>> is limited and is usually available in its release notes. But I don't
>> believe sabrelite is supported, as it's not a board from Freescale.
>>
>> I recommend you to use the fsl-community-bsp as is as sabrelite is
>> properly supported in there by Boundary Devices. You can see a blog
>> post[1] about how to build an image for Nitrogen6x (which works for
>> sabrelite board too). Just change "dylan" to "dora", the latest stable
>> release.
>>
>> If you need kernel 3.10.17 you can have an early snapshot on
>> master-next, although it's a work in progress, so far.
>>
>> 1.
>> http://www.ossystems.com.br/blog/2013/04/15/yocto-with-boundary-devices-nitrogen6x-5-steps-only.html
>>
>>
>> Regards,
>>
>
>


-- 
Daiane

Re: fsl framebuffer image ?

[Rogerio Nunes]

On Mon, Feb 3, 2014 at 5:58 AM, Daiane Angolini
<daiane.angolini@freescale.com> wrote:
> On 31-01-2014 19:47, David Hill wrote:
>>
>>
>> Thanks Otavio,
>>    I see now that I picked the wrong machine type for the SDP in this
>> build, which now make clear to me why I had a failure building u-boot.
>> Unfortunately I don't need to do a lot of this so it is easy to stumble
>> on which board is which.
>>
>>     My need is for fsl-image-fb (or something close to it). Any recent
>> kernel will do as long as I can get the accelerated framebuffer
>> rendering stuff with a handful of other useful items like sshd.
>
>
> You could copy only the fsl-image-fb image file, for your first tests.
>
> But, the piece of code you need is:
>
> DISTRO_FEATURES_remove = "x11 wayland"
>

I suggest doing this for testing purposes only, and not as definitive solution.
Recipes are not the right place to change DISTRO_FEATURES, as you
break the dependency tree from one image to the other.
In other words, if you build different images, that result in
different DISTRO_FEATURES evaluation inside the same build dir, you
end up messing up with the build dir.
As final solution you should either override the DISTRO_FEATURES
variable inside local.conf or create your own distro layer, so that
every image you build has packages compatible with packages from the
other images you build inside the same build dir.

> x11 and wayland are the default DISTRO_FEATURES backend, if you remove both,
> you have framebuffer.
>
>
> Daiane
>
>
>>
>> We have several different boards in my group, Freescale and Boundry and
>> maybe even a Wandboard, so I would really prefer not to use the
>> meta-fsl-bsp-release if there is an easier, mainline way that I can
>> understand. (And I guess follow directions).
>>
>> Any suggestions as to how I should proceed with to get accelerated fb
>> support with fsl-community-bsp other than the earlier suggestion of
>> qt4e-demo-image?
>>
>> I really wish that fsl-image-x11 just contained the two needed GL
>> libraries with different postfixes like it used to. (libEGL-fb.so) I
>> don't care about the image size because I am not distributing it.
>>
>> thanks,
>>      Dave
>>
>>
>> On 1/31/14, Jan 31, 11:11 AM, Otavio Salvador wrote:
>>>
>>> Hello David,
>>>
>>> On Thu, Jan 30, 2014 at 7:55 PM, David Hill <David.Hill@oracle.com>
>>> wrote:
>>>>
>>>> On 1/14/14, Jan 14, 9:25 PM, Lauren Post wrote:
>>>>>
>>>>> You can use the one in our meta-fsl-bsp-release layer.  There is one
>>>>> being
>>>>> reviewed based on the one Freescale released in the
>>>>> meta-fsl-bsp-release
>>>>> layer.  Our current 3.10.17-1.0.0 beta has support for all the
>>>>> graphical
>>>>> backends including the related image recipes for each backend.
>>>>>
>>>>> Get meta-fsl-release-layer from git.freescale.com.
>>>>
>>>>
>>>>
>>>> Hi Lauren,
>>>>     could I trouble you for a quick question ? I am getting a build
>>>> failure
>>>> and have not a clue how to proceed.
>>>>
>>>> meta-fsl-bsp-release & git checkout origin/dora_3.10.17-1.0.0_beta
>>>>
>>>> MACHINE=imx6qsabrelite
>>>> bitbake fsl-iamge-fb
>>>
>>> ...
>>>
>>> Personally I don't use the meta-fsl-bsp-release layer as it's not a
>>> community layer, and we cannot contribute back patches and fixes to
>>> it.
>>>
>>> The  release layer is the official way Freescale is using to release
>>> its new source code on top of meta-fsl-arm. The supported board list
>>> is limited and is usually available in its release notes. But I don't
>>> believe sabrelite is supported, as it's not a board from Freescale.
>>>
>>> I recommend you to use the fsl-community-bsp as is as sabrelite is
>>> properly supported in there by Boundary Devices. You can see a blog
>>> post[1] about how to build an image for Nitrogen6x (which works for
>>> sabrelite board too). Just change "dylan" to "dora", the latest stable
>>> release.
>>>
>>> If you need kernel 3.10.17 you can have an early snapshot on
>>> master-next, although it's a work in progress, so far.
>>>
>>> 1.
>>>
>>> http://www.ossystems.com.br/blog/2013/04/15/yocto-with-boundary-devices-nitrogen6x-5-steps-only.html
>>>
>>>
>>> Regards,
>>>
>>
>>
>
>
> --
> Daiane
>
>
> _______________________________________________
> meta-freescale mailing list
> meta-freescale@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-freescale

Re: fsl framebuffer image ?

[David Hill]

On 1/15/14, Jan 15, 11:16 AM, Gary Thomas wrote:
>
> If you remove X11 you need to build (& use) QT-embedded as the
> normal QT is X11 based.
>
> Try using qt4e-demo-image instead which will build & use QT-embedded.
>

Gary - (finally) got a build with qt4e-demo-image, but it does not help a much as I thought. There is EGL there, but it is not accelerated, which is a bummer.

Dave

-- 
David Hill <David.Hill@Oracle.com>
Java Embedded Development

"If at first you don't succeed; call it version 1.0"

Re: fsl framebuffer image ?

[Otavio Salvador]

Hello David,

On Mon, Feb 3, 2014 at 6:19 PM, David Hill <David.Hill@oracle.com> wrote:
> On 1/15/14, Jan 15, 11:16 AM, Gary Thomas wrote:
>> If you remove X11 you need to build (& use) QT-embedded as the
>> normal QT is X11 based.
>>
>> Try using qt4e-demo-image instead which will build & use QT-embedded.
>>
>
> Gary - (finally) got a build with qt4e-demo-image, but it does not help a
> much as I thought. There is EGL there, but it is not accelerated, which is a
> bummer.

It is accelerated for sure. I use it with several customers...

-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750

Re: fsl framebuffer image ?

[Otavio Salvador]

Hello,

On Mon, Feb 3, 2014 at 6:22 PM, Otavio Salvador <otavio@ossystems.com.br> wrote:
> On Mon, Feb 3, 2014 at 6:19 PM, David Hill <David.Hill@oracle.com> wrote:
>> On 1/15/14, Jan 15, 11:16 AM, Gary Thomas wrote:
>>> If you remove X11 you need to build (& use) QT-embedded as the
>>> normal QT is X11 based.
>>>
>>> Try using qt4e-demo-image instead which will build & use QT-embedded.
>>>
>>
>> Gary - (finally) got a build with qt4e-demo-image, but it does not help a
>> much as I thought. There is EGL there, but it is not accelerated, which is a
>> bummer.
>
> It is accelerated for sure. I use it with several customers...

Did you set the distro features in local.conf?

-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750

Re: fsl framebuffer image ?

[David Hill]

On 2/3/14, Feb 3, 3:22 PM, Otavio Salvador wrote:
> Hello David,
>
> On Mon, Feb 3, 2014 at 6:19 PM, David Hill <David.Hill@oracle.com> wrote:
>> On 1/15/14, Jan 15, 11:16 AM, Gary Thomas wrote:
>>> If you remove X11 you need to build (& use) QT-embedded as the
>>> normal QT is X11 based.
>>>
>>> Try using qt4e-demo-image instead which will build & use QT-embedded.
>>>
>> Gary - (finally) got a build with qt4e-demo-image, but it does not help a
>> much as I thought. There is EGL there, but it is not accelerated, which is a
>> bummer.
> It is accelerated for sure. I use it with several customers...
>
OK - now very confused.

On my other imx6 images, we learned that to init EGL for use with the framebuffer, we needed to use fbGetDisplayByIndex() and fbCreateWindow().
So when I did not find these in libEGL.so I assumed....

Any chance you have a pointer to an EGL init sequence that works with this image ?

Or does this just use EGLNativeDisplayType & EGLNativeWindowType of NULL like some other platforms ?

-- 
David Hill <David.Hill@Oracle.com>
Java Embedded Development

Socialism is great until you run out of other peoples money
-- Margaret Thatcher

Re: fsl framebuffer image ?

[David Hill]

On 2/3/14, Feb 3, 3:25 PM, Otavio Salvador wrote:
> Hello,
>
> On Mon, Feb 3, 2014 at 6:22 PM, Otavio Salvador <otavio@ossystems.com.br> wrote:
>> On Mon, Feb 3, 2014 at 6:19 PM, David Hill <David.Hill@oracle.com> wrote:
>>> On 1/15/14, Jan 15, 11:16 AM, Gary Thomas wrote:
>>>> If you remove X11 you need to build (& use) QT-embedded as the
>>>> normal QT is X11 based.
>>>>
>>>> Try using qt4e-demo-image instead which will build & use QT-embedded.
>>>>
>>> Gary - (finally) got a build with qt4e-demo-image, but it does not help a
>>> much as I thought. There is EGL there, but it is not accelerated, which is a
>>> bummer.
>> It is accelerated for sure. I use it with several customers...
> Did you set the distro features in local.conf?
>
No, I did not set any distro_features this time. Only addition (other than DL_DIR) was to add:

IMAGE_FEATURES += "ssh-server-dropbear"

and use

bitbake qt4e-demo-image


I have been wading through
http://www.yoctoproject.org/docs/current/yocto-project-qs/yocto-project-qs.html
http://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html
but still feel like I am in kindergarten.

Does not help that my build machine takes 11 hours to perform a clean build.

-- 
David Hill <David.Hill@Oracle.com>
Java Embedded Development

"As you journey through life take a minute every now and then to give a thought for the other fellow. He could be plotting something."
-- Hagar the Horrible

Re: fsl framebuffer image ?

[Otavio Salvador]

Hello David,

On Mon, Feb 3, 2014 at 6:43 PM, David Hill <David.Hill@oracle.com> wrote:
> On 2/3/14, Feb 3, 3:25 PM, Otavio Salvador wrote:
>> On Mon, Feb 3, 2014 at 6:22 PM, Otavio Salvador <otavio@ossystems.com.br>
>> wrote:
>>>
>>> On Mon, Feb 3, 2014 at 6:19 PM, David Hill <David.Hill@oracle.com> wrote:
>>>>
>>>> On 1/15/14, Jan 15, 11:16 AM, Gary Thomas wrote:
>>>>>
>>>>> If you remove X11 you need to build (& use) QT-embedded as the
>>>>> normal QT is X11 based.
>>>>>
>>>>> Try using qt4e-demo-image instead which will build & use QT-embedded.
>>>>>
>>>> Gary - (finally) got a build with qt4e-demo-image, but it does not help
>>>> a
>>>> much as I thought. There is EGL there, but it is not accelerated, which
>>>> is a
>>>> bummer.
>>>
>>> It is accelerated for sure. I use it with several customers...
>>
>> Did you set the distro features in local.conf?
>>
> No, I did not set any distro_features this time. Only addition (other than
> DL_DIR) was to add:
>
> IMAGE_FEATURES += "ssh-server-dropbear"
>
> and use
>
> bitbake qt4e-demo-image
>
>
> I have been wading through
> http://www.yoctoproject.org/docs/current/yocto-project-qs/yocto-project-qs.html
> http://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html
> but still feel like I am in kindergarten.
>
> Does not help that my build machine takes 11 hours to perform a clean build.

Yes so it is expected to not be accelerated in Framebuffer backend as
by default it will use X11 backend. Blame Vivante to make those
non-parallel :-(

So please add to your local.conf:

DISTRO_FEATURES_remove = "x11 wayland"

remove your tmp dir and build your image again.

-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750

Re: fsl framebuffer image ?

[David Hill]

On 2/3/14, Feb 3, 8:32 PM, Otavio Salvador wrote:
> Yes so it is expected to not be accelerated in Framebuffer backend as by default it will use X11 backend. Blame Vivante to make those non-parallel :-( So please add to your local.conf: DISTRO_FEATURES_remove = "x11 wayland" remove your tmp dir and build your image again. 

Which target would you expect I should use when I remove "x11 wayland"?
   fsl-image-x11 (fails)
   fsl-image-gui  (fails)
   fsl-image-test (currently building, will know tomorrow)
   core-image-x11

Thanks !


-- 
David Hill <David.Hill@Oracle.com>
Java Embedded Development

"What luck for rulers that men do not think."
-- Adolf Hitler (1889 - 1945)

Re: fsl framebuffer image ?

[Otavio Salvador]

On Tue, Feb 4, 2014 at 8:47 PM, David Hill <David.Hill@oracle.com> wrote:
> On 2/3/14, Feb 3, 8:32 PM, Otavio Salvador wrote:
>>
>> Yes so it is expected to not be accelerated in Framebuffer backend as by
>> default it will use X11 backend. Blame Vivante to make those non-parallel
>> :-( So please add to your local.conf: DISTRO_FEATURES_remove = "x11 wayland"
>> remove your tmp dir and build your image again.
>
>
> Which target would you expect I should use when I remove "x11 wayland"?
>   fsl-image-x11 (fails)
>   fsl-image-gui  (fails)
>   fsl-image-test (currently building, will know tomorrow)
>   core-image-x11

core-image-base and add the recipe you wish. Faster and easier to debug.

-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750

Re: fsl framebuffer image ?

[Filip Piechocki]

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

Hi,

I currently also needed an image with accelerated framebuffer (so I could
run Qt5 eglfs on it) on wandboard-dual. I followed those instructions:
http://wiki.wandboard.org/index.php/Building_Qt5_using_yocto_on_Wandboard ,
with some modifications. I suggest you to do:
- add DISTRO_FEATURES_remove = "x11 wayland"
- add IMAGE_INSTALL_append = " gpu-viv-bin-mx6q "

Then I bitbaked core-image-minimal and it has libGAL, libEGL (and so on) in
framebuffer version.

Regards,
Filip


On Wed, Feb 5, 2014 at 12:17 AM, Otavio Salvador <otavio@ossystems.com.br>wrote:

> On Tue, Feb 4, 2014 at 8:47 PM, David Hill <David.Hill@oracle.com> wrote:
> > On 2/3/14, Feb 3, 8:32 PM, Otavio Salvador wrote:
> >>
> >> Yes so it is expected to not be accelerated in Framebuffer backend as by
> >> default it will use X11 backend. Blame Vivante to make those
> non-parallel
> >> :-( So please add to your local.conf: DISTRO_FEATURES_remove = "x11
> wayland"
> >> remove your tmp dir and build your image again.
> >
> >
> > Which target would you expect I should use when I remove "x11 wayland"?
> >   fsl-image-x11 (fails)
> >   fsl-image-gui  (fails)
> >   fsl-image-test (currently building, will know tomorrow)
> >   core-image-x11
>
> core-image-base and add the recipe you wish. Faster and easier to debug.
>
> --
> Otavio Salvador                             O.S. Systems
> http://www.ossystems.com.br        http://code.ossystems.com.br
> Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750
> _______________________________________________
> meta-freescale mailing list
> meta-freescale@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-freescale
>

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

Re: fsl framebuffer image ?

[David Hill]

On 2/5/14, Feb 5, 12:37 AM, Filip Piechocki wrote:
> Hi,
>
> I currently also needed an image with accelerated framebuffer (so I could run Qt5 eglfs on it) on wandboard-dual. I followed those instructions: http://wiki.wandboard.org/index.php/Building_Qt5_using_yocto_on_Wandboard , with some modifications. I suggest you to do:
> - add DISTRO_FEATURES_remove = "x11 wayland"
> - add IMAGE_INSTALL_append = " gpu-viv-bin-mx6q "
>
> Then I bitbaked core-image-minimal and it has libGAL, libEGL (and so on) in framebuffer version.

I did a bitbake qt4e-demo-image and did not get the accelerated images as you probably saw earlier.

Turns out that the needed libraries are in the build tree, but the script that picks which of the versions to install may not be correct.

You want these:
tmp/work/cortexa9hf-vfp-neon-mx6-poky-linux-gnueabi/gpu-viv-bin-mx6q/1_3.10.9-1.0.0-hfp-r0/gpu-viv-bin-mx6q-3.10.9-1.0.0-hfp/usr/lib/libEGL-fb.so
tmp/work/cortexa9hf-vfp-neon-mx6-poky-linux-gnueabi/gpu-viv-bin-mx6q/1_3.10.9-1.0.0-hfp-r0/gpu-viv-bin-mx6q-3.10.9-1.0.0-hfp/usr/lib/libGAL-fb.so
tmp/work/cortexa9hf-vfp-neon-mx6-poky-linux-gnueabi/gpu-viv-bin-mx6q/1_3.10.9-1.0.0-hfp-r0/gpu-viv-bin-mx6q-3.10.9-1.0.0-hfp/usr/lib/libVIVANTE-fb.so

It was suggested that I do:

# force the gpu-viv-bin-mx6q install script to fall through to framebuffer
DISTRO_FEATURES_remove = "x11 wayland"

bitbake qt4e-demo-image

When I did the qt4e-demo-image without the remove, I did get a libEGL.so, but it was libEGL-x11.so based on the checksum. Copying the correct libEGL-fb.so and libGAL.fb allowed me to render to the fb just fine using my test app.

If curious, the install script is sources/meta-fsl-arm/recipes-graphics/gpu-viv-bin-mx6q/gpu-viv-bin-mx6q.inc, which explained to me why the remove x11 might do something.

But I have not done a second build with the x11 remove quite yet (partly because I misunderstood the suggestion). Perhaps I will know by tomorrow (I have a slow bld machine - 11 plus hours per build).

Dave




-- 
David Hill <David.Hill@Oracle.com>
Java Embedded Development

"Unix is user-friendly. It's just very selective about who its friends are."

Re: fsl framebuffer image ?

[David Hill]

I can confirm that wih DISTRO_FEATURES_remove = "x11 wayland" that bitbake qt4e-demo-image is not copying the libEGL.so and friends to the resulting image.

On 2/6/14, Feb 6, 5:48 PM, David Hill wrote:
> On 2/5/14, Feb 5, 12:37 AM, Filip Piechocki wrote:
>> Hi,
>>
>> I currently also needed an image with accelerated framebuffer (so I could run Qt5 eglfs on it) on wandboard-dual. I followed those instructions: http://wiki.wandboard.org/index.php/Building_Qt5_using_yocto_on_Wandboard , with some modifications. I suggest you to do:
>> - add DISTRO_FEATURES_remove = "x11 wayland"
>> - add IMAGE_INSTALL_append = " gpu-viv-bin-mx6q "
>>
>> Then I bitbaked core-image-minimal and it has libGAL, libEGL (and so on) in framebuffer version.
>
> I did a bitbake qt4e-demo-image and did not get the accelerated images as you probably saw earlier.
>
> Turns out that the needed libraries are in the build tree, but the script that picks which of the versions to install may not be correct.
>
> You want these:
> tmp/work/cortexa9hf-vfp-neon-mx6-poky-linux-gnueabi/gpu-viv-bin-mx6q/1_3.10.9-1.0.0-hfp-r0/gpu-viv-bin-mx6q-3.10.9-1.0.0-hfp/usr/lib/libEGL-fb.so
> tmp/work/cortexa9hf-vfp-neon-mx6-poky-linux-gnueabi/gpu-viv-bin-mx6q/1_3.10.9-1.0.0-hfp-r0/gpu-viv-bin-mx6q-3.10.9-1.0.0-hfp/usr/lib/libGAL-fb.so
> tmp/work/cortexa9hf-vfp-neon-mx6-poky-linux-gnueabi/gpu-viv-bin-mx6q/1_3.10.9-1.0.0-hfp-r0/gpu-viv-bin-mx6q-3.10.9-1.0.0-hfp/usr/lib/libVIVANTE-fb.so
>
> It was suggested that I do:
>
> # force the gpu-viv-bin-mx6q install script to fall through to framebuffer
> DISTRO_FEATURES_remove = "x11 wayland"
>
> bitbake qt4e-demo-image
>
> When I did the qt4e-demo-image without the remove, I did get a libEGL.so, but it was libEGL-x11.so based on the checksum. Copying the correct libEGL-fb.so and libGAL.fb allowed me to render to the fb just fine using my test app.
>
> If curious, the install script is sources/meta-fsl-arm/recipes-graphics/gpu-viv-bin-mx6q/gpu-viv-bin-mx6q.inc, which explained to me why the remove x11 might do something.
>
> But I have not done a second build with the x11 remove quite yet (partly because I misunderstood the suggestion). Perhaps I will know by tomorrow (I have a slow bld machine - 11 plus hours per build).
>
> Dave
>
>
>
>


-- 
David Hill <David.Hill@Oracle.com>
Java Embedded Development

"If you put tomfoolery into a computer, nothing comes out of it but tomfoolery. But this tomfoolery, having passed through a very expensive machine, is somehow ennobled and no-one dares criticize it."
-- Pierre Gallois

Re: fsl framebuffer image ?

[Otavio Salvador]

Hello David,

On Fri, Feb 7, 2014 at 4:54 PM, David Hill <David.Hill@oracle.com> wrote:
> I can confirm that wih DISTRO_FEATURES_remove = "x11 wayland" that bitbake
> qt4e-demo-image is not copying the libEGL.so and friends to the resulting
> image.

I will debug this and try to reproduce it. I let you know when I found
something.

-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750

Re: fsl framebuffer image ?

[Filip Piechocki]

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

I don't know exactly what you want to achieve, but did you try adding:

IMAGE_INSTALL_append = " gpu-viv-bin-mx6q "

?

I did not found this in previous emails. For me this, and
DISTRO_FEATURES_remove = "x11 wayland" solves the case - I get the image
with correct libEGL.so etc (the ones for framebuffer). You can even add
"qt4-embedded" to IMAGE_INSTALL_append and you will get Qt4 with QWS on the
image.

Regards,
Filip


On Fri, Feb 7, 2014 at 7:56 PM, Otavio Salvador <otavio@ossystems.com.br>wrote:

> Hello David,
>
> On Fri, Feb 7, 2014 at 4:54 PM, David Hill <David.Hill@oracle.com> wrote:
> > I can confirm that wih DISTRO_FEATURES_remove = "x11 wayland" that
> bitbake
> > qt4e-demo-image is not copying the libEGL.so and friends to the resulting
> > image.
>
> I will debug this and try to reproduce it. I let you know when I found
> something.
>
> --
> Otavio Salvador                             O.S. Systems
> http://www.ossystems.com.br        http://code.ossystems.com.br
> Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750
> _______________________________________________
> meta-freescale mailing list
> meta-freescale@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-freescale
>

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

Re: fsl framebuffer image ?

[Otavio Salvador]

Hello David,

On Fri, Feb 7, 2014 at 4:56 PM, Otavio Salvador <otavio@ossystems.com.br> wrote:
> On Fri, Feb 7, 2014 at 4:54 PM, David Hill <David.Hill@oracle.com> wrote:
>> I can confirm that wih DISTRO_FEATURES_remove = "x11 wayland" that bitbake
>> qt4e-demo-image is not copying the libEGL.so and friends to the resulting
>> image.
>
> I will debug this and try to reproduce it. I let you know when I found
> something.

I intend to check this today but I'd like to avoid losing time to
figure out what you did. Could you send me, even privately, your
local.conf file so I can reproduce right away your build environment?

-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750