Re: [meta-freescale] [meta-fsl-arm-extra][PATCH v2 1/3] cgtqmx6: Update Congatec-QMX6 machine configuration

2014-08-20 Thread Alejandro . de-cabo-Garcia
Hi Otavio,

 Hello Alex,
 
 On Wed, Aug 20, 2014 at 5:51 AM, Alex de Cabo
 alejandro.de-cabo-gar...@congatec.com wrote:
  Update config file:
 
  * Preferred kernel version: 3.10.17
  * Preferred uboot version: 2013.04
 
 These two are not need as the 3.10.17 is indeed newer than the 3.0.35
 and the u-boot is a single provider.

Ok, I will remove the Preferred_version for both and also remove the old 
kernel and u-boot recipes, keeping just 3.10.17 and 2013.08

 
  * Set build image: tar.bz2
 
 Do you not intend to have users using the sdcard?
 

In order to save building time I just generate the tar.bz2 and then untar 
it into the sdcard. I will remove it.


  * Append firmware for Solo and DualLite: imx-vpu-imx6d
 
 Check how we did for cubox-i; it has support for a single rootfs for 
QDL.
 

Done.

  * Variable PARTNUMBER have to be specified according to the module
  partnumber. The possible values are:
  PN016100, PN016101, PN016102, PN016103, PN016104, PN016105, PN016106,
  PN016110, PN016111, PN016112, PN016113
 
 Can you clarify why?
 
 -- 
 Otavio Salvador O.S. Systems
 http://www.ossystems.com.brhttp://code.ossystems.com.br
 Mobile: +55 (53) 9981-7854Mobile: +1 (347) 903-9750
-- 
___
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale


Re: [meta-freescale] [meta-fsl-arm-extra][PATCH v2 2/3] cgtqmx6: Update Congatec-QMX6 bootloader support

2014-08-20 Thread Alejandro . de-cabo-Garcia
Hi Otavio,

 On Wed, Aug 20, 2014 at 5:52 AM, Alex de Cabo
 alejandro.de-cabo-gar...@congatec.com wrote:
  Provides the recipes and patches to use 2009.08 or 2013.04 U-boot
  versions.
 
  Signed-off-by: Alex de Cabo alejandro.de-cabo-gar...@congatec.com
 
 Now I understand better.
 
 Is there any reason to keep the old U-Boot here? I don't think it is
 worth keep several providers without a good reason.

Not really, I will remove the 2009.08 recipe.

 
  ---
   recipes-bsp/u-boot/u-boot-qmx6/boot.scr|  3 +
   .../u-boot/u-boot-qmx6/cgtqmx6/PN016100.patch  | 13 
   .../u-boot/u-boot-qmx6/cgtqmx6/PN016101.patch  | 13 
   .../u-boot/u-boot-qmx6/cgtqmx6/PN016102.patch  | 13 
   .../u-boot/u-boot-qmx6/cgtqmx6/PN016103.patch  | 13 
   .../u-boot/u-boot-qmx6/cgtqmx6/PN016104.patch  | 13 
   .../u-boot/u-boot-qmx6/cgtqmx6/PN016105.patch  | 13 
   .../u-boot/u-boot-qmx6/cgtqmx6/PN016106.patch  | 13 
   .../u-boot/u-boot-qmx6/cgtqmx6/PN016110.patch  | 13 
   .../u-boot/u-boot-qmx6/cgtqmx6/PN016111.patch  | 13 
   .../u-boot/u-boot-qmx6/cgtqmx6/PN016112.patch  | 13 
   .../u-boot/u-boot-qmx6/cgtqmx6/PN016113.patch  | 13 
 
 The easiest to maintain, and standard mechanism for this kind of
 situation is the UBOOT_CONFIG.
 
 So the best alternative is you to have different U-Boot config files
 for each part number and user can set it in local.conf to build.
 
 We also need one default (which I think can be the latest) so it can
 be tested, automatically when needed.
 

