[meta-fsl-arm-extra][PATCH 0/4] Add support for CrystalFontz boards

[meta-fsl-arm-extra][PATCH 0/4] Add support for CrystalFontz boards

[Alexandre Belloni]

The following series adds support for the various CrystalFontz boards:
 cfa-10036
 cfa-10037
 cfa-10049
 cfa-10055
 cfa-10056
 cfa-10057
 cfa-10058

The first patch adds support for a mainline barebox, here 2013.08.

The second patch add support for the cfa specific version of the bootlets,
including a patch to be able to use barebox as the payload. We may want to
factorize a bit more the imx-bootlets recipes though.

The third patch adds a recipe for the cfa kernel, based on 3.10.

The last patch adds the machine configuration. It is named cfa10036 as this is the base for all the other boards.

Alexandre Belloni (4):
  barebox: add a recipe to support mainline 2013.08.0
  imx-bootlets: add a recipe for barebox and cfa-10036 support
  linux-cfa: add a kernel recipe supporting Crystalfontz boards
  cfa10036: Add cfa10036 machine configuration

 conf/machine/cfa10036.conf                         |  40 +++++
 recipes-bsp/barebox/barebox_2013.08.0.bb           |  26 +++
 .../imx-bootlets/barebox-fix-paths.patch           |  35 ++++
 recipes-bsp/imx-bootlets/imx-bootlets_cfa.bb       |  65 ++++++++
 recipes-kernel/linux/linux-cfa-3.10/defconfig      | 177 +++++++++++++++++++++
 recipes-kernel/linux/linux-cfa_3.10.bb             |  33 ++++
 6 files changed, 376 insertions(+)
 create mode 100644 conf/machine/cfa10036.conf
 create mode 100644 recipes-bsp/barebox/barebox_2013.08.0.bb
 create mode 100644 recipes-bsp/imx-bootlets/imx-bootlets/barebox-fix-paths.patch
 create mode 100644 recipes-bsp/imx-bootlets/imx-bootlets_cfa.bb
 create mode 100644 recipes-kernel/linux/linux-cfa-3.10/defconfig
 create mode 100644 recipes-kernel/linux/linux-cfa_3.10.bb

-- 
1.8.1.2

[meta-fsl-arm-extra][PATCH 1/4] barebox: add a recipe to support mainline 2013.08.0

[Alexandre Belloni]

Signed-off-by: Alexandre Belloni <alexandre.belloni@free-electrons.com>
---
 recipes-bsp/barebox/barebox_2013.08.0.bb | 26 ++++++++++++++++++++++++++
 1 file changed, 26 insertions(+)
 create mode 100644 recipes-bsp/barebox/barebox_2013.08.0.bb

diff --git a/recipes-bsp/barebox/barebox_2013.08.0.bb b/recipes-bsp/barebox/barebox_2013.08.0.bb
new file mode 100644
index 0000000..2f6118b
--- /dev/null
+++ b/recipes-bsp/barebox/barebox_2013.08.0.bb
@@ -0,0 +1,26 @@
+require recipes-bsp/barebox/barebox.inc
+
+PR = "r1"
+
+SRC_URI = "http://barebox.org/download/${PN}-${PV}.tar.bz2"
+
+SRC_URI[md5sum] = "a61b97a2fedebc808d4b182c2ca18a0c"
+SRC_URI[sha256sum] = "d9e46dd3c68b04ab4cbc37135dc34907dbebef393da4b3e54abb203c295c1620"
+
+python () {
+	if not d.getVar("BAREBOX_MACHINE", True):
+		PN = d.getVar("PN", True)
+		FILE = os.path.basename(d.getVar("FILE", True))
+		bb.debug(1, "To build %s, see %s for instructions on \
+			     setting up your machine config" % (PN, FILE))
+		raise bb.parse.SkipPackage("BAREBOX_MACHINE is not set in the %s machine configuration." % d.getVar("MACHINE", True))
+}
+
+do_pre_configure() {
+	oe_runmake ${BAREBOX_MACHINE}
+}
+
+do_env_deploy() {
+}
+
+COMPATIBLE_MACHINE = "cfa10036"
-- 
1.8.1.2

Re: [meta-fsl-arm-extra][PATCH 1/4] barebox: add a recipe to support mainline 2013.08.0

[Otavio Salvador]

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>

Update the fsl-arm recipes; let the board machine specific fields to a
bbappend in the extra layer.

-- 
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: [meta-fsl-arm-extra][PATCH 1/4] barebox: add a recipe to support mainline 2013.08.0

[Eric Bénard]

Hi Alexandre,

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

> Signed-off-by: Alexandre Belloni <alexandre.belloni@free-electrons.com>
> ---
>  recipes-bsp/barebox/barebox_2013.08.0.bb | 26 ++++++++++++++++++++++++++
>  1 file changed, 26 insertions(+)
>  create mode 100644 recipes-bsp/barebox/barebox_2013.08.0.bb
> 
> diff --git a/recipes-bsp/barebox/barebox_2013.08.0.bb b/recipes-bsp/barebox/barebox_2013.08.0.bb
> new file mode 100644
> index 0000000..2f6118b
> --- /dev/null
> +++ b/recipes-bsp/barebox/barebox_2013.08.0.bb
> @@ -0,0 +1,26 @@
> +require recipes-bsp/barebox/barebox.inc
> +
> +PR = "r1"
> +
> +SRC_URI = "http://barebox.org/download/${PN}-${PV}.tar.bz2"
> +
> +SRC_URI[md5sum] = "a61b97a2fedebc808d4b182c2ca18a0c"
> +SRC_URI[sha256sum] = "d9e46dd3c68b04ab4cbc37135dc34907dbebef393da4b3e54abb203c295c1620"
> +
> +python () {
> +	if not d.getVar("BAREBOX_MACHINE", True):
> +		PN = d.getVar("PN", True)
> +		FILE = os.path.basename(d.getVar("FILE", True))
> +		bb.debug(1, "To build %s, see %s for instructions on \
> +			     setting up your machine config" % (PN, FILE))
> +		raise bb.parse.SkipPackage("BAREBOX_MACHINE is not set in the %s machine configuration." % d.getVar("MACHINE", True))
> +}
> +

