[meta-fsl-arm-extra][PATCH 0/3] add support for Toradex Vybrid modules

[meta-fsl-arm-extra][PATCH 0/3] add support for Toradex Vybrid modules

[Stefan Agner]

This patchset adds support for Toradex Colibri VF50/VF61 modules.
The sources of U-Boot and the Linux kernel are directly fetched from
our git server (located at git.toradex.com). The patchset uses the
source level of our V2.3 Beta 7 release.

Stefan Agner (3):
  u-boot-toradex: initial U-Boot recipe for Toradex Vybrid modules
  linux-toradex: initial Linux recipe for Toradex Vybrid modules
  colibri-vf: initial machine for Toradex Vybrid modules

 conf/machine/colibri-vf.conf                      |  36 ++++
 recipes-bsp/u-boot/u-boot-toradex.inc             |  26 +++
 recipes-bsp/u-boot/u-boot-toradex_2014.10.bb      |   7 +
 recipes-kernel/linux/linux-toradex-3.18/defconfig | 247 ++++++++++++++++++++++
 recipes-kernel/linux/linux-toradex_3.18.bb        |  13 ++
 5 files changed, 329 insertions(+)
 create mode 100644 conf/machine/colibri-vf.conf
 create mode 100644 recipes-bsp/u-boot/u-boot-toradex.inc
 create mode 100644 recipes-bsp/u-boot/u-boot-toradex_2014.10.bb
 create mode 100644 recipes-kernel/linux/linux-toradex-3.18/defconfig
 create mode 100644 recipes-kernel/linux/linux-toradex_3.18.bb

-- 
1.9.3

[meta-fsl-arm-extra][PATCH 1/3] u-boot-toradex: initial U-Boot recipe for Toradex Vybrid modules

[Stefan Agner]

This adds recipes for U-Boot supporting Toradex modules. The source
is fetched directly from our Git server at git.toradex.com. This
initial version supports the Freescale Vybrid based modules
Colibri VF50 and VF61.

Signed-off-by: Stefan Agner <stefan.agner@toradex.com>
---
 recipes-bsp/u-boot/u-boot-toradex.inc        | 26 ++++++++++++++++++++++++++
 recipes-bsp/u-boot/u-boot-toradex_2014.10.bb |  7 +++++++
 2 files changed, 33 insertions(+)
 create mode 100644 recipes-bsp/u-boot/u-boot-toradex.inc
 create mode 100644 recipes-bsp/u-boot/u-boot-toradex_2014.10.bb

diff --git a/recipes-bsp/u-boot/u-boot-toradex.inc b/recipes-bsp/u-boot/u-boot-toradex.inc
new file mode 100644
index 0000000..57ae547
--- /dev/null
+++ b/recipes-bsp/u-boot/u-boot-toradex.inc
@@ -0,0 +1,26 @@
+# Copyright (C) 2015 Toradex AG
+# Based on u-boot-fslc.inc Copyright (C) 2012-2014 O.S. Systems Software LTDA
+# Released under the MIT license (see COPYING.MIT for the terms)
+
+require recipes-bsp/u-boot/u-boot.inc
+
+inherit fsl-u-boot-localversion
+
+SUMMARY = "U-Boot bootloader with support for Toradex Computer on Modules"
+LICENSE = "GPLv2+"
+LIC_FILES_CHKSUM = "file://Licenses/README;md5=c7383a594871c03da76b3707929d2919"
+
+PROVIDES += "u-boot"
+
+SRC_URI = "git://git.toradex.com/u-boot-toradex.git;branch=${SRCBRANCH}"
+
+S = "${WORKDIR}/git"
+
+# FIXME: Allow linking of 'tools' binaries with native libraries
+#        used for generating the boot logo and other tools used
+#        during the build process.
+EXTRA_OEMAKE += 'HOSTCC="${BUILD_CC} ${BUILD_CPPFLAGS}" \
+                 HOSTLDFLAGS="${BUILD_LDFLAGS}" \
+                 HOSTSTRIP=true'
+
+PACKAGE_ARCH = "${MACHINE_ARCH}"
diff --git a/recipes-bsp/u-boot/u-boot-toradex_2014.10.bb b/recipes-bsp/u-boot/u-boot-toradex_2014.10.bb
new file mode 100644
index 0000000..ecd1829
--- /dev/null
+++ b/recipes-bsp/u-boot/u-boot-toradex_2014.10.bb
@@ -0,0 +1,7 @@
+include u-boot-toradex.inc
+
+PV = "v2014.10+git${SRCPV}"
+
+SRCREV = "73b99ed96be527c482e63f8d0aac4e6188b1f7e0"
+SRCBRANCH = "2014.10-toradex"
+COMPATIBLE_MACHINE = "(vf)"
-- 
1.9.3

