Patchwork [meta-fsl-arm-extra,3/4] linux-cfa: add a kernel recipe supporting Crystalfontz boards

login
register
mail settings
Submitter Alexandre Belloni
Date Aug. 22, 2013, 2:51 p.m.
Message ID <1377183077-5270-4-git-send-email-alexandre.belloni@free-electrons.com>
Download mbox | patch
Permalink /patch/56271/
State Changes Requested
Delegated to: Otavio Salvador
Headers show

Comments

Alexandre Belloni - Aug. 22, 2013, 2:51 p.m.
Signed-off-by: Alexandre Belloni <alexandre.belloni@free-electrons.com>
---
 recipes-kernel/linux/linux-cfa-3.10/defconfig | 177 ++++++++++++++++++++++++++
 recipes-kernel/linux/linux-cfa_3.10.bb        |  33 +++++
 2 files changed, 210 insertions(+)
 create mode 100644 recipes-kernel/linux/linux-cfa-3.10/defconfig
 create mode 100644 recipes-kernel/linux/linux-cfa_3.10.bb
Otavio Salvador - Aug. 22, 2013, 5:06 p.m.
On Thu, Aug 22, 2013 at 11:51 AM, Alexandre Belloni
<alexandre.belloni@free-electrons.com> wrote:
> Signed-off-by: Alexandre Belloni <alexandre.belloni@free-electrons.com>
> ---
>  recipes-kernel/linux/linux-cfa-3.10/defconfig | 177 ++++++++++++++++++++++++++
>  recipes-kernel/linux/linux-cfa_3.10.bb        |  33 +++++
>  2 files changed, 210 insertions(+)
>  create mode 100644 recipes-kernel/linux/linux-cfa-3.10/defconfig
>  create mode 100644 recipes-kernel/linux/linux-cfa_3.10.bb
>
> diff --git a/recipes-kernel/linux/linux-cfa-3.10/defconfig b/recipes-kernel/linux/linux-cfa-3.10/defconfig
...
> diff --git a/recipes-kernel/linux/linux-cfa_3.10.bb b/recipes-kernel/linux/linux-cfa_3.10.bb
> new file mode 100644
> index 0000000..2c2a723
> --- /dev/null
> +++ b/recipes-kernel/linux/linux-cfa_3.10.bb
> @@ -0,0 +1,33 @@
> +DESCRIPTION = "Linux kernel for Crystalfontz boards"
> +SECTion = "kernel"
> +LICENSE = "GPLv2"
> +
> +LIC_FILES_CHKSUM = "file://COPYING;md5=d7810fab7487fb0aad327b76f1be7cd7"
> +
> +inherit kernel
> +require recipes-kernel/linux/linux-dtb.inc
> +
> +SRC_URI = "git://github.com/crystalfontz/cfa_10036_kernel \
> +           file://defconfig"
> +
> +SRCREV = "552d876f4737ffeb18c9139ede3c439bdcafca94"
> +
> +S = "${WORKDIR}/git"
> +
> +# create symlinks that are the defaults of barebox
> +pkg_postinst_kernel-devicetree_append () {
> +       for DTB_FILE in ${KERNEL_DEVICETREE}
> +       do
> +               DTB_BASE_NAME=`basename ${DTB_FILE} | awk -F "." '{print $1}'`
> +               DTB_BOARD_NAME=`echo ${DTB_BASE_NAME} | awk -F "-" '{print $2}'`
> +               DTB_SYMLINK_NAME=`echo ${KERNEL_IMAGE_SYMLINK_NAME} | sed "s/${MACHINE}/${DTB_BASE_NAME}/g"`
> +               update-alternatives --install /${KERNEL_IMAGEDEST}/oftree-${DTB_BOARD_NAME} oftree-${DTB_BOARD_NAME} devicetree-${DTB_SYMLINK_NAME}.dtb ${KERNEL_PRIORITY} || true
> +       done
> +}
> +
> +pkg_postinst_kernel-image_append () {
> +       update-alternatives --install /${KERNEL_IMAGEDEST}/${KERNEL_IMAGETYPE}-${MACHINE} ${KERNEL_IMAGETYPE}-${MACHINE} ${KERNEL_IMAGETYPE}-${KERNEL_VERSION} ${KERNEL_PRIORITY} || true
> +}
> +
> +COMPATIBLE_MACHINE = "cfa10036"
> +

What it does different here than original linux-dtb alternatives?
Alexandre Belloni - Aug. 22, 2013, 5:17 p.m.
On 22/08/2013 19:06, Otavio Salvador wrote:
> On Thu, Aug 22, 2013 at 11:51 AM, Alexandre Belloni
> <alexandre.belloni@free-electrons.com> wrote:
>> Signed-off-by: Alexandre Belloni <alexandre.belloni@free-electrons.com>
>> ---
>>  recipes-kernel/linux/linux-cfa-3.10/defconfig | 177 ++++++++++++++++++++++++++
>>  recipes-kernel/linux/linux-cfa_3.10.bb        |  33 +++++
>>  2 files changed, 210 insertions(+)
>>  create mode 100644 recipes-kernel/linux/linux-cfa-3.10/defconfig
>>  create mode 100644 recipes-kernel/linux/linux-cfa_3.10.bb
>>
>> diff --git a/recipes-kernel/linux/linux-cfa-3.10/defconfig b/recipes-kernel/linux/linux-cfa-3.10/defconfig
> ...
>> diff --git a/recipes-kernel/linux/linux-cfa_3.10.bb b/recipes-kernel/linux/linux-cfa_3.10.bb
>> new file mode 100644
>> index 0000000..2c2a723
>> --- /dev/null
>> +++ b/recipes-kernel/linux/linux-cfa_3.10.bb
>> @@ -0,0 +1,33 @@
>> +DESCRIPTION = "Linux kernel for Crystalfontz boards"
>> +SECTion = "kernel"
>> +LICENSE = "GPLv2"
>> +
>> +LIC_FILES_CHKSUM = "file://COPYING;md5=d7810fab7487fb0aad327b76f1be7cd7"
>> +
>> +inherit kernel
>> +require recipes-kernel/linux/linux-dtb.inc
>> +
>> +SRC_URI = "git://github.com/crystalfontz/cfa_10036_kernel \
>> +           file://defconfig"
>> +
>> +SRCREV = "552d876f4737ffeb18c9139ede3c439bdcafca94"
>> +
>> +S = "${WORKDIR}/git"
>> +
>> +# create symlinks that are the defaults of barebox
>> +pkg_postinst_kernel-devicetree_append () {
>> +       for DTB_FILE in ${KERNEL_DEVICETREE}
>> +       do
>> +               DTB_BASE_NAME=`basename ${DTB_FILE} | awk -F "." '{print $1}'`
>> +               DTB_BOARD_NAME=`echo ${DTB_BASE_NAME} | awk -F "-" '{print $2}'`
>> +               DTB_SYMLINK_NAME=`echo ${KERNEL_IMAGE_SYMLINK_NAME} | sed "s/${MACHINE}/${DTB_BASE_NAME}/g"`
>> +               update-alternatives --install /${KERNEL_IMAGEDEST}/oftree-${DTB_BOARD_NAME} oftree-${DTB_BOARD_NAME} devicetree-${DTB_SYMLINK_NAME}.dtb ${KERNEL_PRIORITY} || true
>> +       done
>> +}
>> +
>> +pkg_postinst_kernel-image_append () {
>> +       update-alternatives --install /${KERNEL_IMAGEDEST}/${KERNEL_IMAGETYPE}-${MACHINE} ${KERNEL_IMAGETYPE}-${MACHINE} ${KERNEL_IMAGETYPE}-${KERNEL_VERSION} ${KERNEL_PRIORITY} || true
>> +}
>> +
>> +COMPATIBLE_MACHINE = "cfa10036"
>> +
> What it does different here than original linux-dtb alternatives?
>