if you plan to create a generic barebox recipe and as barebox is using
Kconfig like Linux does, I would recommend to include the defconfig for
your board here as done on the kernel side instead of using the
defconfig which may exist into barebox's mainline sources (that makes
customization easier especially when using SOM).

If you don't plan do create the generic barebox recipe, that's still on
my todo list but with a very low priority :-)

Best regards,
Eric

Re: [meta-fsl-arm-extra][PATCH 1/4] barebox: add a recipe to support mainline 2013.08.0

[Otavio Salvador]

On Thu, Aug 22, 2013 at 2:14 PM, Eric Bénard <eric@eukrea.com> wrote:
> Hi Alexandre,
>
> Le Thu, 22 Aug 2013 16:51:14 +0200,
> Alexandre Belloni <alexandre.belloni@free-electrons.com> a écrit :
>
>> Signed-off-by: Alexandre Belloni <alexandre.belloni@free-electrons.com>
>> ---
>>  recipes-bsp/barebox/barebox_2013.08.0.bb | 26 ++++++++++++++++++++++++++
>>  1 file changed, 26 insertions(+)
>>  create mode 100644 recipes-bsp/barebox/barebox_2013.08.0.bb
>>
>> diff --git a/recipes-bsp/barebox/barebox_2013.08.0.bb b/recipes-bsp/barebox/barebox_2013.08.0.bb
>> new file mode 100644
>> index 0000000..2f6118b
>> --- /dev/null
>> +++ b/recipes-bsp/barebox/barebox_2013.08.0.bb
>> @@ -0,0 +1,26 @@
>> +require recipes-bsp/barebox/barebox.inc
>> +
>> +PR = "r1"
>> +
>> +SRC_URI = "http://barebox.org/download/${PN}-${PV}.tar.bz2"
>> +
>> +SRC_URI[md5sum] = "a61b97a2fedebc808d4b182c2ca18a0c"
>> +SRC_URI[sha256sum] = "d9e46dd3c68b04ab4cbc37135dc34907dbebef393da4b3e54abb203c295c1620"
>> +
>> +python () {
>> +     if not d.getVar("BAREBOX_MACHINE", True):
>> +             PN = d.getVar("PN", True)
>> +             FILE = os.path.basename(d.getVar("FILE", True))
>> +             bb.debug(1, "To build %s, see %s for instructions on \
>> +                          setting up your machine config" % (PN, FILE))
>> +             raise bb.parse.SkipPackage("BAREBOX_MACHINE is not set in the %s machine configuration." % d.getVar("MACHINE", True))
>> +}
>> +
>
> if you plan to create a generic barebox recipe and as barebox is using
> Kconfig like Linux does, I would recommend to include the defconfig for
> your board here as done on the kernel side instead of using the
> defconfig which may exist into barebox's mainline sources (that makes
> customization easier especially when using SOM).
>
> If you don't plan do create the generic barebox recipe, that's still on
> my todo list but with a very low priority :-)

Agreed.

-- 
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: [meta-fsl-arm-extra][PATCH 1/4] barebox: add a recipe to support mainline 2013.08.0

[Alexandre Belloni]

On 22/08/2013 20:00, Otavio Salvador wrote:
> On Thu, Aug 22, 2013 at 2:14 PM, Eric Bénard <eric@eukrea.com> wrote:
>> Hi Alexandre,
>>
>> Le Thu, 22 Aug 2013 16:51:14 +0200,
>> Alexandre Belloni <alexandre.belloni@free-electrons.com> a écrit :
>>
>>> Signed-off-by: Alexandre Belloni <alexandre.belloni@free-electrons.com>
>>> ---
>>>  recipes-bsp/barebox/barebox_2013.08.0.bb | 26 ++++++++++++++++++++++++++
>>>  1 file changed, 26 insertions(+)
>>>  create mode 100644 recipes-bsp/barebox/barebox_2013.08.0.bb
>>>
>>> diff --git a/recipes-bsp/barebox/barebox_2013.08.0.bb b/recipes-bsp/barebox/barebox_2013.08.0.bb
>>> new file mode 100644
>>> index 0000000..2f6118b
>>> --- /dev/null
>>> +++ b/recipes-bsp/barebox/barebox_2013.08.0.bb
>>> @@ -0,0 +1,26 @@
>>> +require recipes-bsp/barebox/barebox.inc
>>> +
>>> +PR = "r1"
>>> +
>>> +SRC_URI = "http://barebox.org/download/${PN}-${PV}.tar.bz2"
>>> +
>>> +SRC_URI[md5sum] = "a61b97a2fedebc808d4b182c2ca18a0c"
>>> +SRC_URI[sha256sum] = "d9e46dd3c68b04ab4cbc37135dc34907dbebef393da4b3e54abb203c295c1620"
>>> +
>>> +python () {
>>> +     if not d.getVar("BAREBOX_MACHINE", True):
>>> +             PN = d.getVar("PN", True)
>>> +             FILE = os.path.basename(d.getVar("FILE", True))
>>> +             bb.debug(1, "To build %s, see %s for instructions on \
>>> +                          setting up your machine config" % (PN, FILE))
>>> +             raise bb.parse.SkipPackage("BAREBOX_MACHINE is not set in the %s machine configuration." % d.getVar("MACHINE", True))
>>> +}
>>> +
>> if you plan to create a generic barebox recipe and as barebox is using
>> Kconfig like Linux does, I would recommend to include the defconfig for
>> your board here as done on the kernel side instead of using the
>> defconfig which may exist into barebox's mainline sources (that makes
>> customization easier especially when using SOM).
>>
>> If you don't plan do create the generic barebox recipe, that's still on
>> my todo list but with a very low priority :-)
> Agreed.
>
I'm actually wondering about that. The defconfig included in the barebox
mainline is perfectly fine. And people wanting to change it will have to
write a bbappend anyway or am I missing something ?
Anyway, I don't have a strong opinion on that one.

-- 
Alexandre Belloni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

Re: [meta-fsl-arm-extra][PATCH 1/4] barebox: add a recipe to support mainline 2013.08.0

[Otavio Salvador]