[meta-fsl-arm-extra][PATCH 2/3] linux-toradex: initial Linux recipe for Toradex Vybrid modules

[Stefan Agner]

This Kernel recipe builds the kernel.org based Linux kernel 3.18
for the Freescale Vybrid based modules Colibri VF50 and VF61 of
Toradex.

The kernel.org based Linux kernel support this modules too since
~3.17. However, some patches, such as the NAND flash controller
driver, Display Controller Unit (DCU4) frambuffer driver and
various fixes across different drivers, are still in the process
of being upstreamed.

Signed-off-by: Stefan Agner <stefan.agner@toradex.com>
---
 recipes-kernel/linux/linux-toradex-3.18/defconfig | 247 ++++++++++++++++++++++
 recipes-kernel/linux/linux-toradex_3.18.bb        |  13 ++
 2 files changed, 260 insertions(+)
 create mode 100644 recipes-kernel/linux/linux-toradex-3.18/defconfig
 create mode 100644 recipes-kernel/linux/linux-toradex_3.18.bb

diff --git a/recipes-kernel/linux/linux-toradex-3.18/defconfig b/recipes-kernel/linux/linux-toradex-3.18/defconfig
new file mode 100644
index 0000000..e9fc673
--- /dev/null
+++ b/recipes-kernel/linux/linux-toradex-3.18/defconfig
@@ -0,0 +1,247 @@
+CONFIG_KERNEL_LZO=y
+CONFIG_SYSVIPC=y
+CONFIG_FHANDLE=y
+CONFIG_NO_HZ=y
+CONFIG_HIGH_RES_TIMERS=y
+CONFIG_LOG_BUF_SHIFT=18
+CONFIG_CGROUPS=y
+CONFIG_RELAY=y
+CONFIG_BLK_DEV_INITRD=y
+CONFIG_RD_GZIP=y
+CONFIG_RD_LZO=y
+CONFIG_RD_LZ4=y
+CONFIG_KALLSYMS_ALL=y
+CONFIG_EMBEDDED=y
+CONFIG_PERF_EVENTS=y
+# CONFIG_SLUB_DEBUG is not set
+# CONFIG_COMPAT_BRK is not set
+CONFIG_MODULES=y
+CONFIG_MODULE_UNLOAD=y
+CONFIG_MODVERSIONS=y
+CONFIG_MODULE_SRCVERSION_ALL=y
+# CONFIG_BLK_DEV_BSG is not set
+CONFIG_ARCH_MXC=y
+CONFIG_SOC_VF610=y
+CONFIG_SWP_EMULATE=y
+CONFIG_PL310_ERRATA_588369=y
+CONFIG_PL310_ERRATA_727915=y
+CONFIG_ARM_ERRATA_754322=y
+CONFIG_ARM_ERRATA_775420=y
+CONFIG_VMSPLIT_2G=y
+CONFIG_PREEMPT_VOLUNTARY=y
+CONFIG_AEABI=y
+CONFIG_CMA=y
+CONFIG_CPU_IDLE=y
+# CONFIG_CPU_IDLE_GOV_LADDER is not set
+CONFIG_VFP=y
+CONFIG_NEON=y
+CONFIG_KERNEL_MODE_NEON=y
+CONFIG_PM_RUNTIME=y
+CONFIG_NET=y
+CONFIG_PACKET=y
+CONFIG_UNIX=y
+CONFIG_INET=y
+CONFIG_IP_PNP=y
+CONFIG_IP_PNP_DHCP=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_IPV6=y
+CONFIG_NETFILTER=y
+CONFIG_CAN=y
+CONFIG_CAN_FLEXCAN=y
+CONFIG_CFG80211=y
+CONFIG_MAC80211=y
+CONFIG_RFKILL=y
+CONFIG_RFKILL_INPUT=y
+CONFIG_DEVTMPFS=y
+CONFIG_DEVTMPFS_MOUNT=y
+# CONFIG_STANDALONE is not set
+CONFIG_DMA_CMA=y
+CONFIG_CONNECTOR=y
+CONFIG_MTD=y
+CONFIG_MTD_CMDLINE_PARTS=y
+CONFIG_MTD_BLOCK=y
+CONFIG_MTD_JEDECPROBE=y
+CONFIG_MTD_PHYSMAP_OF=y
+CONFIG_MTD_NAND=y
+CONFIG_MTD_NAND_FSL_NFC=y
+CONFIG_MTD_SPI_NOR=y
+CONFIG_MTD_UBI=y
+CONFIG_MTD_UBI_FASTMAP=y
+CONFIG_BLK_DEV_LOOP=y
+CONFIG_BLK_DEV_RAM=y
+CONFIG_BLK_DEV_RAM_SIZE=65536
+CONFIG_SCSI=y
+# CONFIG_SCSI_PROC_FS is not set
+CONFIG_BLK_DEV_SD=y
+CONFIG_SCSI_CONSTANTS=y
+CONFIG_SCSI_LOGGING=y
+CONFIG_SCSI_SCAN_ASYNC=y
+# CONFIG_SCSI_LOWLEVEL is not set
+CONFIG_NETDEVICES=y
+# CONFIG_NET_VENDOR_ARC is not set
+# CONFIG_NET_CADENCE is not set
+# CONFIG_NET_VENDOR_BROADCOM is not set
+# CONFIG_NET_VENDOR_CIRRUS is not set
+# CONFIG_NET_VENDOR_FARADAY is not set
+# CONFIG_NET_VENDOR_HISILICON is not set
+# CONFIG_NET_VENDOR_INTEL is not set
+# CONFIG_NET_VENDOR_MARVELL is not set
+# CONFIG_NET_VENDOR_MICREL is not set
+# CONFIG_NET_VENDOR_NATSEMI is not set
+# CONFIG_NET_VENDOR_QUALCOMM is not set
+# CONFIG_NET_VENDOR_SAMSUNG is not set
+# CONFIG_NET_VENDOR_SEEQ is not set
+# CONFIG_NET_VENDOR_SMSC is not set
+# CONFIG_NET_VENDOR_STMICRO is not set
+# CONFIG_NET_VENDOR_VIA is not set
+# CONFIG_NET_VENDOR_WIZNET is not set
+CONFIG_MICREL_PHY=y
+CONFIG_INPUT_POLLDEV=y
+# CONFIG_INPUT_MOUSEDEV_PSAUX is not set
+CONFIG_INPUT_EVDEV=y
+CONFIG_KEYBOARD_GPIO=y
+CONFIG_KEYBOARD_IMX=y
+# CONFIG_MOUSE_PS2 is not set
+CONFIG_INPUT_TOUCHSCREEN=y
+CONFIG_TOUCHSCREEN_EGALAX=y
+CONFIG_TOUCHSCREEN_WM97XX=y
+# CONFIG_TOUCHSCREEN_WM9705 is not set
+# CONFIG_TOUCHSCREEN_WM9713 is not set
+CONFIG_TOUCHSCREEN_STMPE=y
+CONFIG_TOUCHSCREEN_COLIBRI_VF50=y
+# CONFIG_LEGACY_PTYS is not set
+# CONFIG_DEVKMEM is not set
+CONFIG_SERIAL_FSL_LPUART=y
+CONFIG_SERIAL_FSL_LPUART_CONSOLE=y
+CONFIG_HW_RANDOM=y
+# CONFIG_I2C_COMPAT is not set
+CONFIG_I2C_CHARDEV=y
+# CONFIG_I2C_HELPER_AUTO is not set
+CONFIG_I2C_ALGOBIT=y
+CONFIG_I2C_IMX=y
+CONFIG_SPI=y
+CONFIG_SPI_FSL_DSPI=y
+CONFIG_SPI_SPIDEV=y
+CONFIG_GPIO_SYSFS=y
+CONFIG_POWER_SUPPLY=y
+CONFIG_POWER_RESET=y
+CONFIG_POWER_RESET_SYSCON=y
+# CONFIG_HWMON is not set
+CONFIG_WATCHDOG=y
+CONFIG_IMX2_WDT=y
+CONFIG_MFD_STMPE=y
+CONFIG_REGULATOR=y
+CONFIG_REGULATOR_FIXED_VOLTAGE=y
+CONFIG_REGULATOR_ANATOP=y
+CONFIG_REGULATOR_GPIO=y
+CONFIG_MEDIA_SUPPORT=y
+CONFIG_MEDIA_CAMERA_SUPPORT=y
+CONFIG_MEDIA_RC_SUPPORT=y
+# CONFIG_RC_MAP is not set
+# CONFIG_RC_DECODERS is not set
+CONFIG_MEDIA_USB_SUPPORT=y
+CONFIG_USB_VIDEO_CLASS=y
+# CONFIG_USB_GSPCA is not set
+CONFIG_FB=y
+CONFIG_FB_FSL_DCU=y
+CONFIG_BACKLIGHT_LCD_SUPPORT=y
+# CONFIG_LCD_CLASS_DEVICE is not set
+CONFIG_BACKLIGHT_CLASS_DEVICE=y
+# CONFIG_BACKLIGHT_GENERIC is not set
+CONFIG_BACKLIGHT_PWM=y
+CONFIG_BACKLIGHT_GPIO=y
+CONFIG_FRAMEBUFFER_CONSOLE=y
+CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY=y
+CONFIG_LOGO=y
+# CONFIG_LOGO_LINUX_MONO is not set
+# CONFIG_LOGO_LINUX_VGA16 is not set
+CONFIG_SOUND=y
+CONFIG_SND=y
+CONFIG_SND_SOC=y
+CONFIG_SND_IMX_SOC=y
+CONFIG_SND_SOC_FSL_SAI_WM9712=y
+CONFIG_SND_SOC_IMX_SGTL5000=y
+CONFIG_USB=y
+CONFIG_USB_EHCI_HCD=y
+CONFIG_USB_STORAGE=y
+CONFIG_USB_CHIPIDEA=y
+CONFIG_USB_CHIPIDEA_UDC=y
+CONFIG_USB_CHIPIDEA_HOST=y
+CONFIG_USB_SERIAL=y
+CONFIG_NOP_USB_XCEIV=y
+CONFIG_USB_MXS_PHY=y
+CONFIG_USB_GADGET=y
+CONFIG_USB_FSL_USB2=y
+CONFIG_USB_ETH=y
+CONFIG_MMC=y
+CONFIG_MMC_SDHCI=y
+CONFIG_MMC_SDHCI_PLTFM=y
+CONFIG_MMC_SDHCI_ESDHC_IMX=y
+CONFIG_NEW_LEDS=y
+CONFIG_LEDS_CLASS=y
+CONFIG_LEDS_GPIO=y
+CONFIG_LEDS_TRIGGERS=y
+CONFIG_LEDS_TRIGGER_TIMER=y
+CONFIG_LEDS_TRIGGER_ONESHOT=y
+CONFIG_LEDS_TRIGGER_HEARTBEAT=y
+CONFIG_LEDS_TRIGGER_BACKLIGHT=y
+CONFIG_LEDS_TRIGGER_GPIO=y
+CONFIG_RTC_CLASS=y
+CONFIG_RTC_DRV_DS1307=y
+CONFIG_RTC_DRV_SNVS=y
+CONFIG_DMADEVICES=y
+# CONFIG_MX3_IPU is not set
+CONFIG_FSL_EDMA=y
+# CONFIG_IOMMU_SUPPORT is not set
+CONFIG_IIO=y
+CONFIG_IIO_TRIGGER=y
+CONFIG_VF610_ADC=y
+CONFIG_PWM=y
+CONFIG_PWM_FSL_FTM=y
+CONFIG_EXT3_FS=y
+CONFIG_EXT3_FS_POSIX_ACL=y
+CONFIG_EXT3_FS_SECURITY=y
+CONFIG_EXT4_FS=y
+CONFIG_EXT4_FS_POSIX_ACL=y
+CONFIG_EXT4_FS_SECURITY=y
+CONFIG_QUOTA=y
+CONFIG_QUOTA_NETLINK_INTERFACE=y
+# CONFIG_PRINT_QUOTA_WARNING is not set
+CONFIG_AUTOFS4_FS=y
+CONFIG_FUSE_FS=y
+CONFIG_OVERLAY_FS=y
+CONFIG_VFAT_FS=y
+CONFIG_NTFS_FS=y
+CONFIG_NTFS_RW=y
+CONFIG_TMPFS=y
+CONFIG_UBIFS_FS=y
+CONFIG_NFS_FS=y
+CONFIG_NFS_V3_ACL=y
+CONFIG_NFS_V4=y
+CONFIG_NFS_V4_1=y
+CONFIG_NFS_V4_2=y
+CONFIG_ROOT_NFS=y
+CONFIG_NLS_DEFAULT="cp437"
+CONFIG_NLS_CODEPAGE_437=y
+CONFIG_NLS_ASCII=y
+CONFIG_NLS_ISO8859_1=y
+CONFIG_NLS_UTF8=y
+CONFIG_PRINTK_TIME=y
+CONFIG_DEBUG_FS=y
+CONFIG_LOCKUP_DETECTOR=y
+CONFIG_DEFAULT_HUNG_TASK_TIMEOUT=10
+# CONFIG_SCHED_DEBUG is not set
+CONFIG_STACKTRACE=y
+# CONFIG_DEBUG_BUGVERBOSE is not set
+# CONFIG_FTRACE is not set
+# CONFIG_ARM_UNWIND is not set
+CONFIG_SECURITYFS=y
+# CONFIG_CRYPTO_ANSI_CPRNG is not set
+# CONFIG_CRYPTO_HW is not set
+CONFIG_CRC_T10DIF=y
+CONFIG_FONTS=y
+CONFIG_FONT_8x8=y
+CONFIG_FONT_8x16=y
diff --git a/recipes-kernel/linux/linux-toradex_3.18.bb b/recipes-kernel/linux/linux-toradex_3.18.bb
new file mode 100644
index 0000000..a031d8e
--- /dev/null
+++ b/recipes-kernel/linux/linux-toradex_3.18.bb
@@ -0,0 +1,13 @@
+require recipes-kernel/linux/linux-imx.inc
+require recipes-kernel/linux/linux-dtb.inc
+
+SUMMARY = "Linux kernel for Toradex Colibri VFxx Computer on Modules"
+
+SRC_URI = "git://git.toradex.com/linux-toradex.git;protocol=git;branch=${SRCBRANCH} \
+           file://defconfig"
+
+LOCALVERSION = "-v2.3b7"
+SRCBRANCH = "toradex_vf_3.18"
+SRCREV = "c78b5ae472e69452d5fe44c261d57c8083c59f74"
+DEPENDS += "lzop-native bc-native"
+COMPATIBLE_MACHINE = "(vf)"
-- 
1.9.3