Actually, the default environment present in the barebox mainline for
the cfa10036 is looking for a kernel named zImage-cfa10036 and DTBs
named oftree-${DTB_BOARD_NAME} in /boot. So I'm just creating more links
to the kernel and DTBs. I'm not doing anything differently, I'm just
creating more links.
Otavio Salvador - Aug. 22, 2013, 5:19 p.m.
On Thu, Aug 22, 2013 at 2:17 PM, Alexandre Belloni
<alexandre.belloni@free-electrons.com> wrote:
> On 22/08/2013 19:06, Otavio Salvador wrote:
>> On Thu, Aug 22, 2013 at 11:51 AM, Alexandre Belloni
>> <alexandre.belloni@free-electrons.com> wrote:
>>> Signed-off-by: Alexandre Belloni <alexandre.belloni@free-electrons.com>
>>> ---
>>>  recipes-kernel/linux/linux-cfa-3.10/defconfig | 177 ++++++++++++++++++++++++++
>>>  recipes-kernel/linux/linux-cfa_3.10.bb        |  33 +++++
>>>  2 files changed, 210 insertions(+)
>>>  create mode 100644 recipes-kernel/linux/linux-cfa-3.10/defconfig
>>>  create mode 100644 recipes-kernel/linux/linux-cfa_3.10.bb
>>>
>>> diff --git a/recipes-kernel/linux/linux-cfa-3.10/defconfig b/recipes-kernel/linux/linux-cfa-3.10/defconfig
>> ...
>>> diff --git a/recipes-kernel/linux/linux-cfa_3.10.bb b/recipes-kernel/linux/linux-cfa_3.10.bb
>>> new file mode 100644
>>> index 0000000..2c2a723
>>> --- /dev/null
>>> +++ b/recipes-kernel/linux/linux-cfa_3.10.bb
>>> @@ -0,0 +1,33 @@
>>> +DESCRIPTION = "Linux kernel for Crystalfontz boards"
>>> +SECTion = "kernel"
>>> +LICENSE = "GPLv2"
>>> +
>>> +LIC_FILES_CHKSUM = "file://COPYING;md5=d7810fab7487fb0aad327b76f1be7cd7"
>>> +
>>> +inherit kernel
>>> +require recipes-kernel/linux/linux-dtb.inc
>>> +
>>> +SRC_URI = "git://github.com/crystalfontz/cfa_10036_kernel \
>>> +           file://defconfig"
>>> +
>>> +SRCREV = "552d876f4737ffeb18c9139ede3c439bdcafca94"
>>> +
>>> +S = "${WORKDIR}/git"
>>> +
>>> +# create symlinks that are the defaults of barebox
>>> +pkg_postinst_kernel-devicetree_append () {
>>> +       for DTB_FILE in ${KERNEL_DEVICETREE}
>>> +       do
>>> +               DTB_BASE_NAME=`basename ${DTB_FILE} | awk -F "." '{print $1}'`
>>> +               DTB_BOARD_NAME=`echo ${DTB_BASE_NAME} | awk -F "-" '{print $2}'`
>>> +               DTB_SYMLINK_NAME=`echo ${KERNEL_IMAGE_SYMLINK_NAME} | sed "s/${MACHINE}/${DTB_BASE_NAME}/g"`
>>> +               update-alternatives --install /${KERNEL_IMAGEDEST}/oftree-${DTB_BOARD_NAME} oftree-${DTB_BOARD_NAME} devicetree-${DTB_SYMLINK_NAME}.dtb ${KERNEL_PRIORITY} || true
>>> +       done
>>> +}
>>> +
>>> +pkg_postinst_kernel-image_append () {
>>> +       update-alternatives --install /${KERNEL_IMAGEDEST}/${KERNEL_IMAGETYPE}-${MACHINE} ${KERNEL_IMAGETYPE}-${MACHINE} ${KERNEL_IMAGETYPE}-${KERNEL_VERSION} ${KERNEL_PRIORITY} || true
>>> +}
>>> +
>>> +COMPATIBLE_MACHINE = "cfa10036"
>>> +
>> What it does different here than original linux-dtb alternatives?
>>
>
> Actually, the default environment present in the barebox mainline for
> the cfa10036 is looking for a kernel named zImage-cfa10036 and DTBs
> named oftree-${DTB_BOARD_NAME} in /boot. So I'm just creating more links
> to the kernel and DTBs. I'm not doing anything differently, I'm just
> creating more links.

I'd patch the default environment so we avoid custom behaviour from
other boards. Do you mind?
Alexandre Belloni - Aug. 22, 2013, 5:27 p.m.
On 22/08/2013 19:19, Otavio Salvador wrote:
>
>>> What it does different here than original linux-dtb alternatives?
>>>
>> Actually, the default environment present in the barebox mainline for
>> the cfa10036 is looking for a kernel named zImage-cfa10036 and DTBs
>> named oftree-${DTB_BOARD_NAME} in /boot. So I'm just creating more links
>> to the kernel and DTBs. I'm not doing anything differently, I'm just
>> creating more links.
> I'd patch the default environment so we avoid custom behaviour from
> other boards. Do you mind?
>
Hum, I'm not sure about that, that would mean that we would have a
different behaviour between the buildroot generated image and the yocto
generated image which is not so great from a customer support point of view.
Also oftree is the usual name for dtbs in barebox, I'd like to stick to
it. That is just a bunch of links and that part will stay in the
crystalfontz specific kernel recipe anyway, does it matter that much ?
Eric BENARD - Aug. 22, 2013, 5:47 p.m.
Hi Alexandre,

Le Thu, 22 Aug 2013 19:27:43 +0200,
Alexandre Belloni <alexandre.belloni@free-electrons.com> a écrit :

> On 22/08/2013 19:19, Otavio Salvador wrote:
> >
> >>> What it does different here than original linux-dtb alternatives?
> >>>
> >> Actually, the default environment present in the barebox mainline for
> >> the cfa10036 is looking for a kernel named zImage-cfa10036 and DTBs
> >> named oftree-${DTB_BOARD_NAME} in /boot. So I'm just creating more links
> >> to the kernel and DTBs. I'm not doing anything differently, I'm just
> >> creating more links.
> > I'd patch the default environment so we avoid custom behaviour from
> > other boards. Do you mind?
> >
> Hum, I'm not sure about that, that would mean that we would have a
> different behaviour between the buildroot generated image and the yocto
> generated image which is not so great from a customer support point of view.
> Also oftree is the usual name for dtbs in barebox, I'd like to stick to
> it. That is just a bunch of links and that part will stay in the
> crystalfontz specific kernel recipe anyway, does it matter that much ?
> 
fully agreed, that's a custom recipe for a custom board so I don't see
how you can get "custom behaviour from other boards".

Eric
Otavio Salvador - Aug. 22, 2013, 5:56 p.m.
On Thu, Aug 22, 2013 at 2:27 PM, Alexandre Belloni
<alexandre.belloni@free-electrons.com> wrote:
> On 22/08/2013 19:19, Otavio Salvador wrote:
>>
>>>> What it does different here than original linux-dtb alternatives?
>>>>
>>> Actually, the default environment present in the barebox mainline for
>>> the cfa10036 is looking for a kernel named zImage-cfa10036 and DTBs
>>> named oftree-${DTB_BOARD_NAME} in /boot. So I'm just creating more links
>>> to the kernel and DTBs. I'm not doing anything differently, I'm just
>>> creating more links.
>> I'd patch the default environment so we avoid custom behaviour from
>> other boards. Do you mind?
>>
> Hum, I'm not sure about that, that would mean that we would have a
> different behaviour between the buildroot generated image and the yocto
> generated image which is not so great from a customer support point of view.
> Also oftree is the usual name for dtbs in barebox, I'd like to stick to
> it. That is just a bunch of links and that part will stay in the
> crystalfontz specific kernel recipe anyway, does it matter that much ?