On Thu, Aug 22, 2013 at 8:06 PM, Alexandre Belloni
<alexandre.belloni@free-electrons.com> wrote:
> On 22/08/2013 20:00, Otavio Salvador wrote:
>> On Thu, Aug 22, 2013 at 2:14 PM, Eric Bénard <eric@eukrea.com> wrote:
>>> Hi Alexandre,
>>>
>>> Le Thu, 22 Aug 2013 16:51:14 +0200,
>>> Alexandre Belloni <alexandre.belloni@free-electrons.com> a écrit :
>>>
>>>> Signed-off-by: Alexandre Belloni <alexandre.belloni@free-electrons.com>
>>>> ---
>>>>  recipes-bsp/barebox/barebox_2013.08.0.bb | 26 ++++++++++++++++++++++++++
>>>>  1 file changed, 26 insertions(+)
>>>>  create mode 100644 recipes-bsp/barebox/barebox_2013.08.0.bb
>>>>
>>>> diff --git a/recipes-bsp/barebox/barebox_2013.08.0.bb b/recipes-bsp/barebox/barebox_2013.08.0.bb
>>>> new file mode 100644
>>>> index 0000000..2f6118b
>>>> --- /dev/null
>>>> +++ b/recipes-bsp/barebox/barebox_2013.08.0.bb
>>>> @@ -0,0 +1,26 @@
>>>> +require recipes-bsp/barebox/barebox.inc
>>>> +
>>>> +PR = "r1"
>>>> +
>>>> +SRC_URI = "http://barebox.org/download/${PN}-${PV}.tar.bz2"
>>>> +
>>>> +SRC_URI[md5sum] = "a61b97a2fedebc808d4b182c2ca18a0c"
>>>> +SRC_URI[sha256sum] = "d9e46dd3c68b04ab4cbc37135dc34907dbebef393da4b3e54abb203c295c1620"
>>>> +
>>>> +python () {
>>>> +     if not d.getVar("BAREBOX_MACHINE", True):
>>>> +             PN = d.getVar("PN", True)
>>>> +             FILE = os.path.basename(d.getVar("FILE", True))
>>>> +             bb.debug(1, "To build %s, see %s for instructions on \
>>>> +                          setting up your machine config" % (PN, FILE))
>>>> +             raise bb.parse.SkipPackage("BAREBOX_MACHINE is not set in the %s machine configuration." % d.getVar("MACHINE", True))
>>>> +}
>>>> +
>>> if you plan to create a generic barebox recipe and as barebox is using
>>> Kconfig like Linux does, I would recommend to include the defconfig for
>>> your board here as done on the kernel side instead of using the
>>> defconfig which may exist into barebox's mainline sources (that makes
>>> customization easier especially when using SOM).
>>>
>>> If you don't plan do create the generic barebox recipe, that's still on
>>> my todo list but with a very low priority :-)
>> Agreed.
>>
> I'm actually wondering about that. The defconfig included in the barebox
> mainline is perfectly fine. And people wanting to change it will have to
> write a bbappend anyway or am I missing something ?
> Anyway, I don't have a strong opinion on that one.

This is the way to go in longterm as it allow for easy customization
and user can easy change it in GIT for testing 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: [meta-fsl-arm-extra][PATCH 1/4] barebox: add a recipe to support mainline 2013.08.0

[Eric Bénard]

Hi Alexandre,

Le Fri, 23 Aug 2013 01:06:14 +0200,
Alexandre Belloni <alexandre.belloni@free-electrons.com> a écrit :

> On 22/08/2013 20:00, Otavio Salvador wrote:
> > On Thu, Aug 22, 2013 at 2:14 PM, Eric Bénard <eric@eukrea.com> wrote:
> >> Hi Alexandre,
> >>
> >> Le Thu, 22 Aug 2013 16:51:14 +0200,
> >> Alexandre Belloni <alexandre.belloni@free-electrons.com> a écrit :
> >>
> >>> Signed-off-by: Alexandre Belloni <alexandre.belloni@free-electrons.com>
> >>> ---
> >>>  recipes-bsp/barebox/barebox_2013.08.0.bb | 26 ++++++++++++++++++++++++++
> >>>  1 file changed, 26 insertions(+)
> >>>  create mode 100644 recipes-bsp/barebox/barebox_2013.08.0.bb
> >>>
> >>> diff --git a/recipes-bsp/barebox/barebox_2013.08.0.bb b/recipes-bsp/barebox/barebox_2013.08.0.bb
> >>> new file mode 100644
> >>> index 0000000..2f6118b
> >>> --- /dev/null
> >>> +++ b/recipes-bsp/barebox/barebox_2013.08.0.bb
> >>> @@ -0,0 +1,26 @@
> >>> +require recipes-bsp/barebox/barebox.inc
> >>> +
> >>> +PR = "r1"
> >>> +
> >>> +SRC_URI = "http://barebox.org/download/${PN}-${PV}.tar.bz2"
> >>> +
> >>> +SRC_URI[md5sum] = "a61b97a2fedebc808d4b182c2ca18a0c"
> >>> +SRC_URI[sha256sum] = "d9e46dd3c68b04ab4cbc37135dc34907dbebef393da4b3e54abb203c295c1620"
> >>> +
> >>> +python () {
> >>> +     if not d.getVar("BAREBOX_MACHINE", True):
> >>> +             PN = d.getVar("PN", True)
> >>> +             FILE = os.path.basename(d.getVar("FILE", True))
> >>> +             bb.debug(1, "To build %s, see %s for instructions on \
> >>> +                          setting up your machine config" % (PN, FILE))
> >>> +             raise bb.parse.SkipPackage("BAREBOX_MACHINE is not set in the %s machine configuration." % d.getVar("MACHINE", True))
> >>> +}
> >>> +
> >> if you plan to create a generic barebox recipe and as barebox is using
> >> Kconfig like Linux does, I would recommend to include the defconfig for
> >> your board here as done on the kernel side instead of using the
> >> defconfig which may exist into barebox's mainline sources (that makes
> >> customization easier especially when using SOM).
> >>
> >> If you don't plan do create the generic barebox recipe, that's still on
> >> my todo list but with a very low priority :-)
> > Agreed.
> >
> I'm actually wondering about that. The defconfig included in the barebox
> mainline is perfectly fine. And people wanting to change it will have to
> write a bbappend anyway or am I missing something ?