[meta-fsl-arm-extra][PATCH 3/3] colibri-vf: initial machine for Toradex Vybrid modules

[Stefan Agner]

The two modules Colibri VF50 and Colibri VF61 are very similar,
with this generic machine called "colibri-vf" both modules are
supported. The bootloader default environment expects the Linux
kernel zImage as well as the device tree files to be located in
the /boot folder of the root file system. Use IMAGE_INSTALL on
the machine level to install them into the root file system by
default.

Signed-off-by: Stefan Agner <stefan.agner@toradex.com>
---
 conf/machine/colibri-vf.conf | 36 ++++++++++++++++++++++++++++++++++++
 1 file changed, 36 insertions(+)
 create mode 100644 conf/machine/colibri-vf.conf

diff --git a/conf/machine/colibri-vf.conf b/conf/machine/colibri-vf.conf
new file mode 100644
index 0000000..f84abbc
--- /dev/null
+++ b/conf/machine/colibri-vf.conf
@@ -0,0 +1,36 @@
+#@TYPE: Machine
+#@NAME: Toradex Colibri VF50/VF61
+#@SOC: VF500/VF610
+#@DESCRIPTION: Machine configuration for Toradex Colibri VF50/VF61 powered by Freescale Vybrid SoC
+#@MAINTAINER: Stefan Agner <stefan.agner@toradex.com>
+
+include conf/machine/include/imx-base.inc
+include conf/machine/include/tune-cortexa5.inc
+
+SOC_FAMILY = "vf:vf50:vf60"
+
+PREFERRED_PROVIDER_virtual/kernel ?= "linux-toradex"
+KERNEL_IMAGETYPE = "zImage"
+KERNEL_DEVICETREE += "vf500-colibri-eval-v3.dtb vf610-colibri-eval-v3.dtb"
+
+# U-Boot expects the kernel and device tree directly in /boot of the rootfs
+IMAGE_INSTALL_append = " kernel-image kernel-devicetree"
+
+PREFERRED_PROVIDER_u-boot = "u-boot-toradex"
+PREFERRED_PROVIDER_virtual/bootloader = "u-boot-toradex"
+
+# U-Boot NAND binary includes 0x400 padding required for NAND boot
+UBOOT_BINARY = "u-boot-nand.imx"
+UBOOT_MAKE_TARGET = "u-boot-nand.imx"
+UBOOT_MACHINE = "colibri_vf_defconfig"
+
+IMAGE_FSTYPES = "tar.bz2 ubifs ubi"
+
+# Enable free --space-fixup (-F) by default, this allows DFU updates
+MKUBIFS_ARGS = " -c 8112 -e 124KiB -m 2KiB -F"
+UBINIZE_ARGS = " -p 128KiB -m 2048 -s 2048"
+UBI_VOLNAME = "rootfs"
+
+SERIAL_CONSOLE = "115200 ttyLP0"
+
+MACHINE_FEATURES = "apm usbgadget usbhost vfat alsa touchscreen"
-- 
1.9.3

Re: [meta-fsl-arm-extra][PATCH 3/3] colibri-vf: initial machine for Toradex Vybrid modules

[Otavio Salvador]

On Mon, Mar 9, 2015 at 5:46 AM, Stefan Agner <stefan.agner@toradex.com> wrote:
> The two modules Colibri VF50 and Colibri VF61 are very similar,
> with this generic machine called "colibri-vf" both modules are
> supported. The bootloader default environment expects the Linux
> kernel zImage as well as the device tree files to be located in
> the /boot folder of the root file system. Use IMAGE_INSTALL on
> the machine level to install them into the root file system by
> default.
>
> Signed-off-by: Stefan Agner <stefan.agner@toradex.com>
> ---
>  conf/machine/colibri-vf.conf | 36 ++++++++++++++++++++++++++++++++++++
>  1 file changed, 36 insertions(+)
>  create mode 100644 conf/machine/colibri-vf.conf
>
> diff --git a/conf/machine/colibri-vf.conf b/conf/machine/colibri-vf.conf
> new file mode 100644
> index 0000000..f84abbc
> --- /dev/null
> +++ b/conf/machine/colibri-vf.conf
> @@ -0,0 +1,36 @@
> +#@TYPE: Machine
> +#@NAME: Toradex Colibri VF50/VF61
> +#@SOC: VF500/VF610
> +#@DESCRIPTION: Machine configuration for Toradex Colibri VF50/VF61 powered by Freescale Vybrid SoC
> +#@MAINTAINER: Stefan Agner <stefan.agner@toradex.com>
> +
> +include conf/machine/include/imx-base.inc
> +include conf/machine/include/tune-cortexa5.inc
> +
> +SOC_FAMILY = "vf:vf50:vf60"