I will set a default PARTNUBMER 

 ...
  diff --git a/recipes-bsp/u-boot/u-boot-qmx6/boot.scr b/recipes-
 bsp/u-boot/u-boot-qmx6/boot.scr
  new file mode 100644
  index 000..ee06444
  --- /dev/null
  +++ b/recipes-bsp/u-boot/u-boot-qmx6/boot.scr
  @@ -0,0 +1,3 @@
  +set bootargs $bootargs root=/dev/mmcblk0p1 rootwait rw fixrtc ;
  +   fsload mmc ${disk}:1 1080 /boot/uImage  bootm 1080 ;
  +   echo Error loading kernel image
 
 Where is documented the way to generate the SD card or eMMC?
 

Nowhere, where should I add it?

 ...
  diff --git a/recipes-bsp/u-boot/u-boot-qmx6_2013.04.bb b/recipes-
 bsp/u-boot/u-boot-qmx6_2013.04.bb
  new file mode 100644
  index 000..3eabf20
  --- /dev/null
  +++ b/recipes-bsp/u-boot/u-boot-qmx6_2013.04.bb
  @@ -0,0 +1,37 @@
  +# Congatec QMX6 u-boot
  +
  +require recipes-bsp/u-boot/u-boot.inc
  +
  +LICENSE = GPLv2+
  +LIC_FILES_CHKSUM = 
file://COPYING;md5=1707d6db1d42237583f50183a5651ecb
  +
  +
  +PROVIDES += u-boot
  +
  +PV = 2013.04
  +
  +SRCREV = 6388c474189b42c07bb865dd604c74483da099f3
  +CGTBRANCH = cgt_imx_v2013.04_3.10.17_1.0.0
 
 All our code user SRCBRANCH, please use the same here.
 

Ok

  +SRC_URI = git://git.congatec.com/arm/
 qmx6_uboot.git;protocol=http;branch=${CGTBRANCH} \
  +
  +
  +UBOOT_MACHINE = cgt_qmx6_`echo ${PARTNUMBER} | tr '[:upper:]' 
 '[:lower:]' `_config
  +UBOOT_MAKE_TARGET = u-boot.`echo ${PARTNUMBER} | tr '[:upper:]'
 '[:lower:]'`.imx
  +
  +S = ${WORKDIR}/git
  +EXTRA_OEMAKE += 'HOSTSTRIP=true'
  +
  +do_compile_prepend() {
  +if [ ${@base_contains('DISTRO_FEATURES', 'ld-is-gold', 
 'ld-is-gold', '', d)} = ld-is-gold ] ; then
  +sed -i 's/$(CROSS_COMPILE)ld/$(CROSS_COMPILE)
 ld.bfd/g' config.mk
  +fi
  +}
  +
  +do_deploy () {
  +install ${S}/${UBOOT_MAKE_TARGET} \
  +${DEPLOYDIR}/
  +}
  +
  +PACKAGE_ARCH = ${MACHINE_ARCH}
  +COMPATIBLE_MACHINE = (cgtqmx6)
 
 The do_compile_prepend and do_deploy seem not needed.
 
 If you look at  the recipe of FSL U-Boot[1] it is much cleaner so
 please clean this recipe as much as possible as this easy the metadata
 maintenance.
 
 1. http://git.yoctoproject.org/cgit/cgit.cgi/meta-fsl-arm/tree/
 recipes-bsp/u-boot/u-boot-imx_2013.04.bb
 

I will clean the u-boot and kernel recipe, remove the old files, 
create a v3 patches and send them back.


 
 -- 
 Otavio Salvador O.S. Systems
 http://www.ossystems.com.brhttp://code.ossystems.com.br
 Mobile: +55 (53) 9981-7854Mobile: +1 (347) 903-9750
-- 
___
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale


Re: [meta-freescale] [meta-fsl-arm-extra][PATCH v3 2/4] cgtqmx6: Update Congatec-QMX6 bootloader support

2014-09-04 Thread Alejandro . de-cabo-Garcia
Hi Fabio,


Just curious: why don't you use mainline U-boot instead?


It was a internal decision.-- 
___
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale


Re: [meta-freescale] [meta-fsl-arm-extra][PATCH v3 1/4] cgtqmx6: Update Congatec-QMX6 machine configuration