a bbappend will be needed but in that case the python () which skips the
package if BAREBOX_MACHINE is not set shouldn't go in the default
barebox recipe else every machine using barebox will have to set
BAREBOX_MACHINE and then to hack the defconfig after pre_configure.

Eric

[meta-fsl-arm-extra][PATCH 2/4] imx-bootlets: add a recipe for barebox and cfa-10036 support

[Alexandre Belloni]

Signed-off-by: Alexandre Belloni <alexandre.belloni@free-electrons.com>
---
 .../imx-bootlets/barebox-fix-paths.patch           | 35 ++++++++++++
 recipes-bsp/imx-bootlets/imx-bootlets_cfa.bb       | 65 ++++++++++++++++++++++
 2 files changed, 100 insertions(+)
 create mode 100644 recipes-bsp/imx-bootlets/imx-bootlets/barebox-fix-paths.patch
 create mode 100644 recipes-bsp/imx-bootlets/imx-bootlets_cfa.bb

diff --git a/recipes-bsp/imx-bootlets/imx-bootlets/barebox-fix-paths.patch b/recipes-bsp/imx-bootlets/imx-bootlets/barebox-fix-paths.patch
new file mode 100644
index 0000000..c6c90d1
--- /dev/null
+++ b/recipes-bsp/imx-bootlets/imx-bootlets/barebox-fix-paths.patch
@@ -0,0 +1,35 @@
+From 98721be1c1762adec9130f15263d98e575e290ae Mon Sep 17 00:00:00 2001
+From: Alexandre Belloni <alexandre.belloni@free-electrons.com>
+Date: Thu, 8 Aug 2013 20:14:51 +0200
+Subject: [PATCH] imx-bootlets: Fix paths used during boot stream generation
+
+This will be run during image generation thus this won't use a
+complete path to allow for relocation.
+
+Upstream-Status: Inappropriate [configuration]
+
+Signed-off-by: Alexandre Belloni <alexandre.belloni@free-electrons.com>
+---
+ barebox_ivt.bd | 6 +++---
+ 1 file changed, 3 insertions(+), 3 deletions(-)
+
+diff --git a/barebox_ivt.bd b/barebox_ivt.bd
+index 0c67e9c..c603f9e 100644
+--- a/barebox_ivt.bd
++++ b/barebox_ivt.bd
+@@ -1,9 +1,9 @@
+ // STMP378x ROM command script to load and run U-Boot
+ 
+ sources {
+-	power_prep="./power_prep/power_prep";
+-	sdram_prep="./boot_prep/boot_prep";
+-	barebox="./barebox";
++	power_prep="imx-bootlets-power_prep-@MACHINE@";
++	sdram_prep="imx-bootlets-boot_prep-@MACHINE@";
++	barebox="barebox-@MACHINE@.bin";
+ }
+ 
+ section (0) {
+-- 
+1.8.1.2
+
diff --git a/recipes-bsp/imx-bootlets/imx-bootlets_cfa.bb b/recipes-bsp/imx-bootlets/imx-bootlets_cfa.bb
new file mode 100644
index 0000000..580adef
--- /dev/null
+++ b/recipes-bsp/imx-bootlets/imx-bootlets_cfa.bb
@@ -0,0 +1,65 @@
+DESCRIPTION = "i.MXS boot streams"
+LICENSE = "GPL-2.0"
+LIC_FILES_CHKSUM = "file://${COREBASE}/meta/files/common-licenses/GPL-2.0;md5=801f80980d171dd6425610833a22dbe6"
+
+PR = "r1"
+
+SRC_URI = "git://github.com/crystalfontz/bootlets.git \
+		   file://barebox-fix-paths.patch \
+		  "
+SRCREV = "03bfdef0fa7efc6b64392e3eebfaf688018751cc"
+
+S = "${WORKDIR}/git"
+
+# Disable parallel building or it may fail to build.
+PARALLEL_MAKE = ""
+
+EXTRA_OEMAKE = "CROSS_COMPILE=${TARGET_PREFIX}"
+
+# Ensure machine defines the IMXBOOTLETS_MACHINE
+python () {
+	if not d.getVar("IMXBOOTLETS_MACHINE", True):
+		PN = d.getVar("PN", True)
+		FILE = os.path.basename(d.getVar("FILE", True))
+		bb.debug(1, "To build %s, see %s for instructions on \
+			     setting up your machine config" % (PN, FILE))
+		raise bb.parse.SkipPackage("because IMXBOOTLETS_MACHINE is not set")
+}
+
+do_configure () {
+    sed -i 's,@MACHINE@,${MACHINE},g' barebox_ivt.bd
+}
+
+do_compile () {
+    oe_runmake BOARD=${IMXBOOTLETS_MACHINE} linux_prep \
+                                            boot_prep \
+                                            power_prep
+}
+
+do_install () {
+    install -d ${D}/boot/
+    install -m 644 boot_prep/boot_prep power_prep/power_prep \
+                   barebox_ivt.bd \
+                   ${D}/boot
+}
+
+FILES_${PN} = "/boot"
+
+do_deploy () {
+    install -d ${DEPLOY_DIR_IMAGE}
+
+	for f in boot_prep/boot_prep \
+             power_prep/power_prep \
+             barebox_ivt.bd; do
+        full_name="imx-bootlets-`basename $f`-${MACHINE}-${PV}-${PR}"
+        symlink_name="imx-bootlets-`basename $f`-${MACHINE}"
+
+        install -m 644 ${S}/$f ${DEPLOY_DIR_IMAGE}/$full_name
+        (cd ${DEPLOY_DIR_IMAGE} ; rm -f $symlink_nake ; ln -sf $full_name $symlink_name)
+    done
+}
+
+addtask deploy before do_build after do_compile
+
+PACKAGE_ARCH = "${MACHINE_ARCH}"
+COMPATIBLE_MACHINE = "(mxs)"
-- 
1.8.1.2

Re: [meta-fsl-arm-extra][PATCH 2/4] imx-bootlets: add a recipe for barebox and cfa-10036 support

[Otavio Salvador]

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>
...
> new file mode 100644
> index 0000000..c6c90d1
> --- /dev/null
> +++ b/recipes-bsp/imx-bootlets/imx-bootlets/barebox-fix-paths.patch
> @@ -0,0 +1,35 @@
> +From 98721be1c1762adec9130f15263d98e575e290ae Mon Sep 17 00:00:00 2001
> +From: Alexandre Belloni <alexandre.belloni@free-electrons.com>
> +Date: Thu, 8 Aug 2013 20:14:51 +0200
> +Subject: [PATCH] imx-bootlets: Fix paths used during boot stream generation
> +
> +This will be run during image generation thus this won't use a
> +complete path to allow for relocation.
> +
> +Upstream-Status: Inappropriate [configuration]
> +
> +Signed-off-by: Alexandre Belloni <alexandre.belloni@free-electrons.com>
> +---
> + barebox_ivt.bd | 6 +++---
> + 1 file changed, 3 insertions(+), 3 deletions(-)
> +
> +diff --git a/barebox_ivt.bd b/barebox_ivt.bd
> +index 0c67e9c..c603f9e 100644
> +--- a/barebox_ivt.bd
> ++++ b/barebox_ivt.bd
> +@@ -1,9 +1,9 @@
> + // STMP378x ROM command script to load and run U-Boot
> +
> + sources {
> +-      power_prep="./power_prep/power_prep";
> +-      sdram_prep="./boot_prep/boot_prep";
> +-      barebox="./barebox";
> ++      power_prep="imx-bootlets-power_prep-@MACHINE@";
> ++      sdram_prep="imx-bootlets-boot_prep-@MACHINE@";
> ++      barebox="barebox-@MACHINE@.bin";
> + }
> +
> + section (0) {
> +--
> +1.8.1.2


This patch is generic, move it to fsl-arm :)

> diff --git a/recipes-bsp/imx-bootlets/imx-bootlets_cfa.bb b/recipes-bsp/imx-bootlets/imx-bootlets_cfa.bb
> new file mode 100644
> index 0000000..580adef
> --- /dev/null
> +++ b/recipes-bsp/imx-bootlets/imx-bootlets_cfa.bb
> @@ -0,0 +1,65 @@
> +DESCRIPTION = "i.MXS boot streams"
> +LICENSE = "GPL-2.0"
> +LIC_FILES_CHKSUM = "file://${COREBASE}/meta/files/common-licenses/GPL-2.0;md5=801f80980d171dd6425610833a22dbe6"
> +
> +PR = "r1"
> +
> +SRC_URI = "git://github.com/crystalfontz/bootlets.git \
> +                  file://barebox-fix-paths.patch \
> +                 "
...

Use a bbappend :)

-- 
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: [meta-fsl-arm-extra][PATCH 2/4] imx-bootlets: add a recipe for barebox and cfa-10036 support

[Alexandre Belloni]

On 22/08/2013 19:10, 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>
> ...
>> new file mode 100644
>> index 0000000..c6c90d1
>> --- /dev/null
>> +++ b/recipes-bsp/imx-bootlets/imx-bootlets/barebox-fix-paths.patch
>> @@ -0,0 +1,35 @@
>> +From 98721be1c1762adec9130f15263d98e575e290ae Mon Sep 17 00:00:00 2001
>> +From: Alexandre Belloni <alexandre.belloni@free-electrons.com>
>> +Date: Thu, 8 Aug 2013 20:14:51 +0200
>> +Subject: [PATCH] imx-bootlets: Fix paths used during boot stream generation
>> +
>> +This will be run during image generation thus this won't use a
>> +complete path to allow for relocation.
>> +
>> +Upstream-Status: Inappropriate [configuration]
>> +
>> +Signed-off-by: Alexandre Belloni <alexandre.belloni@free-electrons.com>
>> +---
>> + barebox_ivt.bd | 6 +++---
>> + 1 file changed, 3 insertions(+), 3 deletions(-)
>> +
>> +diff --git a/barebox_ivt.bd b/barebox_ivt.bd
>> +index 0c67e9c..c603f9e 100644
>> +--- a/barebox_ivt.bd
>> ++++ b/barebox_ivt.bd
>> +@@ -1,9 +1,9 @@
>> + // STMP378x ROM command script to load and run U-Boot
>> +
>> + sources {
>> +-      power_prep="./power_prep/power_prep";
>> +-      sdram_prep="./boot_prep/boot_prep";
>> +-      barebox="./barebox";
>> ++      power_prep="imx-bootlets-power_prep-@MACHINE@";
>> ++      sdram_prep="imx-bootlets-boot_prep-@MACHINE@";
>> ++      barebox="barebox-@MACHINE@.bin";
>> + }
>> +
>> + section (0) {
>> +--
>> +1.8.1.2
>
> This patch is generic, move it to fsl-arm :)
>

Probably not generic enough, barebox_ivt.bd is only present in the
crystalfontz's github repository. I think that is the main difference
but I didn't check.

>> diff --git a/recipes-bsp/imx-bootlets/imx-bootlets_cfa.bb b/recipes-bsp/imx-bootlets/imx-bootlets_cfa.bb
>> new file mode 100644
>> index 0000000..580adef
>> --- /dev/null
>> +++ b/recipes-bsp/imx-bootlets/imx-bootlets_cfa.bb
>> @@ -0,0 +1,65 @@
>> +DESCRIPTION = "i.MXS boot streams"
>> +LICENSE = "GPL-2.0"
>> +LIC_FILES_CHKSUM = "file://${COREBASE}/meta/files/common-licenses/GPL-2.0;md5=801f80980d171dd6425610833a22dbe6"
>> +
>> +PR = "r1"
>> +
>> +SRC_URI = "git://github.com/crystalfontz/bootlets.git \
>> +                  file://barebox-fix-paths.patch \
>> +                 "
> ...
>
> Use a bbappend :)
>


-- 
Alexandre Belloni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

Re: [meta-fsl-arm-extra][PATCH 2/4] imx-bootlets: add a recipe for barebox and cfa-10036 support

[Otavio Salvador]

On Thu, Aug 22, 2013 at 2:20 PM, Alexandre Belloni
<alexandre.belloni@free-electrons.com> wrote:
> On 22/08/2013 19:10, 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>
>> ...
>>> new file mode 100644
>>> index 0000000..c6c90d1
>>> --- /dev/null
>>> +++ b/recipes-bsp/imx-bootlets/imx-bootlets/barebox-fix-paths.patch
>>> @@ -0,0 +1,35 @@
>>> +From 98721be1c1762adec9130f15263d98e575e290ae Mon Sep 17 00:00:00 2001
>>> +From: Alexandre Belloni <alexandre.belloni@free-electrons.com>
>>> +Date: Thu, 8 Aug 2013 20:14:51 +0200
>>> +Subject: [PATCH] imx-bootlets: Fix paths used during boot stream generation
>>> +
>>> +This will be run during image generation thus this won't use a
>>> +complete path to allow for relocation.
>>> +
>>> +Upstream-Status: Inappropriate [configuration]
>>> +
>>> +Signed-off-by: Alexandre Belloni <alexandre.belloni@free-electrons.com>
>>> +---
>>> + barebox_ivt.bd | 6 +++---
>>> + 1 file changed, 3 insertions(+), 3 deletions(-)
>>> +
>>> +diff --git a/barebox_ivt.bd b/barebox_ivt.bd
>>> +index 0c67e9c..c603f9e 100644
>>> +--- a/barebox_ivt.bd
>>> ++++ b/barebox_ivt.bd
>>> +@@ -1,9 +1,9 @@
>>> + // STMP378x ROM command script to load and run U-Boot
>>> +
>>> + sources {
>>> +-      power_prep="./power_prep/power_prep";
>>> +-      sdram_prep="./boot_prep/boot_prep";
>>> +-      barebox="./barebox";
>>> ++      power_prep="imx-bootlets-power_prep-@MACHINE@";
>>> ++      sdram_prep="imx-bootlets-boot_prep-@MACHINE@";
>>> ++      barebox="barebox-@MACHINE@.bin";
>>> + }
>>> +
>>> + section (0) {
>>> +--
>>> +1.8.1.2
>>
>> This patch is generic, move it to fsl-arm :)
>>
>
> Probably not generic enough, barebox_ivt.bd is only present in the
> crystalfontz's github repository. I think that is the main difference
> but I didn't check.

I'd prefer to check the changes need and keep them in imx-bootlets to
avoid other boards intending to use barebox to redo it. The patch for
the board can be done using the bbappend.


-- 
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-fsl-arm-extra][PATCH 3/4] linux-cfa: add a kernel recipe supporting Crystalfontz boards

[Alexandre Belloni]

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
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"
+
-- 
1.8.1.2

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

[Otavio Salvador]

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?

-- 
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: [meta-fsl-arm-extra][PATCH 3/4] linux-cfa: add a kernel recipe supporting Crystalfontz boards

[Alexandre Belloni]

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.

-- 
Alexandre Belloni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

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

[Otavio Salvador]

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?

-- 
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: [meta-fsl-arm-extra][PATCH 3/4] linux-cfa: add a kernel recipe supporting Crystalfontz boards

[Alexandre Belloni]

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 ?

-- 
Alexandre Belloni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

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

[Eric Bénard]

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

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

[Otavio Salvador]

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.

-- 
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: [meta-fsl-arm-extra][PATCH 3/4] linux-cfa: add a kernel recipe supporting Crystalfontz boards

[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.
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.

-- 
Alexandre Belloni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

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

[Otavio Salvador]

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. :)

-- 
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: [meta-fsl-arm-extra][PATCH 3/4] linux-cfa: add a kernel recipe supporting Crystalfontz boards

[Marek Vasut]

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

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