I agree with this however this imposes a change in imx-base.inc.
Please change the UBOOT_ENTRYPOINT for vf so it avoids the duplicated
definition. This also needs to add the vf in the SOC_FAMILY of Tower.

> +PREFERRED_PROVIDER_virtual/kernel ?= "linux-toradex"
> +KERNEL_IMAGETYPE = "zImage"
> +KERNEL_DEVICETREE += "vf500-colibri-eval-v3.dtb vf610-colibri-eval-v3.dtb"
> +
> +# U-Boot expects the kernel and device tree directly in /boot of the rootfs
> +IMAGE_INSTALL_append = " kernel-image kernel-devicetree"

Please use:

=== MACHINE_EXTRA_RDEPENDS
A list of machine-specific packages to install as part of the image
being built that are not essential for the machine to boot. However,
the build process for more fully-featured images depends on the
packages being present.

This variable affects all images based on `packagegroup-base`, which
does not include the `core-image-minimal` or `core-image-full-cmdline`
images.

The variable is similar to the `MACHINE_EXTRA_RRECOMMENDS` variable
with the exception that the image being built has a build dependency
on the variable's list of packages. In other words, the image will not
build if a file in this list is not found.

An example is a machine that has WiFi capability but is not essential
for the machine to boot the image. However, if you are building a more
fully-featured image, you want to enable the WiFi. The package
containing the firmware for the WiFi hardware is always expected to
exist, so it is acceptable for the build process to depend upon
finding the package. In this case, assuming the package for the
firmware was called `wifidriver-firmware`, you would use the following
in the `.conf` file for the machine:

     MACHINE_EXTRA_RDEPENDS += "wifidriver-firmware"

-- 
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/3] colibri-vf: initial machine for Toradex Vybrid modules

[Stefan Agner]

Hi Otavio,

On 09.03.2015 14:12, Otavio Salvador wrote:
> On Mon, Mar 9, 2015 at 5:46 AM, Stefan Agner <stefan.agner@toradex.com> wrote:
>> The two modules Colibri VF50 and Colibri VF61 are very similar,
>> with this generic machine called "colibri-vf" both modules are
>> supported. The bootloader default environment expects the Linux
>> kernel zImage as well as the device tree files to be located in
>> the /boot folder of the root file system. Use IMAGE_INSTALL on
>> the machine level to install them into the root file system by
>> default.
>>
>> Signed-off-by: Stefan Agner <stefan.agner@toradex.com>
>> ---
>>  conf/machine/colibri-vf.conf | 36 ++++++++++++++++++++++++++++++++++++
>>  1 file changed, 36 insertions(+)
>>  create mode 100644 conf/machine/colibri-vf.conf
>>
>> diff --git a/conf/machine/colibri-vf.conf b/conf/machine/colibri-vf.conf
>> new file mode 100644
>> index 0000000..f84abbc
>> --- /dev/null
>> +++ b/conf/machine/colibri-vf.conf
>> @@ -0,0 +1,36 @@
>> +#@TYPE: Machine
>> +#@NAME: Toradex Colibri VF50/VF61
>> +#@SOC: VF500/VF610
>> +#@DESCRIPTION: Machine configuration for Toradex Colibri VF50/VF61 powered by Freescale Vybrid SoC
>> +#@MAINTAINER: Stefan Agner <stefan.agner@toradex.com>
>> +
>> +include conf/machine/include/imx-base.inc
>> +include conf/machine/include/tune-cortexa5.inc
>> +
>> +SOC_FAMILY = "vf:vf50:vf60"
> I agree with this however this imposes a change in imx-base.inc.
> Please change the UBOOT_ENTRYPOINT for vf so it avoids the duplicated
> definition. This also needs to add the vf in the SOC_FAMILY of Tower.

Yep, makes sense, will include that change in v2.


>> +PREFERRED_PROVIDER_virtual/kernel ?= "linux-toradex"
>> +KERNEL_IMAGETYPE = "zImage"
>> +KERNEL_DEVICETREE += "vf500-colibri-eval-v3.dtb vf610-colibri-eval-v3.dtb"
>> +
>> +# U-Boot expects the kernel and device tree directly in /boot of the rootfs
>> +IMAGE_INSTALL_append = " kernel-image kernel-devicetree"
> Please use:
>
> === MACHINE_EXTRA_RDEPENDS
> A list of machine-specific packages to install as part of the image
> being built that are not essential for the machine to boot. However,
> the build process for more fully-featured images depends on the
> packages being present.

"not essential for the machine to boot", well, those are essential... At
least for NAND/SD boot. Theoretically its optional since the
kernel/device tree can also be fetched over the network, but that's not
the common use case.


>
> This variable affects all images based on `packagegroup-base`, which
> does not include the `core-image-minimal` or `core-image-full-cmdline`
> images.
>
> The variable is similar to the `MACHINE_EXTRA_RRECOMMENDS` variable
> with the exception that the image being built has a build dependency
> on the variable's list of packages. In other words, the image will not
> build if a file in this list is not found.
Currently I test with core-image-minimal. I guess this won't boot if I
use MACHINE_EXTRA_DEPENDS...

>
> An example is a machine that has WiFi capability but is not essential
> for the machine to boot the image. However, if you are building a more
> fully-featured image, you want to enable the WiFi. The package
> containing the firmware for the WiFi hardware is always expected to
> exist, so it is acceptable for the build process to depend upon
> finding the package. In this case, assuming the package for the
> firmware was called `wifidriver-firmware`, you would use the following
> in the `.conf` file for the machine:
>
>      MACHINE_EXTRA_RDEPENDS += "wifidriver-firmware"
>

--
Stefan

Re: [meta-fsl-arm-extra][PATCH 3/3] colibri-vf: initial machine for Toradex Vybrid modules

[Otavio Salvador]

On Mon, Mar 9, 2015 at 10:20 AM, Stefan Agner <stefan.agner@toradex.com> wrote:
> Hi Otavio,
>
> On 09.03.2015 14:12, Otavio Salvador wrote:
>> On Mon, Mar 9, 2015 at 5:46 AM, Stefan Agner <stefan.agner@toradex.com> wrote:
>>> The two modules Colibri VF50 and Colibri VF61 are very similar,
>>> with this generic machine called "colibri-vf" both modules are
>>> supported. The bootloader default environment expects the Linux
>>> kernel zImage as well as the device tree files to be located in
>>> the /boot folder of the root file system. Use IMAGE_INSTALL on
>>> the machine level to install them into the root file system by
>>> default.
>>>
>>> Signed-off-by: Stefan Agner <stefan.agner@toradex.com>
>>> ---
>>>  conf/machine/colibri-vf.conf | 36 ++++++++++++++++++++++++++++++++++++
>>>  1 file changed, 36 insertions(+)
>>>  create mode 100644 conf/machine/colibri-vf.conf
>>>
>>> diff --git a/conf/machine/colibri-vf.conf b/conf/machine/colibri-vf.conf
>>> new file mode 100644
>>> index 0000000..f84abbc
>>> --- /dev/null
>>> +++ b/conf/machine/colibri-vf.conf
>>> @@ -0,0 +1,36 @@
>>> +#@TYPE: Machine
>>> +#@NAME: Toradex Colibri VF50/VF61
>>> +#@SOC: VF500/VF610
>>> +#@DESCRIPTION: Machine configuration for Toradex Colibri VF50/VF61 powered by Freescale Vybrid SoC
>>> +#@MAINTAINER: Stefan Agner <stefan.agner@toradex.com>
>>> +
>>> +include conf/machine/include/imx-base.inc
>>> +include conf/machine/include/tune-cortexa5.inc
>>> +
>>> +SOC_FAMILY = "vf:vf50:vf60"
>> I agree with this however this imposes a change in imx-base.inc.
>> Please change the UBOOT_ENTRYPOINT for vf so it avoids the duplicated
>> definition. This also needs to add the vf in the SOC_FAMILY of Tower.
>
> Yep, makes sense, will include that change in v2.
>
>
>>> +PREFERRED_PROVIDER_virtual/kernel ?= "linux-toradex"
>>> +KERNEL_IMAGETYPE = "zImage"
>>> +KERNEL_DEVICETREE += "vf500-colibri-eval-v3.dtb vf610-colibri-eval-v3.dtb"
>>> +
>>> +# U-Boot expects the kernel and device tree directly in /boot of the rootfs
>>> +IMAGE_INSTALL_append = " kernel-image kernel-devicetree"
>> Please use:
>>
>> === MACHINE_EXTRA_RDEPENDS
>> A list of machine-specific packages to install as part of the image
>> being built that are not essential for the machine to boot. However,
>> the build process for more fully-featured images depends on the
>> packages being present.
>
> "not essential for the machine to boot", well, those are essential... At
> least for NAND/SD boot. Theoretically its optional since the
> kernel/device tree can also be fetched over the network, but that's not
> the common use case.

So:

=== MACHINE_ESSENTIAL_EXTRA_RDEPENDS
A list of required machine-specific packages to install as part of the
image being built. The build process depends on these packages being
present. Furthermore, because this is a "machine essential" variable,
the list of packages are essential for the machine to boot. The impact
of this variable affects images based on `packagegroup-core-boot`,
including the `core-image-minimal` image.

This variable is similar to the `MACHINE_ESSENTIAL_EXTRA_RRECOMMENDS`
variable with the exception that the image being built has a build
dependency on the variable's list of packages. In other words, the
image will not build if a file in this list is not found.

As an example, suppose the machine for which you are building requires
`example-init` to be run during boot to initialize the hardware. In
this case, you would use the following in the machine's `.conf`
configuration file:

     MACHINE_ESSENTIAL_EXTRA_RDEPENDS += "example-init"

-- 
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/3] add support for Toradex Vybrid modules

[Otavio Salvador]

Hello,

On Mon, Mar 9, 2015 at 5:46 AM, Stefan Agner <stefan.agner@toradex.com> wrote:
> This patchset adds support for Toradex Colibri VF50/VF61 modules.
> The sources of U-Boot and the Linux kernel are directly fetched from
> our git server (located at git.toradex.com). The patchset uses the
> source level of our V2.3 Beta 7 release.

Thanks for working on this. I really appreciate the work Toradex being
doing with Vybrid and I believe we can end moving some of this work to
meta-fsl-arm and improve the overall support for Vybrid.

The only remark I found is the one related to the machine file itself.
It will need a patch to fsl-arm to fix imx-base and Tower board but it
is trivial :-)

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