No; but it is code for you to maintain and be sure it keeps working.
Personally I'd stick to OE-Core standard but it is up to you to
decide. I am fine with both ways.
Alexandre Belloni - Aug. 22, 2013, 11:11 p.m.
On 22/08/2013 19:56, Otavio Salvador wrote:
> On Thu, Aug 22, 2013 at 2:27 PM, Alexandre Belloni
> <alexandre.belloni@free-electrons.com> wrote:
>> On 22/08/2013 19:19, Otavio Salvador wrote:
>>>>> What it does different here than original linux-dtb alternatives?
>>>>>
>>>> Actually, the default environment present in the barebox mainline for
>>>> the cfa10036 is looking for a kernel named zImage-cfa10036 and DTBs
>>>> named oftree-${DTB_BOARD_NAME} in /boot. So I'm just creating more links
>>>> to the kernel and DTBs. I'm not doing anything differently, I'm just
>>>> creating more links.
>>> I'd patch the default environment so we avoid custom behaviour from
>>> other boards. Do you mind?
>>>
>> Hum, I'm not sure about that, that would mean that we would have a
>> different behaviour between the buildroot generated image and the yocto
>> generated image which is not so great from a customer support point of view.
>> Also oftree is the usual name for dtbs in barebox, I'd like to stick to
>> it. That is just a bunch of links and that part will stay in the
>> crystalfontz specific kernel recipe anyway, does it matter that much ?
> No; but it is code for you to maintain and be sure it keeps working.
> Personally I'd stick to OE-Core standard but it is up to you to
> decide. I am fine with both ways.
>
Sure but my opinion is that is is already quite stupid that yocto does
not use the names generated by the kernel in the first place.
I can make my links pointing to the yocto generated links if you find
that more future proof. I don't believe the names will change that much
anyway and I'd like to ensure maximum compatibility with what is done in
buildroot if possible.
Otavio Salvador - Aug. 23, 2013, 12:20 a.m.
On Thu, Aug 22, 2013 at 8:11 PM, Alexandre Belloni
<alexandre.belloni@free-electrons.com> wrote:
> On 22/08/2013 19:56, Otavio Salvador wrote:
>> On Thu, Aug 22, 2013 at 2:27 PM, Alexandre Belloni
>> <alexandre.belloni@free-electrons.com> wrote:
>>> On 22/08/2013 19:19, Otavio Salvador wrote:
>>>>>> What it does different here than original linux-dtb alternatives?
>>>>>>
>>>>> Actually, the default environment present in the barebox mainline for
>>>>> the cfa10036 is looking for a kernel named zImage-cfa10036 and DTBs
>>>>> named oftree-${DTB_BOARD_NAME} in /boot. So I'm just creating more links
>>>>> to the kernel and DTBs. I'm not doing anything differently, I'm just
>>>>> creating more links.
>>>> I'd patch the default environment so we avoid custom behaviour from
>>>> other boards. Do you mind?
>>>>
>>> Hum, I'm not sure about that, that would mean that we would have a
>>> different behaviour between the buildroot generated image and the yocto
>>> generated image which is not so great from a customer support point of view.
>>> Also oftree is the usual name for dtbs in barebox, I'd like to stick to
>>> it. That is just a bunch of links and that part will stay in the
>>> crystalfontz specific kernel recipe anyway, does it matter that much ?
>> No; but it is code for you to maintain and be sure it keeps working.
>> Personally I'd stick to OE-Core standard but it is up to you to
>> decide. I am fine with both ways.
>>
> Sure but my opinion is that is is already quite stupid that yocto does
> not use the names generated by the kernel in the first place.
> I can make my links pointing to the yocto generated links if you find
> that more future proof. I don't believe the names will change that much
> anyway and I'd like to ensure maximum compatibility with what is done in
> buildroot if possible.

I am fine with it than. :)
Marek Vasut - Aug. 23, 2013, 3:13 a.m.
Dear Alexandre Belloni,

> On 22/08/2013 19:56, Otavio Salvador wrote:
> > On Thu, Aug 22, 2013 at 2:27 PM, Alexandre Belloni
> > 
> > <alexandre.belloni@free-electrons.com> wrote:
> >> On 22/08/2013 19:19, Otavio Salvador wrote:
> >>>>> What it does different here than original linux-dtb alternatives?
> >>>> 
> >>>> Actually, the default environment present in the barebox mainline for
> >>>> the cfa10036 is looking for a kernel named zImage-cfa10036 and DTBs
> >>>> named oftree-${DTB_BOARD_NAME} in /boot. So I'm just creating more
> >>>> links to the kernel and DTBs. I'm not doing anything differently, I'm
> >>>> just creating more links.
> >>> 
> >>> I'd patch the default environment so we avoid custom behaviour from
> >>> other boards. Do you mind?
> >> 
> >> Hum, I'm not sure about that, that would mean that we would have a
> >> different behaviour between the buildroot generated image and the yocto
> >> generated image which is not so great from a customer support point of
> >> view. Also oftree is the usual name for dtbs in barebox, I'd like to
> >> stick to it. That is just a bunch of links and that part will stay in
> >> the crystalfontz specific kernel recipe anyway, does it matter that
> >> much ?
> > 
> > No; but it is code for you to maintain and be sure it keeps working.
> > Personally I'd stick to OE-Core standard but it is up to you to
> > decide. I am fine with both ways.
> 
> Sure but my opinion is that is is already quite stupid that yocto does
> not use the names generated by the kernel in the first place.

The linux kernel does generate files named "oftree-FOO" somehow? How?

Best regards,
Marek Vasut
Simone - Aug. 23, 2013, 9:09 a.m.
Dear all,
for my project, I am using qt embedded 4.8.4 (no X11) generated by Yocto following the procedure indicated on the freescale website.
My application is all based on QML for graphics UI, and since I have problems with rendering speed in animations and listview scrolling, I was thinking to give a try to the new QT5 which (unless I misunderstood) can render the QML scene by opengl. I saw some video on the web about raspberry PI and QML with qt5 and the viewable result is not comparable with the graphics performance i'm obtaining with imx53 and qt4, also if the raspberry pi cpu is much less powerful than imx53)
now:
I do not know where to start to compile QT5, I can not find a tutorial on the web that do work for me (I'm not an expert on yocto, I just did some bitbake following the procedure described in the freescale manual).
Also do not know how to be sure to compile the library with support for OpenGL (and relative Hardware acceleration) of my processor (imx53 family).
My board is based on imx53qsb.
Can someone help?
Thanks in advance
Eric BENARD - Aug. 23, 2013, 9:17 a.m.
Hi Simone,

Le Fri, 23 Aug 2013 11:09:56 +0200,
Simone <cjb.sw.nospam@gmail.com> a écrit :

> Dear all,
> for my project, I am using qt embedded 4.8.4 (no X11) generated by Yocto following the procedure indicated on the freescale website.
> My application is all based on QML for graphics UI, and since I have problems with rendering speed in animations and listview scrolling, I was thinking to give a try to the new QT5 which (unless I misunderstood) can render the QML scene by opengl. I saw some video on the web about raspberry PI and QML with qt5 and the viewable result is not comparable with the graphics performance i'm obtaining with imx53 and qt4, also if the raspberry pi cpu is much less powerful than imx53)
> now:
> I do not know where to start to compile QT5, I can not find a tutorial on the web that do work for me (I'm not an expert on yocto, I just did some bitbake following the procedure described in the freescale manual).
> Also do not know how to be sure to compile the library with support for OpenGL (and relative Hardware acceleration) of my processor (imx53 family).
> My board is based on imx53qsb.

by using meta-fsl-arm and meta-qt5  you should manage to get a QT5
linked against i.MX53's OpenGL ES libraries.

Eric
Simone - Aug. 23, 2013, 9:28 a.m.
Hi Eric, 
Thanks for your reply,
I have to apologize but I'm slowly entering the world of yocto and I have not the slightest idea of ??how to configure it for a new layer. 
you know if there's a generic manual that I can use?
Thanks so much
 



Il giorno 23/ago/2013, alle ore 11:17, Eric Bénard <eric@eukrea.com> ha scritto:

> Hi Simone,
> 
> Le Fri, 23 Aug 2013 11:09:56 +0200,
> Simone <cjb.sw.nospam@gmail.com> a écrit :
> 
>> Dear all,
>> for my project, I am using qt embedded 4.8.4 (no X11) generated by Yocto following the procedure indicated on the freescale website.
>> My application is all based on QML for graphics UI, and since I have problems with rendering speed in animations and listview scrolling, I was thinking to give a try to the new QT5 which (unless I misunderstood) can render the QML scene by opengl. I saw some video on the web about raspberry PI and QML with qt5 and the viewable result is not comparable with the graphics performance i'm obtaining with imx53 and qt4, also if the raspberry pi cpu is much less powerful than imx53)
>> now:
>> I do not know where to start to compile QT5, I can not find a tutorial on the web that do work for me (I'm not an expert on yocto, I just did some bitbake following the procedure described in the freescale manual).
>> Also do not know how to be sure to compile the library with support for OpenGL (and relative Hardware acceleration) of my processor (imx53 family).
>> My board is based on imx53qsb.
> 
> by using meta-fsl-arm and meta-qt5  you should manage to get a QT5
> linked against i.MX53's OpenGL ES libraries.
> 
> Eric
Eric BENARD - Aug. 23, 2013, 9:40 a.m.
Hi Simone,

Le Fri, 23 Aug 2013 11:28:26 +0200,
Simone <cjb.sw.nospam@gmail.com> a écrit :
> I have to apologize but I'm slowly entering the world of yocto and I have not the slightest idea of ??how to configure it for a new layer. 
> you know if there's a generic manual that I can use?

meta-qt5 can be found here :
https://github.com/meta-qt5/meta-qt5

simply fetch it at the same directory level where you will find
meta-fsl-arm, checkout the version of oe-core you are using, and add it
to bblayer.conf (the paths depend on the scripts you are using to setup
your build system).
http://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#enabling-your-layer

For the manual you can find Yocto's one here :
http://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html

Best regards
Eric
Simone - Aug. 23, 2013, 9:56 a.m.
Hello Eric,
I cloned the meta-qt5 from git.
I've added the meta-qt5 in bblayers.conf.

Now how i can build the libraries?


Il giorno 23/ago/2013, alle ore 11:40, Eric Bénard <eric@eukrea.com> ha scritto:

> Hi Simone,
> 
> Le Fri, 23 Aug 2013 11:28:26 +0200,
> Simone <cjb.sw.nospam@gmail.com> a écrit :
>> I have to apologize but I'm slowly entering the world of yocto and I have not the slightest idea of ??how to configure it for a new layer. 
>> you know if there's a generic manual that I can use?
> 
> meta-qt5 can be found here :
> https://github.com/meta-qt5/meta-qt5
> 
> simply fetch it at the same directory level where you will find
> meta-fsl-arm, checkout the version of oe-core you are using, and add it
> to bblayer.conf (the paths depend on the scripts you are using to setup
> your build system).
> http://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#enabling-your-layer
> 
> For the manual you can find Yocto's one here :
> http://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html
> 
> Best regards
> Eric
Abhijit Potnis - Aug. 23, 2013, 10:08 a.m.
Hello Simone,

I hope you are on the latest meta-fsl-arm master,
as qt-layer is needed to build qt5 on mx5

http://git.yoctoproject.org/cgit/cgit.cgi/meta-fsl-arm/tree/qt5-layer




On Fri, Aug 23, 2013 at 3:26 PM, Simone <cjb.sw.nospam@gmail.com> wrote:

> Hello Eric,
> I cloned the meta-qt5 from git.
> I've added the meta-qt5 in bblayers.conf.
>
> Now how i can build the libraries?
>
>
> Il giorno 23/ago/2013, alle ore 11:40, Eric Bénard <eric@eukrea.com> ha
> scritto:
>
> > Hi Simone,
> >
> > Le Fri, 23 Aug 2013 11:28:26 +0200,
> > Simone <cjb.sw.nospam@gmail.com> a écrit :
> >> I have to apologize but I'm slowly entering the world of yocto and I
> have not the slightest idea of how to configure it for a new layer.
> >> you know if there's a generic manual that I can use?
> >
> > meta-qt5 can be found here :
> > https://github.com/meta-qt5/meta-qt5
> >
> > simply fetch it at the same directory level where you will find
> > meta-fsl-arm, checkout the version of oe-core you are using, and add it
> > to bblayer.conf (the paths depend on the scripts you are using to setup
> > your build system).
> >
> http://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#enabling-your-layer
> >
> > For the manual you can find Yocto's one here :
> > http://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html
> >
> > Best regards
> > Eric
> _______________________________________________
> meta-freescale mailing list
> meta-freescale@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-freescale
>
Simone - Aug. 23, 2013, 10:15 a.m.
Hello Abhijit,
I don't know, how i can check/change it?



Il giorno 23/ago/2013, alle ore 12:08, Abhijit Potnis <abhijitpotnis@gmail.com> ha scritto:

> Hello Simone,
> 
> I hope you are on the latest meta-fsl-arm master,
> as qt-layer is needed to build qt5 on mx5
> 
> http://git.yoctoproject.org/cgit/cgit.cgi/meta-fsl-arm/tree/qt5-layer
> 
> 
> 
> 
> On Fri, Aug 23, 2013 at 3:26 PM, Simone <cjb.sw.nospam@gmail.com> wrote:
>> Hello Eric,
>> I cloned the meta-qt5 from git.
>> I've added the meta-qt5 in bblayers.conf.
>> 
>> Now how i can build the libraries?
>> 
>> 
>> Il giorno 23/ago/2013, alle ore 11:40, Eric Bénard <eric@eukrea.com> ha scritto:
>> 
>> > Hi Simone,
>> >
>> > Le Fri, 23 Aug 2013 11:28:26 +0200,
>> > Simone <cjb.sw.nospam@gmail.com> a écrit :
>> >> I have to apologize but I'm slowly entering the world of yocto and I have not the slightest idea of how to configure it for a new layer.
>> >> you know if there's a generic manual that I can use?
>> >
>> > meta-qt5 can be found here :
>> > https://github.com/meta-qt5/meta-qt5
>> >
>> > simply fetch it at the same directory level where you will find
>> > meta-fsl-arm, checkout the version of oe-core you are using, and add it
>> > to bblayer.conf (the paths depend on the scripts you are using to setup
>> > your build system).
>> > http://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#enabling-your-layer
>> >
>> > For the manual you can find Yocto's one here :
>> > http://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html
>> >
>> > Best regards
>> > Eric
>> _______________________________________________
>> meta-freescale mailing list
>> meta-freescale@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/meta-freescale
>
Abhijit Potnis - Aug. 23, 2013, 10:19 a.m.
Under your project folder, *cd* into *meta-fsl-arm*
and try finding
*qt5-layer<http://git.yoctoproject.org/cgit/cgit.cgi/meta-fsl-arm/tree/qt5-layer>
*named folder. That should confirm that you are on the right way to build
qt5.

Go ahead and build qtbase package, lets see what happnes.

-Abhijit


On Fri, Aug 23, 2013 at 3:45 PM, Simone <cjb.sw.nospam@gmail.com> wrote:

> Hello Abhijit,
> I don't know, how i can check/change it?
>
>
>
> Il giorno 23/ago/2013, alle ore 12:08, Abhijit Potnis <
> abhijitpotnis@gmail.com> ha scritto:
>
> Hello Simone,
>
> I hope you are on the latest meta-fsl-arm master,
> as qt-layer is needed to build qt5 on mx5
>
> http://git.yoctoproject.org/cgit/cgit.cgi/meta-fsl-arm/tree/qt5-layer
>
>
>
>
> On Fri, Aug 23, 2013 at 3:26 PM, Simone <cjb.sw.nospam@gmail.com> wrote:
>
>> Hello Eric,
>> I cloned the meta-qt5 from git.
>> I've added the meta-qt5 in bblayers.conf.
>>
>> Now how i can build the libraries?
>>
>>
>> Il giorno 23/ago/2013, alle ore 11:40, Eric Bénard <eric@eukrea.com> ha
>> scritto:
>>
>> > Hi Simone,
>> >
>> > Le Fri, 23 Aug 2013 11:28:26 +0200,
>> > Simone <cjb.sw.nospam@gmail.com> a écrit :
>> >> I have to apologize but I'm slowly entering the world of yocto and I
>> have not the slightest idea of how to configure it for a new layer.
>> >> you know if there's a generic manual that I can use?
>> >
>> > meta-qt5 can be found here :
>> > https://github.com/meta-qt5/meta-qt5
>> >
>> > simply fetch it at the same directory level where you will find
>> > meta-fsl-arm, checkout the version of oe-core you are using, and add it
>> > to bblayer.conf (the paths depend on the scripts you are using to setup
>> > your build system).
>> >
>> http://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#enabling-your-layer
>> >
>> > For the manual you can find Yocto's one here :
>> > http://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html
>> >
>> > Best regards
>> > Eric
>> _______________________________________________
>> meta-freescale mailing list
>> meta-freescale@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/meta-freescale
>>
>
>
Simone - Aug. 23, 2013, 10:26 a.m.
Dear Abhijit

No, I can?t see the qt5-layer in meta-fsl-arm?.

 

For the configuration, I followed the tutorial at:

 <https://community.freescale.com/docs/DOC-95096>
https://community.freescale.com/docs/DOC-95096

 

Thank you for your time.

 

 

Da: Abhijit Potnis [mailto:abhijitpotnis@gmail.com] 
Inviato: venerdì 23 agosto 2013 12:20
A: Simone
Cc: Eric Bénard; meta-freescale@yoctoproject.org
Oggetto: Re: [meta-freescale] Qt5 with opengl hw acceleration on imx53

 

Under your project folder, cd into meta-fsl-arm

and try finding qt5-layer
<http://git.yoctoproject.org/cgit/cgit.cgi/meta-fsl-arm/tree/qt5-layer>
named folder. That should confirm that you are on the right way to build
qt5.

Go ahead and build qtbase package, lets see what happnes.

-Abhijit

 

On Fri, Aug 23, 2013 at 3:45 PM, Simone <cjb.sw.nospam@gmail.com
<mailto:cjb.sw.nospam@gmail.com> > wrote:

Hello Abhijit,

I don't know, how i can check/change it?




Il giorno 23/ago/2013, alle ore 12:08, Abhijit Potnis
<abhijitpotnis@gmail.com <mailto:abhijitpotnis@gmail.com> > ha scritto:

Hello Simone,

I hope you are on the latest meta-fsl-arm master,
as qt-layer is needed to build qt5 on mx5

http://git.yoctoproject.org/cgit/cgit.cgi/meta-fsl-arm/tree/qt5-layer



 

On Fri, Aug 23, 2013 at 3:26 PM, Simone <cjb.sw.nospam@gmail.com
<mailto:cjb.sw.nospam@gmail.com> > wrote:

Hello Eric,
I cloned the meta-qt5 from git.
I've added the meta-qt5 in bblayers.conf.

Now how i can build the libraries?


Il giorno 23/ago/2013, alle ore 11:40, Eric Bénard <eric@eukrea.com
<mailto:eric@eukrea.com> > ha scritto:


> Hi Simone,
>
> Le Fri, 23 Aug 2013 11:28:26 +0200,
> Simone <cjb.sw.nospam@gmail.com <mailto:cjb.sw.nospam@gmail.com> > a écrit
:
>> I have to apologize but I'm slowly entering the world of yocto and I have
not the slightest idea of how to configure it for a new layer.
>> you know if there's a generic manual that I can use?
>
> meta-qt5 can be found here :
> https://github.com/meta-qt5/meta-qt5
>
> simply fetch it at the same directory level where you will find
> meta-fsl-arm, checkout the version of oe-core you are using, and add it
> to bblayer.conf (the paths depend on the scripts you are using to setup
> your build system).
>
http://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#enabli
ng-your-layer
>
> For the manual you can find Yocto's one here :
> http://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html
>
> Best regards
> Eric
Abhijit Potnis - Aug. 23, 2013, 10:41 a.m.
Hello Simone,

The repo init step in the document does say that you are based on the dylan
branch.
What you can do is clone the git://git.yoctoproject.org/meta-fsl-arm, and
copy the qt5-layer folder from the clone to your
project folder's meta-fsl-arm.

Then edit the meta-fsl-arm/conf/layer.conf* *to add qt5-layer to the
BBFILES variable as below

# We have a packages directory, add to BBFILES
BBFILES += "${LAYERDIR}/recipes-*/*/*.bb \
*            **${LAYERDIR}/qt5-layer/recipes-*/*/*.bbappend \*

            ${LAYERDIR}/recipes-*/*/*.bbappend"

then start building qtbase


On Fri, Aug 23, 2013 at 3:56 PM, Simone <cjb.sw.nospam@gmail.com> wrote:

> Dear Abhijit****
>
> No, I can’t see the qt5-layer in meta-fsl-arm….****
>
> ** **
>
> For the configuration, I followed the tutorial at:****
>
> https://community.freescale.com/docs/DOC-95096****
>
> ** **
>
> Thank you for your time.****
>
> ** **
>
> ** **
>
> *Da:* Abhijit Potnis [mailto:abhijitpotnis@gmail.com]
> *Inviato:* venerdì 23 agosto 2013 12:20
> *A:* Simone
> *Cc:* Eric Bénard; meta-freescale@yoctoproject.org
> *Oggetto:* Re: [meta-freescale] Qt5 with opengl hw acceleration on imx53**
> **
>
> ** **
>
> Under your project folder, *cd* into *meta-fsl-arm*****
>
> and try finding *qt5-layer<http://git.yoctoproject.org/cgit/cgit.cgi/meta-fsl-arm/tree/qt5-layer>
> *named folder. That should confirm that you are on the right way to build
> qt5.****
>
> Go ahead and build qtbase package, lets see what happnes.****
>
> -Abhijit****
>
> ** **
>
> On Fri, Aug 23, 2013 at 3:45 PM, Simone <cjb.sw.nospam@gmail.com> wrote:**
> **
>
> Hello Abhijit,****
>
> I don't know, how i can check/change it?
>
> ****
>
>
> Il giorno 23/ago/2013, alle ore 12:08, Abhijit Potnis <
> abhijitpotnis@gmail.com> ha scritto:****
>
> Hello Simone,****
>
> I hope you are on the latest meta-fsl-arm master,
> as qt-layer is needed to build qt5 on mx5
>
> http://git.yoctoproject.org/cgit/cgit.cgi/meta-fsl-arm/tree/qt5-layer
>
> ****
>
> ** **
>
> On Fri, Aug 23, 2013 at 3:26 PM, Simone <cjb.sw.nospam@gmail.com> wrote:**
> **
>
> Hello Eric,
> I cloned the meta-qt5 from git.
> I've added the meta-qt5 in bblayers.conf.
>
> Now how i can build the libraries?
>
>
> Il giorno 23/ago/2013, alle ore 11:40, Eric Bénard <eric@eukrea.com> ha
> scritto:****
>
>
> > Hi Simone,
> >
> > Le Fri, 23 Aug 2013 11:28:26 +0200,
> > Simone <cjb.sw.nospam@gmail.com> a écrit :
> >> I have to apologize but I'm slowly entering the world of yocto and I
> have not the slightest idea of how to configure it for a new layer.
> >> you know if there's a generic manual that I can use?
> >
> > meta-qt5 can be found here :
> > https://github.com/meta-qt5/meta-qt5
> >
> > simply fetch it at the same directory level where you will find
> > meta-fsl-arm, checkout the version of oe-core you are using, and add it
> > to bblayer.conf (the paths depend on the scripts you are using to setup
> > your build system).
> >
> http://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#enabling-your-layer
> >
> > For the manual you can find Yocto's one here :
> > http://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html
> >
> > Best regards
> > Eric
> _______________________________________________
> meta-freescale mailing list
> meta-freescale@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-freescale****
>
> ** **
>
> ** **
>
Simone - Aug. 23, 2013, 10:50 a.m.
Hello Abhijit,

I re-done the repo-init with master branch (I don?t know if it is correct,
but now in the meta-fsl-arm I have the qt5-layer).

 

Now I launched bitbake qtbase and it is compiling something.. (seems it will
take long time)

Let?s see..

 

I will reply when I have news..

Thanks so much

 

 

 

Da: Simone [mailto:cjb.sw.nospam@gmail.com] 
Inviato: venerdì 23 agosto 2013 12:27
A: 'Abhijit Potnis'
Cc: 'Eric Bénard'; 'meta-freescale@yoctoproject.org'
Oggetto: R: [meta-freescale] Qt5 with opengl hw acceleration on imx53
Priorità: Alta

 

Dear Abhijit

No, I can?t see the qt5-layer in meta-fsl-arm?.

 

For the configuration, I followed the tutorial at:

 <https://community.freescale.com/docs/DOC-95096>
https://community.freescale.com/docs/DOC-95096

 

Thank you for your time.

 

 

Da: Abhijit Potnis [mailto:abhijitpotnis@gmail.com] 
Inviato: venerdì 23 agosto 2013 12:20
A: Simone
Cc: Eric Bénard; meta-freescale@yoctoproject.org
<mailto:meta-freescale@yoctoproject.org> 
Oggetto: Re: [meta-freescale] Qt5 with opengl hw acceleration on imx53

 

Under your project folder, cd into meta-fsl-arm

and try finding qt5-layer
<http://git.yoctoproject.org/cgit/cgit.cgi/meta-fsl-arm/tree/qt5-layer>
named folder. That should confirm that you are on the right way to build
qt5.

Go ahead and build qtbase package, lets see what happnes.

-Abhijit

 

On Fri, Aug 23, 2013 at 3:45 PM, Simone <cjb.sw.nospam@gmail.com
<mailto:cjb.sw.nospam@gmail.com> > wrote:

Hello Abhijit,

I don't know, how i can check/change it?


Il giorno 23/ago/2013, alle ore 12:08, Abhijit Potnis
<abhijitpotnis@gmail.com <mailto:abhijitpotnis@gmail.com> > ha scritto:

Hello Simone,

I hope you are on the latest meta-fsl-arm master,
as qt-layer is needed to build qt5 on mx5

http://git.yoctoproject.org/cgit/cgit.cgi/meta-fsl-arm/tree/qt5-layer

 

On Fri, Aug 23, 2013 at 3:26 PM, Simone <cjb.sw.nospam@gmail.com
<mailto:cjb.sw.nospam@gmail.com> > wrote:

Hello Eric,
I cloned the meta-qt5 from git.
I've added the meta-qt5 in bblayers.conf.

Now how i can build the libraries?


Il giorno 23/ago/2013, alle ore 11:40, Eric Bénard <eric@eukrea.com
<mailto:eric@eukrea.com> > ha scritto:


> Hi Simone,
>
> Le Fri, 23 Aug 2013 11:28:26 +0200,
> Simone <cjb.sw.nospam@gmail.com <mailto:cjb.sw.nospam@gmail.com> > a écrit
:
>> I have to apologize but I'm slowly entering the world of yocto and I have
not the slightest idea of how to configure it for a new layer.
>> you know if there's a generic manual that I can use?
>
> meta-qt5 can be found here :
> https://github.com/meta-qt5/meta-qt5
>
> simply fetch it at the same directory level where you will find
> meta-fsl-arm, checkout the version of oe-core you are using, and add it
> to bblayer.conf (the paths depend on the scripts you are using to setup
> your build system).
>
http://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#enabli
ng-your-layer
>
> For the manual you can find Yocto's one here :
> http://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html
>
> Best regards
> Eric
Alexandre Belloni - Aug. 23, 2013, 11:06 a.m.
On 23/08/2013 05:13, Marek Vasut wrote:
> Dear Alexandre Belloni,
>
>> On 22/08/2013 19:56, Otavio Salvador wrote:
>>> On Thu, Aug 22, 2013 at 2:27 PM, Alexandre Belloni
>>>
>>> <alexandre.belloni@free-electrons.com> wrote:
>>>> On 22/08/2013 19:19, Otavio Salvador wrote:
>>>>>>> What it does different here than original linux-dtb alternatives?
>>>>>> Actually, the default environment present in the barebox mainline for
>>>>>> the cfa10036 is looking for a kernel named zImage-cfa10036 and DTBs
>>>>>> named oftree-${DTB_BOARD_NAME} in /boot. So I'm just creating more
>>>>>> links to the kernel and DTBs. I'm not doing anything differently, I'm
>>>>>> just creating more links.
>>>>> I'd patch the default environment so we avoid custom behaviour from
>>>>> other boards. Do you mind?
>>>> Hum, I'm not sure about that, that would mean that we would have a
>>>> different behaviour between the buildroot generated image and the yocto
>>>> generated image which is not so great from a customer support point of
>>>> view. Also oftree is the usual name for dtbs in barebox, I'd like to
>>>> stick to it. That is just a bunch of links and that part will stay in
>>>> the crystalfontz specific kernel recipe anyway, does it matter that
>>>> much ?
>>> No; but it is code for you to maintain and be sure it keeps working.
>>> Personally I'd stick to OE-Core standard but it is up to you to
>>> decide. I am fine with both ways.
>> Sure but my opinion is that is is already quite stupid that yocto does
>> not use the names generated by the kernel in the first place.
> The linux kernel does generate files named "oftree-FOO" somehow? How?
No, what I meant is that yocto is using
devicetree-zImage-imx28-cfa10036.dtb instead of imx28-cfa10036.dtb for
example when installing devicetrees in the image.
Marek Vasut - Aug. 23, 2013, 11:25 a.m.
Dear Alexandre Belloni,

> On 23/08/2013 05:13, Marek Vasut wrote:
> > Dear Alexandre Belloni,
> > 
> >> On 22/08/2013 19:56, Otavio Salvador wrote:
> >>> On Thu, Aug 22, 2013 at 2:27 PM, Alexandre Belloni
> >>> 
> >>> <alexandre.belloni@free-electrons.com> wrote:
> >>>> On 22/08/2013 19:19, Otavio Salvador wrote:
> >>>>>>> What it does different here than original linux-dtb alternatives?
> >>>>>> 
> >>>>>> Actually, the default environment present in the barebox mainline
> >>>>>> for the cfa10036 is looking for a kernel named zImage-cfa10036 and
> >>>>>> DTBs named oftree-${DTB_BOARD_NAME} in /boot. So I'm just creating
> >>>>>> more links to the kernel and DTBs. I'm not doing anything
> >>>>>> differently, I'm just creating more links.
> >>>>> 
> >>>>> I'd patch the default environment so we avoid custom behaviour from
> >>>>> other boards. Do you mind?
> >>>> 
> >>>> Hum, I'm not sure about that, that would mean that we would have a
> >>>> different behaviour between the buildroot generated image and the
> >>>> yocto generated image which is not so great from a customer support
> >>>> point of view. Also oftree is the usual name for dtbs in barebox, I'd
> >>>> like to stick to it. That is just a bunch of links and that part will
> >>>> stay in the crystalfontz specific kernel recipe anyway, does it
> >>>> matter that much ?
> >>> 
> >>> No; but it is code for you to maintain and be sure it keeps working.
> >>> Personally I'd stick to OE-Core standard but it is up to you to
> >>> decide. I am fine with both ways.
> >> 
> >> Sure but my opinion is that is is already quite stupid that yocto does
> >> not use the names generated by the kernel in the first place.
> > 
> > The linux kernel does generate files named "oftree-FOO" somehow? How?
> 
> No, what I meant is that yocto is using
> devicetree-zImage-imx28-cfa10036.dtb instead of imx28-cfa10036.dtb for
> example when installing devicetrees in the image.

Ah yes, you're right, the way Yocto does it is rather confusing. But it's not my 
call to comemnt on this.

Best regards,
Marek Vasut
Simone - Aug. 23, 2013, 12:06 p.m.
Hello Abhijit,

The bitbake is currently doing these steps:

 

0: qtbase-native-5.1.0-r0 do_fetch (pid 17834)

1: qtbase-5.1.0-r0 do_fetch (pid 17835)

 

And it seems will take some time.

Anyway, in the meantime I?m thinking about how to build the image after the
current bitbake is ok.

What image I have to bitbake? For testing with qt4e in the past I builded
the qt4e-demo-image. There is something similar for Qt5 or I have to
modify/create another?

Have I to include/modify something in the configuration files?

Qt5 needs X server? There is no QWS server on Qt5 right?

What about the toolchain? How I can make it?

Thank you so much

Simone

 

 

Da: Abhijit Potnis [mailto:abhijitpotnis@gmail.com] 
Inviato: venerdì 23 agosto 2013 12:42
A: Simone
Cc: Eric Bénard; meta-freescale@yoctoproject.org
Oggetto: Re: [meta-freescale] Qt5 with opengl hw acceleration on imx53

 

Hello Simone,

The repo init step in the document does say that you are based on the dylan
branch.

What you can do is clone the git://git.yoctoproject.org/meta-fsl-arm, and
copy the qt5-layer folder from the clone to your
project folder's meta-fsl-arm.

Then edit the meta-fsl-arm/conf/layer.conf to add qt5-layer to the BBFILES
variable as below

 

# We have a packages directory, add to BBFILES
BBFILES += "${LAYERDIR}/recipes-*/*/*.bb \
            ${LAYERDIR}/qt5-layer/recipes-*/*/*.bbappend \


 
            ${LAYERDIR}/recipes-*/*/*.bbappend"

then start building qtbase

 

On Fri, Aug 23, 2013 at 3:56 PM, Simone <cjb.sw.nospam@gmail.com
<mailto:cjb.sw.nospam@gmail.com> > wrote:

Dear Abhijit

No, I can?t see the qt5-layer in meta-fsl-arm?.

 

For the configuration, I followed the tutorial at:

 <https://community.freescale.com/docs/DOC-95096>
https://community.freescale.com/docs/DOC-95096

 

Thank you for your time.

 

 

Da: Abhijit Potnis [mailto:abhijitpotnis@gmail.com
<mailto:abhijitpotnis@gmail.com> ] 
Inviato: venerdì 23 agosto 2013 12:20
A: Simone
Cc: Eric Bénard; meta-freescale@yoctoproject.org
<mailto:meta-freescale@yoctoproject.org> 
Oggetto: Re: [meta-freescale] Qt5 with opengl hw acceleration on imx53

 

Under your project folder, cd into meta-fsl-arm

and try finding qt5-layer
<http://git.yoctoproject.org/cgit/cgit.cgi/meta-fsl-arm/tree/qt5-layer>
named folder. That should confirm that you are on the right way to build
qt5.

Go ahead and build qtbase package, lets see what happnes.

-Abhijit

 

On Fri, Aug 23, 2013 at 3:45 PM, Simone <cjb.sw.nospam@gmail.com
<mailto:cjb.sw.nospam@gmail.com> > wrote:

Hello Abhijit,

I don't know, how i can check/change it?


Il giorno 23/ago/2013, alle ore 12:08, Abhijit Potnis
<abhijitpotnis@gmail.com <mailto:abhijitpotnis@gmail.com> > ha scritto:

Hello Simone,

I hope you are on the latest meta-fsl-arm master,
as qt-layer is needed to build qt5 on mx5

http://git.yoctoproject.org/cgit/cgit.cgi/meta-fsl-arm/tree/qt5-layer

 

On Fri, Aug 23, 2013 at 3:26 PM, Simone <cjb.sw.nospam@gmail.com
<mailto:cjb.sw.nospam@gmail.com> > wrote:

Hello Eric,
I cloned the meta-qt5 from git.
I've added the meta-qt5 in bblayers.conf.

Now how i can build the libraries?


Il giorno 23/ago/2013, alle ore 11:40, Eric Bénard <eric@eukrea.com
<mailto:eric@eukrea.com> > ha scritto:


> Hi Simone,
>
> Le Fri, 23 Aug 2013 11:28:26 +0200,
> Simone <cjb.sw.nospam@gmail.com <mailto:cjb.sw.nospam@gmail.com> > a écrit
:
>> I have to apologize but I'm slowly entering the world of yocto and I have
not the slightest idea of how to configure it for a new layer.
>> you know if there's a generic manual that I can use?
>
> meta-qt5 can be found here :
> https://github.com/meta-qt5/meta-qt5
>
> simply fetch it at the same directory level where you will find
> meta-fsl-arm, checkout the version of oe-core you are using, and add it
> to bblayer.conf (the paths depend on the scripts you are using to setup
> your build system).
>
http://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#enabli
ng-your-layer
>
> For the manual you can find Yocto's one here :
> http://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html
>
> Best regards
> Eric
Simone - Aug. 23, 2013, 12:52 p.m.
Hello,

the bitbake qtbase finished with success.

Now how I can make a demo image with some demo application in qt5 like the
fsl-image-gui for qt4?

 

 

 

Da: Abhijit Potnis [mailto:abhijitpotnis@gmail.com] 
Inviato: venerdì 23 agosto 2013 12:42
A: Simone
Cc: Eric Bénard; meta-freescale@yoctoproject.org
Oggetto: Re: [meta-freescale] Qt5 with opengl hw acceleration on imx53

 

Hello Simone,

The repo init step in the document does say that you are based on the dylan
branch.

What you can do is clone the git://git.yoctoproject.org/meta-fsl-arm, and
copy the qt5-layer folder from the clone to your
project folder's meta-fsl-arm.

Then edit the meta-fsl-arm/conf/layer.conf to add qt5-layer to the BBFILES
variable as below

 

# We have a packages directory, add to BBFILES
BBFILES += "${LAYERDIR}/recipes-*/*/*.bb \
            ${LAYERDIR}/qt5-layer/recipes-*/*/*.bbappend \


 
            ${LAYERDIR}/recipes-*/*/*.bbappend"

then start building qtbase

 

On Fri, Aug 23, 2013 at 3:56 PM, Simone <cjb.sw.nospam@gmail.com
<mailto:cjb.sw.nospam@gmail.com> > wrote:

Dear Abhijit

No, I can?t see the qt5-layer in meta-fsl-arm?.

 

For the configuration, I followed the tutorial at:

 <https://community.freescale.com/docs/DOC-95096>
https://community.freescale.com/docs/DOC-95096

 

Thank you for your time.

 

 

Da: Abhijit Potnis [mailto:abhijitpotnis@gmail.com
<mailto:abhijitpotnis@gmail.com> ] 
Inviato: venerdì 23 agosto 2013 12:20
A: Simone
Cc: Eric Bénard; meta-freescale@yoctoproject.org
<mailto:meta-freescale@yoctoproject.org> 
Oggetto: Re: [meta-freescale] Qt5 with opengl hw acceleration on imx53

 

Under your project folder, cd into meta-fsl-arm

and try finding qt5-layer
<http://git.yoctoproject.org/cgit/cgit.cgi/meta-fsl-arm/tree/qt5-layer>
named folder. That should confirm that you are on the right way to build
qt5.

Go ahead and build qtbase package, lets see what happnes.

-Abhijit

 

On Fri, Aug 23, 2013 at 3:45 PM, Simone <cjb.sw.nospam@gmail.com
<mailto:cjb.sw.nospam@gmail.com> > wrote:

Hello Abhijit,

I don't know, how i can check/change it?


Il giorno 23/ago/2013, alle ore 12:08, Abhijit Potnis
<abhijitpotnis@gmail.com <mailto:abhijitpotnis@gmail.com> > ha scritto:

Hello Simone,

I hope you are on the latest meta-fsl-arm master,
as qt-layer is needed to build qt5 on mx5

http://git.yoctoproject.org/cgit/cgit.cgi/meta-fsl-arm/tree/qt5-layer

 

On Fri, Aug 23, 2013 at 3:26 PM, Simone <cjb.sw.nospam@gmail.com
<mailto:cjb.sw.nospam@gmail.com> > wrote:

Hello Eric,
I cloned the meta-qt5 from git.
I've added the meta-qt5 in bblayers.conf.

Now how i can build the libraries?


Il giorno 23/ago/2013, alle ore 11:40, Eric Bénard <eric@eukrea.com
<mailto:eric@eukrea.com> > ha scritto:


> Hi Simone,
>
> Le Fri, 23 Aug 2013 11:28:26 +0200,
> Simone <cjb.sw.nospam@gmail.com <mailto:cjb.sw.nospam@gmail.com> > a écrit
:
>> I have to apologize but I'm slowly entering the world of yocto and I have
not the slightest idea of how to configure it for a new layer.
>> you know if there's a generic manual that I can use?
>
> meta-qt5 can be found here :
> https://github.com/meta-qt5/meta-qt5
>
> simply fetch it at the same directory level where you will find
> meta-fsl-arm, checkout the version of oe-core you are using, and add it
> to bblayer.conf (the paths depend on the scripts you are using to setup
> your build system).
>
http://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#enabli
ng-your-layer
>
> For the manual you can find Yocto's one here :
> http://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html
>
> Best regards
> Eric

Patch

diff --git a/recipes-kernel/linux/linux-cfa-3.10/defconfig b/recipes-kernel/linux/linux-cfa-3.10/defconfig
new file mode 100644
index 0000000..ab8732e
--- /dev/null
+++ b/recipes-kernel/linux/linux-cfa-3.10/defconfig
@@ -0,0 +1,177 @@ 
+CONFIG_SYSVIPC=y
+CONFIG_NO_HZ=y
+CONFIG_HIGH_RES_TIMERS=y
+CONFIG_TASKSTATS=y
+CONFIG_TASK_DELAY_ACCT=y
+CONFIG_TASK_XACCT=y
+CONFIG_TASK_IO_ACCOUNTING=y
+CONFIG_IKCONFIG=y
+CONFIG_IKCONFIG_PROC=y
+# CONFIG_UTS_NS is not set
+# CONFIG_IPC_NS is not set
+# CONFIG_PID_NS is not set
+# CONFIG_NET_NS is not set
+CONFIG_PERF_EVENTS=y
+# CONFIG_COMPAT_BRK is not set
+CONFIG_MODULES=y
+CONFIG_MODULE_FORCE_LOAD=y
+CONFIG_MODULE_UNLOAD=y
+CONFIG_MODULE_FORCE_UNLOAD=y
+CONFIG_MODVERSIONS=y
+CONFIG_BLK_DEV_INTEGRITY=y
+# CONFIG_IOSCHED_DEADLINE is not set
+# CONFIG_IOSCHED_CFQ is not set
+# CONFIG_ARCH_MULTI_V7 is not set
+CONFIG_GPIO_PCA953X=y
+CONFIG_ARCH_MXS=y
+# CONFIG_ARM_THUMB is not set
+CONFIG_PREEMPT_VOLUNTARY=y
+CONFIG_AEABI=y
+# CONFIG_COMPACTION is not set
+CONFIG_DEFAULT_MMAP_MIN_ADDR=65536
+CONFIG_FPE_NWFPE=y
+CONFIG_NET=y
+CONFIG_PACKET=y
+CONFIG_UNIX=y
+CONFIG_INET=y
+CONFIG_IP_PNP=y
+CONFIG_IP_PNP_DHCP=y
+CONFIG_SYN_COOKIES=y
+# CONFIG_INET_XFRM_MODE_TRANSPORT is not set
+# CONFIG_INET_XFRM_MODE_TUNNEL is not set
+# CONFIG_INET_XFRM_MODE_BEET is not set
+# CONFIG_INET_LRO is not set
+# CONFIG_INET_DIAG is not set
+# CONFIG_IPV6 is not set
+CONFIG_DEVTMPFS=y
+CONFIG_DEVTMPFS_MOUNT=y
+# CONFIG_FIRMWARE_IN_KERNEL is not set
+CONFIG_CMA=y
+# CONFIG_BLK_DEV is not set
+CONFIG_CFAFIQ=y
+CONFIG_SCSI=y
+CONFIG_BLK_DEV_SD=y
+CONFIG_NETDEVICES=y
+CONFIG_MII=y
+CONFIG_ENC28J60=y
+# CONFIG_WLAN is not set
+# CONFIG_INPUT_MOUSEDEV_PSAUX is not set
+CONFIG_INPUT_EVDEV=y
+CONFIG_INPUT_EVBUG=y
+# CONFIG_KEYBOARD_ATKBD is not set
+CONFIG_KEYBOARD_GPIO=y
+# CONFIG_INPUT_MOUSE is not set
+CONFIG_INPUT_MISC=y
+CONFIG_INPUT_GPIO_ROTARY_ENCODER=y
+# CONFIG_SERIO is not set
+CONFIG_VT_HW_CONSOLE_BINDING=y
+CONFIG_DEVPTS_MULTIPLE_INSTANCES=y
+# CONFIG_LEGACY_PTYS is not set
+# CONFIG_DEVKMEM is not set
+CONFIG_SERIAL_AMBA_PL011=y
+CONFIG_SERIAL_AMBA_PL011_CONSOLE=y
+# CONFIG_HW_RANDOM is not set
+CONFIG_I2C=y
+# CONFIG_I2C_COMPAT is not set
+CONFIG_I2C_CHARDEV=y
+CONFIG_I2C_MUX=y
+CONFIG_I2C_MUX_GPIO=y
+CONFIG_I2C_GPIO=y
+CONFIG_I2C_MXS=y
+CONFIG_SPI=y
+CONFIG_SPI_GPIO=y
+CONFIG_SPI_MXS=y
+CONFIG_SPI_SPIDEV=y
+CONFIG_GPIO_SYSFS=y
+CONFIG_GPIO_PCA953X_IRQ=y
+CONFIG_GPIO_74X164=y
+CONFIG_W1=y
+CONFIG_W1_MASTER_GPIO=y
+CONFIG_W1_SLAVE_THERM=y
+CONFIG_SENSORS_IIO_HWMON=y
+CONFIG_SENSORS_MXS_CPU=y
+CONFIG_REGULATOR=y
+CONFIG_REGULATOR_FIXED_VOLTAGE=y
+CONFIG_FB=y
+CONFIG_FB_MXS=y
+CONFIG_BACKLIGHT_LCD_SUPPORT=y
+CONFIG_LCD_CLASS_DEVICE=y
+CONFIG_LCD_HX8357=y
+CONFIG_BACKLIGHT_CLASS_DEVICE=y
+# CONFIG_BACKLIGHT_GENERIC is not set
+CONFIG_BACKLIGHT_PWM=y
+CONFIG_FB_SSD1307=y
+CONFIG_SOUND=y
+CONFIG_SND=y
+CONFIG_SND_SOC=y
+CONFIG_SND_MXS_SOC=y
+CONFIG_SND_SOC_MXS_SGTL5000=y
+CONFIG_HID_LOGITECH_DJ=m
+CONFIG_USB=y
+CONFIG_USB_DEBUG=y
+CONFIG_USB_ANNOUNCE_NEW_DEVICES=y
+CONFIG_USB_EHCI_HCD=y
+CONFIG_USB_ACM=y
+CONFIG_USB_STORAGE=y
+CONFIG_USB_STORAGE_DEBUG=y
+CONFIG_USB_CHIPIDEA=y
+CONFIG_USB_CHIPIDEA_UDC=y
+CONFIG_USB_CHIPIDEA_HOST=y
+CONFIG_USB_CHIPIDEA_DEBUG=y
+CONFIG_USB_PHY=y
+CONFIG_USB_MXS_PHY=y
+CONFIG_USB_GADGET=y
+CONFIG_USB_ETH=y
+CONFIG_USB_ETH_EEM=y
+CONFIG_MMC=y
+CONFIG_MMC_MXS=y
+CONFIG_NEW_LEDS=y
+CONFIG_LEDS_CLASS=y
+CONFIG_LEDS_GPIO=y
+CONFIG_LEDS_TRIGGERS=y
+CONFIG_LEDS_TRIGGER_HEARTBEAT=y
+CONFIG_LEDS_TRIGGER_DEFAULT_ON=y
+CONFIG_RTC_CLASS=y
+CONFIG_RTC_DRV_DS1307=m
+CONFIG_DMADEVICES=y
+CONFIG_MXS_DMA=y
+CONFIG_STAGING=y
+CONFIG_MXS_LRADC=y
+CONFIG_IIO=y
+CONFIG_NAU7802=y
+CONFIG_PWM_MXS=y
+CONFIG_EXT3_FS=y
+# CONFIG_DNOTIFY is not set
+CONFIG_FSCACHE=m
+CONFIG_FSCACHE_STATS=y
+CONFIG_CACHEFILES=m
+CONFIG_TMPFS=y
+CONFIG_TMPFS_POSIX_ACL=y
+# CONFIG_MISC_FILESYSTEMS is not set
+CONFIG_NFS_FS=y
+CONFIG_NFS_V3_ACL=y
+CONFIG_NFS_V4=y
+CONFIG_ROOT_NFS=y
+CONFIG_PRINTK_TIME=y
+CONFIG_FRAME_WARN=2048
+CONFIG_MAGIC_SYSRQ=y
+CONFIG_UNUSED_SYMBOLS=y
+CONFIG_DEBUG_KERNEL=y
+CONFIG_LOCKUP_DETECTOR=y
+CONFIG_TIMER_STATS=y
+CONFIG_PROVE_LOCKING=y
+CONFIG_DEBUG_INFO=y
+CONFIG_BLK_DEV_IO_TRACE=y
+CONFIG_STRICT_DEVMEM=y
+CONFIG_DEBUG_USER=y
+CONFIG_DEBUG_LL=y
+CONFIG_DEBUG_IMX28_UART=y
+CONFIG_EARLY_PRINTK=y
+CONFIG_CRYPTO_CRC32C=m
+CONFIG_CRYPTO_ARC4=y
+# CONFIG_CRYPTO_ANSI_CPRNG is not set
+# CONFIG_CRYPTO_HW is not set
+CONFIG_CRC16=y
+CONFIG_CRC_ITU_T=m
+CONFIG_CRC7=m
+CONFIG_AVERAGE=y
diff --git a/recipes-kernel/linux/linux-cfa_3.10.bb b/recipes-kernel/linux/linux-cfa_3.10.bb
new file mode 100644
index 0000000..2c2a723
--- /dev/null
+++ b/recipes-kernel/linux/linux-cfa_3.10.bb
@@ -0,0 +1,33 @@ 
+DESCRIPTION = "Linux kernel for Crystalfontz boards"
+SECTion = "kernel"
+LICENSE = "GPLv2"
+
+LIC_FILES_CHKSUM = "file://COPYING;md5=d7810fab7487fb0aad327b76f1be7cd7"
+
+inherit kernel
+require recipes-kernel/linux/linux-dtb.inc
+
+SRC_URI = "git://github.com/crystalfontz/cfa_10036_kernel \
+           file://defconfig"
+
+SRCREV = "552d876f4737ffeb18c9139ede3c439bdcafca94"
+
+S = "${WORKDIR}/git"
+
+# create symlinks that are the defaults of barebox
+pkg_postinst_kernel-devicetree_append () {
+	for DTB_FILE in ${KERNEL_DEVICETREE}
+	do
+		DTB_BASE_NAME=`basename ${DTB_FILE} | awk -F "." '{print $1}'`
+		DTB_BOARD_NAME=`echo ${DTB_BASE_NAME} | awk -F "-" '{print $2}'`
+		DTB_SYMLINK_NAME=`echo ${KERNEL_IMAGE_SYMLINK_NAME} | sed "s/${MACHINE}/${DTB_BASE_NAME}/g"`
+		update-alternatives --install /${KERNEL_IMAGEDEST}/oftree-${DTB_BOARD_NAME} oftree-${DTB_BOARD_NAME} devicetree-${DTB_SYMLINK_NAME}.dtb ${KERNEL_PRIORITY} || true
+	done
+}
+
+pkg_postinst_kernel-image_append () {
+	update-alternatives --install /${KERNEL_IMAGEDEST}/${KERNEL_IMAGETYPE}-${MACHINE} ${KERNEL_IMAGETYPE}-${MACHINE} ${KERNEL_IMAGETYPE}-${KERNEL_VERSION} ${KERNEL_PRIORITY} || true
+}
+
+COMPATIBLE_MACHINE = "cfa10036"
+