[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.


-- 
Alexandre Belloni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

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

[Marek Vasut]

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

Qt5 with opengl hw acceleration on imx53

[Simone]

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

Re: Qt5 with opengl hw acceleration on imx53

[Eric Bénard]

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

Re: Qt5 with opengl hw acceleration on imx53

[Simone]

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

Re: Qt5 with opengl hw acceleration on imx53

[Eric Bénard]

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

Re: Qt5 with opengl hw acceleration on imx53

[Simone]

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

Re: Qt5 with opengl hw acceleration on imx53

[Abhijit Potnis]

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

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
>

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

Re: Qt5 with opengl hw acceleration on imx53

[Simone]

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

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
> 

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

Re: Qt5 with opengl hw acceleration on imx53

[Abhijit Potnis]

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

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
>>
>
>

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

Re: Qt5 with opengl hw acceleration on imx53

[Simone]

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

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
_______________________________________________
meta-freescale mailing list
meta-freescale@yoctoproject.org <mailto:meta-freescale@yoctoproject.org> 
https://lists.yoctoproject.org/listinfo/meta-freescale

 

 


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

Re: Qt5 with opengl hw acceleration on imx53

[Abhijit Potnis]

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

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****
>
> ** **
>
> ** **
>

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

Re: Qt5 with opengl hw acceleration on imx53

[Simone]

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

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
_______________________________________________
meta-freescale mailing list
meta-freescale@yoctoproject.org <mailto:meta-freescale@yoctoproject.org> 
https://lists.yoctoproject.org/listinfo/meta-freescale

 

 

 


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

Re: Qt5 with opengl hw acceleration on imx53

[Simone]

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

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
_______________________________________________
meta-freescale mailing list
meta-freescale@yoctoproject.org <mailto:meta-freescale@yoctoproject.org> 
https://lists.yoctoproject.org/listinfo/meta-freescale

 

 

 


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

Re: Qt5 with opengl hw acceleration on imx53

[Simone]

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

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
_______________________________________________
meta-freescale mailing list
meta-freescale@yoctoproject.org <mailto:meta-freescale@yoctoproject.org> 
https://lists.yoctoproject.org/listinfo/meta-freescale

 

 


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

[meta-fsl-arm-extra][PATCH 4/4] cfa10036: Add cfa10036 machine configuration

[Alexandre Belloni]

This configuration supports the following Crystalfontz boards:
 - cfa-10036
 - cfa-10037
 - cfa-10049
 - cfa-10055
 - cfa-10056
 - cfa-10057
 - cfa-10058

which are all based on the cfa-10036.

Signed-off-by: Alexandre Belloni <alexandre.belloni@free-electrons.com>
---
 conf/machine/cfa10036.conf | 40 ++++++++++++++++++++++++++++++++++++++++
 1 file changed, 40 insertions(+)
 create mode 100644 conf/machine/cfa10036.conf

diff --git a/conf/machine/cfa10036.conf b/conf/machine/cfa10036.conf
new file mode 100644
index 0000000..7f2fe35
--- /dev/null
+++ b/conf/machine/cfa10036.conf
@@ -0,0 +1,40 @@
+#@TYPE: Machine
+#@NAME: Crystalfontz CFA-10036
+#@SOC: i.MX28
+#@DESCRIPTION: Machine configuration for CFA-10036
+
+include conf/machine/include/mxs-base.inc
+
+SOC_FAMILY = "mxs:mx28"
+
+PREFERRED_PROVIDER_virtual/kernel = "linux-cfa"
+PREFERRED_VERSION_imx-bootlets = "cfa"
+
+BAREBOX_MACHINE = "cfa10036_defconfig"
+IMAGE_BOOTLOADER = "barebox"
+BAREBOX_BINARY = "barebox"
+
+IMXBOOTLETS_MACHINE = "cfa10036"
+BOOT_SPACE="32768"
+
+KERNEL_IMAGETYPE = "zImage"
+KERNEL_DEVICETREE = "${S}/arch/arm/boot/dts/imx28-cfa10036.dts"
+KERNEL_DEVICETREE += "${S}/arch/arm/boot/dts/imx28-cfa10037.dts"
+KERNEL_DEVICETREE += "${S}/arch/arm/boot/dts/imx28-cfa10049.dts"
+KERNEL_DEVICETREE += "${S}/arch/arm/boot/dts/imx28-cfa10055.dts"
+KERNEL_DEVICETREE += "${S}/arch/arm/boot/dts/imx28-cfa10056.dts"
+KERNEL_DEVICETREE += "${S}/arch/arm/boot/dts/imx28-cfa10057.dts"
+KERNEL_DEVICETREE += "${S}/arch/arm/boot/dts/imx28-cfa10058.dts"
+
+#we need the kernel to be installed in the final image
+IMAGE_INSTALL_append = " kernel-image kernel-devicetree"
+
+SDCARD_ROOTFS ?= "${DEPLOY_DIR_IMAGE}/${IMAGE_NAME}.rootfs.ext3"
+IMAGE_FSTYPES ?= "tar.bz2 ext3 barebox.sb sdcard"
+
+SERIAL_CONSOLE = "115200 ttyAMA0"
+
+MACHINE_FEATURES = "apm usbgadget usbhost vfat"
+
+# Gstreamer plugin
+MACHINE_GSTREAMER_PLUGIN ?= "gst-fsl-plugin"
-- 
1.8.1.2

Re: [meta-fsl-arm-extra][PATCH 4/4] cfa10036: Add cfa10036 machine configuration

[Otavio Salvador]

On Thu, Aug 22, 2013 at 11:51 AM, Alexandre Belloni
<alexandre.belloni@free-electrons.com> wrote:
> This configuration supports the following Crystalfontz boards:
>  - cfa-10036
>  - cfa-10037
>  - cfa-10049
>  - cfa-10055
>  - cfa-10056
>  - cfa-10057
>  - cfa-10058
>
> which are all based on the cfa-10036.
>
> Signed-off-by: Alexandre Belloni <alexandre.belloni@free-electrons.com>
> ---
>  conf/machine/cfa10036.conf | 40 ++++++++++++++++++++++++++++++++++++++++
>  1 file changed, 40 insertions(+)
>  create mode 100644 conf/machine/cfa10036.conf
>
> diff --git a/conf/machine/cfa10036.conf b/conf/machine/cfa10036.conf
> new file mode 100644
> index 0000000..7f2fe35
> --- /dev/null
> +++ b/conf/machine/cfa10036.conf
> @@ -0,0 +1,40 @@
> +#@TYPE: Machine
> +#@NAME: Crystalfontz CFA-10036
> +#@SOC: i.MX28
> +#@DESCRIPTION: Machine configuration for CFA-10036
> +
> +include conf/machine/include/mxs-base.inc
> +
> +SOC_FAMILY = "mxs:mx28"
> +
> +PREFERRED_PROVIDER_virtual/kernel = "linux-cfa"
> +PREFERRED_VERSION_imx-bootlets = "cfa"
> +
> +BAREBOX_MACHINE = "cfa10036_defconfig"
> +IMAGE_BOOTLOADER = "barebox"
> +BAREBOX_BINARY = "barebox"
> +
> +IMXBOOTLETS_MACHINE = "cfa10036"
> +BOOT_SPACE="32768"
> +
> +KERNEL_IMAGETYPE = "zImage"
> +KERNEL_DEVICETREE = "${S}/arch/arm/boot/dts/imx28-cfa10036.dts"

imx28-cfa10036.dtb ...

No full path.

> +KERNEL_DEVICETREE += "${S}/arch/arm/boot/dts/imx28-cfa10037.dts"
> +KERNEL_DEVICETREE += "${S}/arch/arm/boot/dts/imx28-cfa10049.dts"
> +KERNEL_DEVICETREE += "${S}/arch/arm/boot/dts/imx28-cfa10055.dts"
> +KERNEL_DEVICETREE += "${S}/arch/arm/boot/dts/imx28-cfa10056.dts"
> +KERNEL_DEVICETREE += "${S}/arch/arm/boot/dts/imx28-cfa10057.dts"
> +KERNEL_DEVICETREE += "${S}/arch/arm/boot/dts/imx28-cfa10058.dts"
> +
> +#we need the kernel to be installed in the final image
> +IMAGE_INSTALL_append = " kernel-image kernel-devicetree"
> +
> +SDCARD_ROOTFS ?= "${DEPLOY_DIR_IMAGE}/${IMAGE_NAME}.rootfs.ext3"
> +IMAGE_FSTYPES ?= "tar.bz2 ext3 barebox.sb sdcard"
> +
> +SERIAL_CONSOLE = "115200 ttyAMA0"
> +
> +MACHINE_FEATURES = "apm usbgadget usbhost vfat"
> +
> +# Gstreamer plugin
> +MACHINE_GSTREAMER_PLUGIN ?= "gst-fsl-plugin"
> --
> 1.8.1.2
>
> _______________________________________________
> meta-freescale mailing list
> meta-freescale@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-freescale



-- 
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: [meta-fsl-arm-extra][PATCH 4/4] cfa10036: Add cfa10036 machine configuration

[Alexandre Belloni]

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:
>> This configuration supports the following Crystalfontz boards:
>>  - cfa-10036
>>  - cfa-10037
>>  - cfa-10049
>>  - cfa-10055
>>  - cfa-10056
>>  - cfa-10057
>>  - cfa-10058
>>
>> which are all based on the cfa-10036.
>>
>> Signed-off-by: Alexandre Belloni <alexandre.belloni@free-electrons.com>
>> ---
>>  conf/machine/cfa10036.conf | 40 ++++++++++++++++++++++++++++++++++++++++
>>  1 file changed, 40 insertions(+)
>>  create mode 100644 conf/machine/cfa10036.conf
>>
>> diff --git a/conf/machine/cfa10036.conf b/conf/machine/cfa10036.conf
>> new file mode 100644
>> index 0000000..7f2fe35
>> --- /dev/null
>> +++ b/conf/machine/cfa10036.conf
>> @@ -0,0 +1,40 @@
>> +#@TYPE: Machine
>> +#@NAME: Crystalfontz CFA-10036
>> +#@SOC: i.MX28
>> +#@DESCRIPTION: Machine configuration for CFA-10036
>> +
>> +include conf/machine/include/mxs-base.inc
>> +
>> +SOC_FAMILY = "mxs:mx28"
>> +
>> +PREFERRED_PROVIDER_virtual/kernel = "linux-cfa"
>> +PREFERRED_VERSION_imx-bootlets = "cfa"
>> +
>> +BAREBOX_MACHINE = "cfa10036_defconfig"
>> +IMAGE_BOOTLOADER = "barebox"
>> +BAREBOX_BINARY = "barebox"
>> +
>> +IMXBOOTLETS_MACHINE = "cfa10036"
>> +BOOT_SPACE="32768"
>> +
>> +KERNEL_IMAGETYPE = "zImage"
>> +KERNEL_DEVICETREE = "${S}/arch/arm/boot/dts/imx28-cfa10036.dts"
> imx28-cfa10036.dtb ...
>
> No full path.

Oh yeah, and I saw that in linux-dtb.inc but didn't react on it. I would
be expecting a warning there with:

bbwarn "${DTB} contains the full path to the the dts file, but only the
dtb name should be used."

but didn't get any.



-- 
Alexandre Belloni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

Re: [meta-fsl-arm-extra][PATCH 4/4] cfa10036: Add cfa10036 machine configuration

[Otavio Salvador]

On Thu, Aug 22, 2013 at 2:12 PM, Alexandre Belloni
<alexandre.belloni@free-electrons.com> wrote:
...
>>> +KERNEL_IMAGETYPE = "zImage"
>>> +KERNEL_DEVICETREE = "${S}/arch/arm/boot/dts/imx28-cfa10036.dts"
>> imx28-cfa10036.dtb ...
>>
>> No full path.
>
> Oh yeah, and I saw that in linux-dtb.inc but didn't react on it. I would
> be expecting a warning there with:
>
> bbwarn "${DTB} contains the full path to the the dts file, but only the
> dtb name should be used."
>
> but didn't get any.

In the log files inside temp/log.* :D

-- 
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: [meta-fsl-arm-extra][PATCH 0/4] Add support for CrystalFontz boards

[Alexandre Belloni]

Otavio,

I forgot to add, this series depends on the two previous patches:
 - mx28-bcb: add utility to generate Boot Control Block
 - image_types_fsl: mxs: Add support for a barebox bootstream

Regards,

On 22/08/2013 16:51, Alexandre Belloni wrote:
> The following series adds support for the various CrystalFontz boards:
>  cfa-10036
>  cfa-10037
>  cfa-10049
>  cfa-10055
>  cfa-10056
>  cfa-10057
>  cfa-10058
>
> The first patch adds support for a mainline barebox, here 2013.08.
>
> The second patch add support for the cfa specific version of the bootlets,
> including a patch to be able to use barebox as the payload. We may want to
> factorize a bit more the imx-bootlets recipes though.
>
> The third patch adds a recipe for the cfa kernel, based on 3.10.
>
> The last patch adds the machine configuration. It is named cfa10036 as this is the base for all the other boards.
>
> Alexandre Belloni (4):
>   barebox: add a recipe to support mainline 2013.08.0
>   imx-bootlets: add a recipe for barebox and cfa-10036 support
>   linux-cfa: add a kernel recipe supporting Crystalfontz boards
>   cfa10036: Add cfa10036 machine configuration
>
>  conf/machine/cfa10036.conf                         |  40 +++++
>  recipes-bsp/barebox/barebox_2013.08.0.bb           |  26 +++
>  .../imx-bootlets/barebox-fix-paths.patch           |  35 ++++
>  recipes-bsp/imx-bootlets/imx-bootlets_cfa.bb       |  65 ++++++++
>  recipes-kernel/linux/linux-cfa-3.10/defconfig      | 177 +++++++++++++++++++++
>  recipes-kernel/linux/linux-cfa_3.10.bb             |  33 ++++
>  6 files changed, 376 insertions(+)
>  create mode 100644 conf/machine/cfa10036.conf
>  create mode 100644 recipes-bsp/barebox/barebox_2013.08.0.bb
>  create mode 100644 recipes-bsp/imx-bootlets/imx-bootlets/barebox-fix-paths.patch
>  create mode 100644 recipes-bsp/imx-bootlets/imx-bootlets_cfa.bb
>  create mode 100644 recipes-kernel/linux/linux-cfa-3.10/defconfig
>  create mode 100644 recipes-kernel/linux/linux-cfa_3.10.bb
>


-- 
Alexandre Belloni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

Re: [meta-fsl-arm-extra][PATCH 0/4] Add support for CrystalFontz boards

[Otavio Salvador]

On Thu, Aug 22, 2013 at 11:52 AM, Alexandre Belloni
<alexandre.belloni@free-electrons.com> wrote:
> Otavio,
>
> I forgot to add, this series depends on the two previous patches:
>  - mx28-bcb: add utility to generate Boot Control Block
>  - image_types_fsl: mxs: Add support for a barebox bootstream

The barebox and imx-bootlets changes for barebox support should be
sent to fsl-arm. I will comment in each patch :)

-- 
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