2014-09-04 Thread Alejandro . de-cabo-Garcia
 
  Due to decisions we've taken, having only one partition, for now
  I would like to keep it as it is.
 
  Anyway I will think about this in the near future.
 
 Does your generated .sdcard image works?
 

To make it work I have to change those three U-boot environment variables 
with:

setenv loadfdt 'fatload mmc ${mmcdev}:${mmcpart} ${fdt_addr} ${fdt_file}'

setenv loaduimage 'fatload mmc ${mmcdev}:${mmcpart} ${loadaddr} ${uimage}'

setenv mmcroot '/dev/mmcblk0p2 rootwait rw'


By default we have only one partition, installing the uImage and the dts 
files into
the /boot folder. 

I don't like to have now two different structures for our customers, 
that's why I 
want to keep the old one.

Even with that I could add some small description to make the sdcard file 
works.

What do you think?-- 
___
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale


[meta-freescale] Yocto 1.7: u-boot-imx 2009.08 error

2014-11-19 Thread Alejandro . de-cabo-Garcia
Hi,

I am trying to bitbake the u-boot-imx 2009.08 for imx6qsabresd, but I get 
this error:

fatal error: gnu/stubs-soft.h: No such file or directory

and bitbake output: http://pastebin.com/Fj0UZaCj

do you have any idea that could help me?


thanks in advance,
alex-- 
___
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale


Re: [meta-freescale] [meta-fsl-arm-extra][PATCH] 2/3] qmx6-addons-gpio: Add gpio.sh configuration script

2015-02-03 Thread Alejandro . de-cabo-Garcia
Hi Otavio,
 
 It seems for me this could be better if documented in the Congatec's
 documentation or even in the Release Notes (adding Daiane on Cc so she
 can comment if she thinks this applies or not).
 
 The biggest problem I see with this kind of script is that it will
 always be changed by the user and end not being tracked.
 
 What do you think?


I see your point and I agree, we cannot track the changes, so I will 
include the script in the Congatec's documentation.
-- 
___
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale


Re: [meta-freescale] linux-congatec (fido) silent after Starting kernel ...

2015-05-27 Thread Alejandro . de-cabo-Garcia
Hi,

 
 I am trying to understand why the higher FDT address would help. 
 Where does the kernel extract to upon start?

loadaddr=0x1200


Kind regards,
alex.-- 
___
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale


Re: [meta-freescale] linux-congatec (fido) silent after Starting kernel ...

2015-05-22 Thread Alejandro . de-cabo-Garcia
Hi Leon,

could you try to set the following fdt loading address:

setenv fdt_addr 0x1800


Regards,
alex.-- 
___
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale


Re: [meta-freescale] [CRITICAL] Boards failing to build with GCC 5.2 - Kernel patches are needed

2015-11-11 Thread Alejandro . de-cabo-Garcia
Hi Otavio,

> Following patches are worth checking:

The patches applied here smoothly. I was out of the office.

I will test the good behaviour of the system and if so, 
I will send the patches to the meta-fsl-arm-extra as latest
next week.

Thanks.

Alex de Cabo.-- 
___
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale


Re: [meta-freescale] [3rdparty][master][PATCH 2/2] cgtqmx6: Change default kernel version

2017-02-09 Thread Alejandro . de-cabo-Garcia
> >  KERNEL_DEVICETREE = "imx6q-qmx6.dtb imx6dl-qmx6.dtb"
> >  KERNEL_IMAGETYPE = "zImage"
> >
> >  SERIAL_CONSOLE = "115200 ttymxc1"
> >
> >  MACHINE_FEATURES += " pci"
> > +MACHINE_HAS_VIVANTE_KERNEL_DRIVER_SUPPORT_cgtqmx6 = "1"
> > +MACHINE_USES_VIVANTE_KERNEL_DRIVER_MODULE_cgtqmx6 = "0"
> 
> Why?

In our default defconfig, the vivante module is set as a built-in. But I 
don't see any problem having it as a external module. So you can omit this 
patch.
-- 
___
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale