[meta-fsl-arm-extra][PATCH 0/3] add Toradex i.MX 6 based modules

[meta-fsl-arm-extra][PATCH 0/3] add Toradex i.MX 6 based modules

[Max Krummenacher]

Hello

The patchset adds two new machines, apalis-imx6 and colibri-imx6, together
with U-Boot and kernel for Toradex i.MX6 based modules.

The patches apply on top of meta-fsl-arm-extra master.
The idea is that if they are accepted to also apply them for jethro.

Regards
Max


Max Krummenacher (3):
  u-boot-toradex: add U-Boot recipe for Toradex i.MX 6 based modules
  linux-toradex: add Linux recipe for Toradex i.MX 6 based modules
  apalis-imx6/colibri-imx6: add machine configuration

 conf/machine/apalis-imx6.conf                      |  29 ++
 conf/machine/colibri-imx6.conf                     |  22 ++
 recipes-bsp/u-boot/u-boot-toradex_2015.04.bb       |   2 +-
 .../linux-toradex-3.14.28/apalis-imx6/defconfig    | 364 +++++++++++++++++++++
 .../linux-toradex-3.14.28/colibri-imx6/defconfig   | 356 ++++++++++++++++++++
 recipes-kernel/linux/linux-toradex_3.14.28.bb      |  13 +
 6 files changed, 785 insertions(+), 1 deletion(-)
 create mode 100644 conf/machine/apalis-imx6.conf
 create mode 100644 conf/machine/colibri-imx6.conf
 create mode 100644 recipes-kernel/linux/linux-toradex-3.14.28/apalis-imx6/defconfig
 create mode 100644 recipes-kernel/linux/linux-toradex-3.14.28/colibri-imx6/defconfig
 create mode 100644 recipes-kernel/linux/linux-toradex_3.14.28.bb

-- 
1.9.3

[meta-fsl-arm-extra][PATCH 1/3] u-boot-toradex: add U-Boot recipe for Toradex i.MX 6 based modules

[Max Krummenacher]

This allows building U-Boot supporting Toradex modules based on i.MX 6
Apalis iMX6 and Colibri iMX6.
The source is combined with the source already used for our Vybrid based
modules and fetched directly from our Git server at git.toradex.com.

  - based on upstream U-Boot 2015.04
  - environment storage in eMMC
  - Ethernet
  - enabled gpio command line interface
  - enabled DFU and Mass Storage on USB client
  - framebuffer support
  - MMC/SD cards
  - eMMC flash
  - RAM size auto detection
  - serial console debug UART1
  - Toradex Apalis configuration block handling
  - USB storage as host on USB host ports

Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
---
 recipes-bsp/u-boot/u-boot-toradex_2015.04.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/recipes-bsp/u-boot/u-boot-toradex_2015.04.bb b/recipes-bsp/u-boot/u-boot-toradex_2015.04.bb
index 175add2..17c9267 100644
--- a/recipes-bsp/u-boot/u-boot-toradex_2015.04.bb
+++ b/recipes-bsp/u-boot/u-boot-toradex_2015.04.bb
@@ -4,4 +4,4 @@ PV = "v2015.04-v2.5b2+git${SRCPV}"
 
 SRCREV = "1ef4a29e8cea0239411dde64f9617ad76248fd02"
 SRCBRANCH = "2015.04-toradex"
-COMPATIBLE_MACHINE = "(vf)"
+COMPATIBLE_MACHINE = "(apalis-imx6|colibri-imx6|vf)"
-- 
1.9.3

[meta-fsl-arm-extra][PATCH 2/3] linux-toradex: add Linux recipe for Toradex i.MX 6 based modules

[Max Krummenacher]

This recipe provides a kernel for the Freescale i.MX 6 based modules
Colibri iMX6 and Apalis iMX6.

  - based on Freescale's BSP release imx_3.14.28_1.0.0_ga release and patches from Boundary Devices
  - GPIOlib /sys/class/gpio
  - PWM LEDs /sys/class/leds/
  - temperature sensor CPU /sys/devices/virtual/thermal/thermal_zone0/temp
      board: /sys/devices/soc0/soc.1/2100000.aips-bus/21a4000.i2c/i2c-1/1-0041/stmpe-adc/iio:device0/in_temp8_raw
  - Ethernet
  - eMMC/SD/MMC
  - serial console debug UART1
  - UARTs
  - I2C via /dev/i2c-X
  - framebuffer console
  - HDMI audio
  - analogue audio playback and capture, resistive touch
  - S/PDIF
  - SPI via /dev/spidev
  - serial number and board revision
  - USB host port
  - USB device Ethernet RNDIS
  - automatic USB device/host switching
  - analog input via IIO framework
  - parallel camera interface
  - DVFS power management
  - suspend LP1
  - watchdog
  Apalis only
  - CAN on via can0 and can1
  - PCIe (regular ports and mini-PCIe slot)
  - SATA (regular port or mSATA slot)

Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
---
 .../linux-toradex-3.14.28/apalis-imx6/defconfig    | 364 +++++++++++++++++++++
 .../linux-toradex-3.14.28/colibri-imx6/defconfig   | 356 ++++++++++++++++++++
 recipes-kernel/linux/linux-toradex_3.14.28.bb      |  13 +
 3 files changed, 733 insertions(+)
 create mode 100644 recipes-kernel/linux/linux-toradex-3.14.28/apalis-imx6/defconfig
 create mode 100644 recipes-kernel/linux/linux-toradex-3.14.28/colibri-imx6/defconfig
 create mode 100644 recipes-kernel/linux/linux-toradex_3.14.28.bb

diff --git a/recipes-kernel/linux/linux-toradex-3.14.28/apalis-imx6/defconfig b/recipes-kernel/linux/linux-toradex-3.14.28/apalis-imx6/defconfig
new file mode 100644
index 0000000..4c7be40
--- /dev/null
+++ b/recipes-kernel/linux/linux-toradex-3.14.28/apalis-imx6/defconfig
@@ -0,0 +1,364 @@
+CONFIG_KERNEL_LZO=y
+CONFIG_SYSVIPC=y
+CONFIG_FHANDLE=y
+CONFIG_NO_HZ=y
+CONFIG_HIGH_RES_TIMERS=y
+CONFIG_IKCONFIG=y
+CONFIG_IKCONFIG_PROC=y
+CONFIG_LOG_BUF_SHIFT=18
+CONFIG_CGROUPS=y
+CONFIG_CGROUP_DEBUG=y
+CONFIG_CGROUP_FREEZER=y
+CONFIG_CGROUP_CPUACCT=y
+CONFIG_RESOURCE_COUNTERS=y
+CONFIG_CGROUP_SCHED=y
+CONFIG_NAMESPACES=y
+CONFIG_RELAY=y
+CONFIG_BLK_DEV_INITRD=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_IMX6Q=y
+CONFIG_SOC_IMX6SL=y
+CONFIG_SOC_IMX6SX=y
+CONFIG_PCI=y
+CONFIG_PCI_MSI=y
+CONFIG_PCI_IMX6=y
+CONFIG_PCI_FORCE_GEN1=y
+CONFIG_SMP=y
+CONFIG_VMSPLIT_2G=y
+CONFIG_PREEMPT_VOLUNTARY=y
+CONFIG_AEABI=y
+CONFIG_HIGHMEM=y
+CONFIG_CMA=y
+CONFIG_UACCESS_WITH_MEMCPY=y
+CONFIG_SECCOMP=y
+CONFIG_CMDLINE="noinitrd console=ttymxc0,115200"
+CONFIG_CPU_FREQ=y
+CONFIG_CPU_FREQ_DEFAULT_GOV_INTERACTIVE=y
+CONFIG_CPU_FREQ_GOV_POWERSAVE=y
+CONFIG_CPU_FREQ_GOV_USERSPACE=y
+CONFIG_CPU_FREQ_GOV_ONDEMAND=y
+CONFIG_CPU_FREQ_GOV_CONSERVATIVE=y
+CONFIG_ARM_IMX6Q_CPUFREQ=y
+CONFIG_CPU_IDLE=y
+CONFIG_VFP=y
+CONFIG_NEON=y
+CONFIG_BINFMT_MISC=m
+CONFIG_PM_RUNTIME=y
+CONFIG_PM_DEBUG=y
+CONFIG_PM_TEST_SUSPEND=y
+CONFIG_NET=y
+CONFIG_PACKET=y
+CONFIG_UNIX=y
+CONFIG_INET=y
+CONFIG_IP_MULTICAST=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_VCAN=y
+CONFIG_CAN_FLEXCAN=y
+CONFIG_BT=m
+CONFIG_BT_RFCOMM=m
+CONFIG_BT_RFCOMM_TTY=y
+CONFIG_BT_BNEP=m
+CONFIG_BT_BNEP_MC_FILTER=y
+CONFIG_BT_BNEP_PROTO_FILTER=y
+CONFIG_BT_HIDP=m
+CONFIG_BT_HCIUART=m
+CONFIG_BT_HCIUART_LL=y
+CONFIG_CFG80211=m
+CONFIG_MAC80211=m
+CONFIG_RFKILL=y
+CONFIG_RFKILL_GPIO=y
+CONFIG_DEVTMPFS=y
+CONFIG_DEVTMPFS_MOUNT=y
+# CONFIG_STANDALONE is not set
+CONFIG_DMA_CMA=y
+CONFIG_CMA_SIZE_MBYTES=320
+CONFIG_CONNECTOR=y
+CONFIG_MTD=y
+CONFIG_MTD_CMDLINE_PARTS=y
+CONFIG_MTD_BLOCK=y
+CONFIG_MTD_CFI=y
+CONFIG_MTD_JEDECPROBE=y
+CONFIG_MTD_CFI_INTELEXT=y
+CONFIG_MTD_CFI_AMDSTD=y
+CONFIG_MTD_CFI_STAA=y
+CONFIG_MTD_PHYSMAP_OF=y
+CONFIG_MTD_UBI=y
+CONFIG_PROC_DEVICETREE=y
+CONFIG_BLK_DEV_LOOP=y
+CONFIG_BLK_DEV_RAM=y
+CONFIG_BLK_DEV_RAM_SIZE=65536
+CONFIG_EEPROM_AT24=y
+CONFIG_EEPROM_AT25=y
+# CONFIG_SCSI_PROC_FS is not set
+CONFIG_BLK_DEV_SD=y
+CONFIG_SCSI_MULTI_LUN=y
+CONFIG_SCSI_CONSTANTS=y
+CONFIG_SCSI_LOGGING=y
+CONFIG_SCSI_SCAN_ASYNC=y
+# CONFIG_SCSI_LOWLEVEL is not set
+CONFIG_ATA=y
+CONFIG_SATA_AHCI=m
+CONFIG_SATA_AHCI_PLATFORM=y
+CONFIG_AHCI_IMX=y
+CONFIG_PATA_IMX=y
+CONFIG_NETDEVICES=y
+# CONFIG_NET_VENDOR_ATHEROS 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_INTEL is not set
+# CONFIG_NET_VENDOR_MARVELL is not set
+# CONFIG_NET_VENDOR_MICREL is not set
+# CONFIG_NET_VENDOR_MICROCHIP is not set
+# CONFIG_NET_VENDOR_NATSEMI 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_WIZNET is not set
+CONFIG_MICREL_PHY=y
+CONFIG_PPP=m
+CONFIG_USB_USBNET=y
+CONFIG_RT2X00=m
+CONFIG_RT2800USB=m
+CONFIG_RTL8192CU=m
+# CONFIG_RTLWIFI_DEBUG is not set
+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_FUSION_F0710A=m
+CONFIG_TOUCHSCREEN_STMPE=y
+CONFIG_INPUT_MISC=y
+CONFIG_INPUT_UINPUT=y
+CONFIG_SERIO_SERPORT=m
+CONFIG_DEVPTS_MULTIPLE_INSTANCES=y
+# CONFIG_LEGACY_PTYS is not set
+# CONFIG_DEVKMEM is not set
+CONFIG_SERIAL_IMX=y
+CONFIG_SERIAL_IMX_CONSOLE=y
+CONFIG_SERIAL_FSL_LPUART=y
+CONFIG_SERIAL_FSL_LPUART_CONSOLE=y
+# CONFIG_I2C_COMPAT is not set
+CONFIG_I2C_CHARDEV=y
+CONFIG_I2C_MUX=y
+CONFIG_I2C_MUX_GPIO=y
+# CONFIG_I2C_HELPER_AUTO is not set
+CONFIG_I2C_ALGOPCF=m
+CONFIG_I2C_ALGOPCA=m
+CONFIG_I2C_GPIO=y
+CONFIG_I2C_IMX=y
+CONFIG_SPI=y
+CONFIG_SPI_IMX=y
+CONFIG_SPI_SPIDEV=y
+CONFIG_GPIO_SYSFS=y
+CONFIG_POWER_SUPPLY=y
+CONFIG_SENSORS_MAG3110=y
+CONFIG_THERMAL=y
+CONFIG_CPU_THERMAL=y
+CONFIG_IMX_THERMAL=y
+CONFIG_DEVICE_THERMAL=y
+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_PFUZE100=y
+CONFIG_MEDIA_SUPPORT=y
+CONFIG_MEDIA_CAMERA_SUPPORT=y
+CONFIG_MEDIA_USB_SUPPORT=y
+CONFIG_USB_VIDEO_CLASS=m
+CONFIG_V4L_PLATFORM_DRIVERS=y
+CONFIG_VIDEO_MXC_OUTPUT=y
+CONFIG_VIDEO_MXC_CAPTURE=m
+CONFIG_MXC_CAMERA_OV5640=m
+CONFIG_MXC_CAMERA_OV5642=m
+CONFIG_MXC_CAMERA_OV5640_MIPI=m
+CONFIG_MXC_TVIN_ADV7180=m
+CONFIG_MXC_TVIN_MAX9526=m
+CONFIG_MXC_IPU_DEVICE_QUEUE_SDC=m
+CONFIG_VIDEO_MXC_IPU_OUTPUT=y
+CONFIG_VIDEO_MXC_PXP_V4L2=y
+CONFIG_VIDEO_MXC_CSI_CAMERA=m
+CONFIG_MXC_VADC=m
+CONFIG_SOC_CAMERA=y
+# CONFIG_MEDIA_SUBDRV_AUTOSELECT is not set
+# CONFIG_DVB_AU8522_V4L is not set
+# CONFIG_DVB_TUNER_DIB0070 is not set
+# CONFIG_DVB_TUNER_DIB0090 is not set
+CONFIG_DRM=y
+CONFIG_DRM_VIVANTE=y
+CONFIG_FB=y
+CONFIG_FB_MXS=y
+CONFIG_BACKLIGHT_LCD_SUPPORT=y
+CONFIG_LCD_CLASS_DEVICE=y
+CONFIG_LCD_L4F00242T03=y
+CONFIG_LCD_PLATFORM=y
+CONFIG_BACKLIGHT_CLASS_DEVICE=y
+CONFIG_BACKLIGHT_PWM=y
+CONFIG_FB_MXC_SYNC_PANEL=y
+CONFIG_FB_MXC_LDB=y
+CONFIG_FB_MXC_MIPI_DSI=y
+CONFIG_FB_MXC_TRULY_WVGA_SYNC_PANEL=y
+CONFIG_FB_MXC_HDMI=y
+CONFIG_FB_MXC_EINK_PANEL=y
+CONFIG_FB_MXS_SII902X=y
+CONFIG_HANNSTAR_CABC=y
+CONFIG_FRAMEBUFFER_CONSOLE=y
+CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY=y
+CONFIG_LOGO=y
+CONFIG_SOUND=y
+CONFIG_SND=y
+# CONFIG_SND_DRIVERS is not set
+# CONFIG_SND_ARM is not set
+# CONFIG_SND_SPI is not set
+CONFIG_SND_USB_AUDIO=m
+CONFIG_SND_SOC=y
+CONFIG_SND_IMX_SOC=y
+CONFIG_SND_SOC_IMX_SGTL5000=y
+CONFIG_SND_SOC_IMX_SPDIF=y
+CONFIG_SND_SOC_IMX_HDMI=y
+CONFIG_HIDRAW=y
+CONFIG_HID_MULTITOUCH=m
+CONFIG_USB_HIDDEV=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_USB_SERIAL_GENERIC=y
+CONFIG_USB_SERIAL_PL2303=y
+CONFIG_USB_SERIAL_QUALCOMM=y
+CONFIG_USB_SERIAL_OPTION=y
+CONFIG_USB_MXS_PHY=y
+CONFIG_USB_GADGET=y
+CONFIG_USB_ZERO=m
+CONFIG_USB_ETH=m
+CONFIG_USB_MASS_STORAGE=m
+CONFIG_USB_G_SERIAL=m
+CONFIG_MMC=y
+CONFIG_MMC_UNSAFE_RESUME=y
+CONFIG_MMC_SDHCI=y
+CONFIG_MMC_SDHCI_PLTFM=y
+CONFIG_MMC_SDHCI_ESDHC_IMX=y
+CONFIG_MXC_IPU=y
+CONFIG_MXC_GPU_VIV=y
+CONFIG_MXC_MIPI_CSI2=y
+CONFIG_MXC_MLB150=m
+CONFIG_NEW_LEDS=y
+CONFIG_LEDS_CLASS=y
+CONFIG_LEDS_GPIO=y
+CONFIG_LEDS_PWM=y
+CONFIG_RTC_CLASS=y
+CONFIG_RTC_INTF_DEV_UIE_EMUL=y
+CONFIG_RTC_DRV_DS1307=y
+CONFIG_RTC_DRV_SNVS=y
+CONFIG_DMADEVICES=y
+# CONFIG_MX3_IPU is not set
+CONFIG_MXC_PXP_V2=y
+CONFIG_IMX_SDMA=y
+CONFIG_STAGING=y
+CONFIG_STMPE_ADC=y
+# CONFIG_IOMMU_SUPPORT is not set
+CONFIG_IIO=y
+CONFIG_PWM=y
+CONFIG_PWM_IMX=y
+CONFIG_EXT2_FS=y
+CONFIG_EXT2_FS_XATTR=y
+CONFIG_EXT2_FS_POSIX_ACL=y
+CONFIG_EXT2_FS_SECURITY=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_CUSE=y
+CONFIG_ISO9660_FS=m
+CONFIG_JOLIET=y
+CONFIG_ZISOFS=y
+CONFIG_UDF_FS=m
+CONFIG_MSDOS_FS=m
+CONFIG_VFAT_FS=y
+CONFIG_TMPFS=y
+CONFIG_TMPFS_POSIX_ACL=y
+CONFIG_SQUASHFS=y
+CONFIG_NFS_FS=y
+CONFIG_NFS_V3_ACL=y
+CONFIG_NFS_V4=y
+CONFIG_ROOT_NFS=y
+CONFIG_CIFS=y
+CONFIG_NLS_DEFAULT="cp437"
+CONFIG_NLS_CODEPAGE_437=y
+CONFIG_NLS_ASCII=y
+CONFIG_NLS_ISO8859_1=y
+CONFIG_NLS_ISO8859_15=m
+CONFIG_NLS_UTF8=y
+CONFIG_PRINTK_TIME=y
+CONFIG_DEBUG_FS=y
+# CONFIG_SCHED_DEBUG is not set
+# CONFIG_DEBUG_BUGVERBOSE is not set
+# CONFIG_FTRACE is not set
+# CONFIG_ARM_UNWIND is not set
+CONFIG_SECURITYFS=y
+CONFIG_CRYPTO_USER=y
+CONFIG_CRYPTO_CCM=y
+CONFIG_CRYPTO_GCM=y
+CONFIG_CRYPTO_CBC=y
+CONFIG_CRYPTO_CTS=y
+CONFIG_CRYPTO_LRW=y
+CONFIG_CRYPTO_PCBC=y
+CONFIG_CRYPTO_XTS=y
+CONFIG_CRYPTO_MICHAEL_MIC=y
+CONFIG_CRYPTO_RMD128=y
+CONFIG_CRYPTO_RMD160=y
+CONFIG_CRYPTO_RMD256=y
+CONFIG_CRYPTO_RMD320=y
+CONFIG_CRYPTO_SHA1=y
+CONFIG_CRYPTO_SHA512=y
+CONFIG_CRYPTO_TGR192=y
+CONFIG_CRYPTO_WP512=y
+CONFIG_CRYPTO_BLOWFISH=y
+CONFIG_CRYPTO_CAMELLIA=y
+CONFIG_CRYPTO_TWOFISH=y
+CONFIG_CRYPTO_DEFLATE=y
+CONFIG_CRYPTO_LZO=y
+# CONFIG_CRYPTO_ANSI_CPRNG is not set
+CONFIG_CRYPTO_DEV_FSL_CAAM=y
+CONFIG_CRYPTO_DEV_FSL_CAAM_SM=y
+CONFIG_CRYPTO_DEV_FSL_CAAM_SM_TEST=y
+CONFIG_CRYPTO_DEV_FSL_CAAM_SECVIO=y
+CONFIG_CRC_T10DIF=y
+CONFIG_CRC7=m
+CONFIG_LIBCRC32C=m
+CONFIG_FONTS=y
+CONFIG_FONT_8x8=y
+CONFIG_FONT_8x16=y
diff --git a/recipes-kernel/linux/linux-toradex-3.14.28/colibri-imx6/defconfig b/recipes-kernel/linux/linux-toradex-3.14.28/colibri-imx6/defconfig
new file mode 100644
index 0000000..ac6f0fb
--- /dev/null
+++ b/recipes-kernel/linux/linux-toradex-3.14.28/colibri-imx6/defconfig
@@ -0,0 +1,356 @@
+CONFIG_KERNEL_LZO=y
+CONFIG_SYSVIPC=y
+CONFIG_FHANDLE=y
+CONFIG_NO_HZ=y
+CONFIG_HIGH_RES_TIMERS=y
+CONFIG_IKCONFIG=y
+CONFIG_IKCONFIG_PROC=y
+CONFIG_LOG_BUF_SHIFT=18
+CONFIG_CGROUPS=y
+CONFIG_CGROUP_DEBUG=y
+CONFIG_CGROUP_FREEZER=y
+CONFIG_CGROUP_CPUACCT=y
+CONFIG_RESOURCE_COUNTERS=y
+CONFIG_CGROUP_SCHED=y
+CONFIG_NAMESPACES=y
+CONFIG_RELAY=y
+CONFIG_BLK_DEV_INITRD=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_IMX6Q=y
+CONFIG_SOC_IMX6SL=y
+CONFIG_SOC_IMX6SX=y
+CONFIG_SMP=y
+CONFIG_VMSPLIT_2G=y
+CONFIG_PREEMPT_VOLUNTARY=y
+CONFIG_AEABI=y
+CONFIG_HIGHMEM=y
+CONFIG_CMA=y
+CONFIG_UACCESS_WITH_MEMCPY=y
+CONFIG_SECCOMP=y
+CONFIG_CMDLINE="noinitrd console=ttymxc0,115200"
+CONFIG_CPU_FREQ=y
+CONFIG_CPU_FREQ_DEFAULT_GOV_INTERACTIVE=y
+CONFIG_CPU_FREQ_GOV_POWERSAVE=y
+CONFIG_CPU_FREQ_GOV_USERSPACE=y
+CONFIG_CPU_FREQ_GOV_ONDEMAND=y
+CONFIG_CPU_FREQ_GOV_CONSERVATIVE=y
+CONFIG_ARM_IMX6Q_CPUFREQ=y
+CONFIG_CPU_IDLE=y
+CONFIG_VFP=y
+CONFIG_NEON=y
+CONFIG_BINFMT_MISC=m
+CONFIG_PM_RUNTIME=y
+CONFIG_PM_DEBUG=y
+CONFIG_PM_TEST_SUSPEND=y
+CONFIG_NET=y
+CONFIG_PACKET=y
+CONFIG_UNIX=y
+CONFIG_INET=y
+CONFIG_IP_MULTICAST=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_VCAN=y
+CONFIG_CAN_MCP251X=y
+CONFIG_CAN_FLEXCAN=y
+CONFIG_BT=m
+CONFIG_BT_RFCOMM=m
+CONFIG_BT_RFCOMM_TTY=y
+CONFIG_BT_BNEP=m
+CONFIG_BT_BNEP_MC_FILTER=y
+CONFIG_BT_BNEP_PROTO_FILTER=y
+CONFIG_BT_HIDP=m
+CONFIG_BT_HCIUART=m
+CONFIG_BT_HCIUART_LL=y
+CONFIG_CFG80211=m
+CONFIG_MAC80211=m
+CONFIG_RFKILL=y
+CONFIG_RFKILL_GPIO=y
+CONFIG_DEVTMPFS=y
+CONFIG_DEVTMPFS_MOUNT=y
+# CONFIG_STANDALONE is not set
+CONFIG_DMA_CMA=y
+CONFIG_CMA_SIZE_MBYTES=256
+CONFIG_CMA_SIZE_PERCENTAGE=50
+CONFIG_CMA_SIZE_SEL_MIN=y
+CONFIG_IMX_WEIM=y
+CONFIG_CONNECTOR=y
+CONFIG_MTD=y
+CONFIG_MTD_CMDLINE_PARTS=y
+CONFIG_MTD_BLOCK=y
+CONFIG_MTD_CFI=y
+CONFIG_MTD_JEDECPROBE=y
+CONFIG_MTD_CFI_INTELEXT=y
+CONFIG_MTD_CFI_AMDSTD=y
+CONFIG_MTD_CFI_STAA=y
+CONFIG_MTD_PHYSMAP_OF=y
+CONFIG_MTD_UBI=y
+CONFIG_PROC_DEVICETREE=y
+CONFIG_BLK_DEV_LOOP=y
+CONFIG_BLK_DEV_RAM=y
+CONFIG_BLK_DEV_RAM_SIZE=65536
+CONFIG_EEPROM_AT24=y
+CONFIG_EEPROM_AT25=y
+CONFIG_SCSI=y
+# CONFIG_SCSI_PROC_FS is not set
+CONFIG_BLK_DEV_SD=y
+CONFIG_SCSI_MULTI_LUN=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_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_INTEL is not set
+# CONFIG_NET_VENDOR_MARVELL is not set
+# CONFIG_NET_VENDOR_MICREL is not set
+# CONFIG_NET_VENDOR_MICROCHIP is not set
+# CONFIG_NET_VENDOR_NATSEMI 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_WIZNET is not set
+CONFIG_MICREL_PHY=y
+CONFIG_PPP=m
+CONFIG_USB_USBNET=y
+CONFIG_RT2X00=m
+CONFIG_RT2800USB=m
+CONFIG_RTL8192CU=m
+# CONFIG_RTLWIFI_DEBUG is not set
+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_FUSION_F0710A=m
+CONFIG_TOUCHSCREEN_STMPE=y
+CONFIG_INPUT_MISC=y
+CONFIG_INPUT_UINPUT=y
+CONFIG_SERIO_SERPORT=m
+CONFIG_DEVPTS_MULTIPLE_INSTANCES=y
+# CONFIG_LEGACY_PTYS is not set
+# CONFIG_DEVKMEM is not set
+CONFIG_SERIAL_IMX=y
+CONFIG_SERIAL_IMX_CONSOLE=y
+CONFIG_SERIAL_FSL_LPUART=y
+CONFIG_SERIAL_FSL_LPUART_CONSOLE=y
+# CONFIG_I2C_COMPAT is not set
+CONFIG_I2C_CHARDEV=y
+CONFIG_I2C_MUX=y
+CONFIG_I2C_MUX_GPIO=y
+# CONFIG_I2C_HELPER_AUTO is not set
+CONFIG_I2C_ALGOPCF=m
+CONFIG_I2C_ALGOPCA=m
+CONFIG_I2C_GPIO=y
+CONFIG_I2C_IMX=y
+CONFIG_SPI=y
+CONFIG_SPI_IMX=y
+CONFIG_SPI_SPIDEV=y
+CONFIG_GPIO_SYSFS=y
+CONFIG_POWER_SUPPLY=y
+CONFIG_SENSORS_MAG3110=y
+CONFIG_THERMAL=y
+CONFIG_CPU_THERMAL=y
+CONFIG_IMX_THERMAL=y
+CONFIG_DEVICE_THERMAL=y
+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_PFUZE100=y
+CONFIG_MEDIA_SUPPORT=y
+CONFIG_MEDIA_CAMERA_SUPPORT=y
+CONFIG_MEDIA_USB_SUPPORT=y
+CONFIG_USB_VIDEO_CLASS=m
+CONFIG_V4L_PLATFORM_DRIVERS=y
+CONFIG_VIDEO_MXC_OUTPUT=y
+CONFIG_VIDEO_MXC_CAPTURE=m
+CONFIG_MXC_CAMERA_OV5640=m
+CONFIG_MXC_CAMERA_OV5642=m
+CONFIG_MXC_CAMERA_OV5640_MIPI=m
+CONFIG_MXC_TVIN_ADV7180=m
+CONFIG_MXC_TVIN_MAX9526=m
+CONFIG_MXC_IPU_DEVICE_QUEUE_SDC=m
+CONFIG_VIDEO_MXC_IPU_OUTPUT=y
+CONFIG_VIDEO_MXC_PXP_V4L2=y
+CONFIG_VIDEO_MXC_CSI_CAMERA=m
+CONFIG_MXC_VADC=m
+CONFIG_SOC_CAMERA=y
+# CONFIG_MEDIA_SUBDRV_AUTOSELECT is not set
+# CONFIG_DVB_AU8522_V4L is not set
+# CONFIG_DVB_TUNER_DIB0070 is not set
+# CONFIG_DVB_TUNER_DIB0090 is not set
+CONFIG_DRM=y
+CONFIG_DRM_VIVANTE=y
+CONFIG_FB=y
+CONFIG_FB_MXS=y
+CONFIG_BACKLIGHT_LCD_SUPPORT=y
+CONFIG_LCD_CLASS_DEVICE=y
+CONFIG_LCD_L4F00242T03=y
+CONFIG_LCD_PLATFORM=y
+CONFIG_BACKLIGHT_CLASS_DEVICE=y
+CONFIG_BACKLIGHT_PWM=y
+CONFIG_FB_MXC_SYNC_PANEL=y
+CONFIG_FB_MXC_HDMI=y
+CONFIG_FB_MXS_SII902X=y
+CONFIG_FRAMEBUFFER_CONSOLE=y
+CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY=y
+CONFIG_LOGO=y
+CONFIG_SOUND=y
+CONFIG_SND=y
+# CONFIG_SND_DRIVERS is not set
+# CONFIG_SND_ARM is not set
+# CONFIG_SND_SPI is not set
+CONFIG_SND_USB_AUDIO=m
+CONFIG_SND_SOC=y
+CONFIG_SND_IMX_SOC=y
+CONFIG_SND_SOC_IMX_SGTL5000=y
+CONFIG_SND_SOC_IMX_SPDIF=y
+CONFIG_SND_SOC_IMX_HDMI=y
+CONFIG_HIDRAW=y
+CONFIG_HID_MULTITOUCH=m
+CONFIG_USB_HIDDEV=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_USB_SERIAL_GENERIC=y
+CONFIG_USB_SERIAL_PL2303=y
+CONFIG_USB_SERIAL_QUALCOMM=y
+CONFIG_USB_SERIAL_OPTION=y
+CONFIG_USB_MXS_PHY=y
+CONFIG_USB_GADGET=y
+CONFIG_USB_ZERO=m
+CONFIG_USB_ETH=m
+CONFIG_USB_MASS_STORAGE=m
+CONFIG_USB_G_SERIAL=m
+CONFIG_MMC=y
+CONFIG_MMC_UNSAFE_RESUME=y
+CONFIG_MMC_SDHCI=y
+CONFIG_MMC_SDHCI_PLTFM=y
+CONFIG_MMC_SDHCI_ESDHC_IMX=y
+CONFIG_MXC_IPU=y
+CONFIG_MXC_GPU_VIV=y
+CONFIG_MXC_MIPI_CSI2=y
+CONFIG_MXC_MLB150=m
+CONFIG_NEW_LEDS=y
+CONFIG_LEDS_CLASS=y
+CONFIG_LEDS_GPIO=y
+CONFIG_LEDS_PWM=y
+CONFIG_RTC_CLASS=y
+CONFIG_RTC_INTF_DEV_UIE_EMUL=y
+CONFIG_RTC_DRV_DS1307=y
+CONFIG_RTC_DRV_SNVS=y
+CONFIG_DMADEVICES=y
+# CONFIG_MX3_IPU is not set
+CONFIG_MXC_PXP_V2=y
+CONFIG_IMX_SDMA=y
+CONFIG_STAGING=y
+CONFIG_STMPE_ADC=y
+# CONFIG_IOMMU_SUPPORT is not set
+CONFIG_EXTCON=y
+CONFIG_EXTCON_USB_GPIO=y
+CONFIG_IIO=y
+CONFIG_PWM=y
+CONFIG_PWM_IMX=y
+CONFIG_EXT2_FS=y
+CONFIG_EXT2_FS_XATTR=y
+CONFIG_EXT2_FS_POSIX_ACL=y
+CONFIG_EXT2_FS_SECURITY=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_CUSE=y
+CONFIG_ISO9660_FS=m
+CONFIG_JOLIET=y
+CONFIG_ZISOFS=y
+CONFIG_UDF_FS=m
+CONFIG_MSDOS_FS=m
+CONFIG_VFAT_FS=y
+CONFIG_TMPFS=y
+CONFIG_TMPFS_POSIX_ACL=y
+CONFIG_SQUASHFS=y
+CONFIG_NFS_FS=y
+CONFIG_NFS_V3_ACL=y
+CONFIG_NFS_V4=y
+CONFIG_ROOT_NFS=y
+CONFIG_CIFS=y
+CONFIG_NLS_DEFAULT="cp437"
+CONFIG_NLS_CODEPAGE_437=y
+CONFIG_NLS_ASCII=y
+CONFIG_NLS_ISO8859_1=y
+CONFIG_NLS_ISO8859_15=m
+CONFIG_NLS_UTF8=y
+CONFIG_PRINTK_TIME=y
+CONFIG_DEBUG_FS=y
+# CONFIG_SCHED_DEBUG is not set
+# CONFIG_DEBUG_BUGVERBOSE is not set
+# CONFIG_FTRACE is not set
+# CONFIG_ARM_UNWIND is not set
+CONFIG_SECURITYFS=y
+CONFIG_CRYPTO_USER=y
+CONFIG_CRYPTO_CCM=y
+CONFIG_CRYPTO_GCM=y
+CONFIG_CRYPTO_CBC=y
+CONFIG_CRYPTO_CTS=y
+CONFIG_CRYPTO_LRW=y
+CONFIG_CRYPTO_PCBC=y
+CONFIG_CRYPTO_XTS=y
+CONFIG_CRYPTO_MICHAEL_MIC=y
+CONFIG_CRYPTO_RMD128=y
+CONFIG_CRYPTO_RMD160=y
+CONFIG_CRYPTO_RMD256=y
+CONFIG_CRYPTO_RMD320=y
+CONFIG_CRYPTO_SHA1=y
+CONFIG_CRYPTO_SHA512=y
+CONFIG_CRYPTO_TGR192=y
+CONFIG_CRYPTO_WP512=y
+CONFIG_CRYPTO_BLOWFISH=y
+CONFIG_CRYPTO_CAMELLIA=y
+CONFIG_CRYPTO_TWOFISH=y
+CONFIG_CRYPTO_DEFLATE=y
+CONFIG_CRYPTO_LZO=y
+# CONFIG_CRYPTO_ANSI_CPRNG is not set
+CONFIG_CRYPTO_DEV_FSL_CAAM=y
+CONFIG_CRYPTO_DEV_FSL_CAAM_SM=y
+CONFIG_CRYPTO_DEV_FSL_CAAM_SM_TEST=y
+CONFIG_CRYPTO_DEV_FSL_CAAM_SECVIO=y
+CONFIG_CRC_T10DIF=y
+CONFIG_CRC7=m
+CONFIG_LIBCRC32C=m
+CONFIG_FONTS=y
+CONFIG_FONT_8x8=y
+CONFIG_FONT_8x16=y
diff --git a/recipes-kernel/linux/linux-toradex_3.14.28.bb b/recipes-kernel/linux/linux-toradex_3.14.28.bb
new file mode 100644
index 0000000..abd4278
--- /dev/null
+++ b/recipes-kernel/linux/linux-toradex_3.14.28.bb
@@ -0,0 +1,13 @@
+require recipes-kernel/linux/linux-imx.inc
+require recipes-kernel/linux/linux-dtb.inc
+
+SUMMARY = "Linux kernel for Toradex Freescale i.MX based modules"
+
+SRC_URI = "git://git.toradex.com/linux-toradex.git;protocol=git;branch=${SRCBRANCH} \
+           file://defconfig"
+
+LOCALVERSION = "-v2.5b2"
+SRCBRANCH = "toradex_imx_3.14.28_1.0.0_ga"
+SRCREV = "8f237ebe42f2cb911245369276a6b3043c2815f2"
+DEPENDS += "lzop-native bc-native"
+COMPATIBLE_MACHINE = "(apalis-imx6|colibri-imx6)"
-- 
1.9.3

[meta-fsl-arm-extra][PATCH 3/3] apalis-imx6/colibri-imx6: add machine configuration

[Max Krummenacher]

The Toradex Apalis iMX6 and Colibri iMX6 computer modules are based on i.MX 6.

The Apalis iMX6 is a member of the pincompatible Apalis family while
the Colibri iMX6 belongs to the Colibri family.

They feature on module RAM and EMMC, Ethernet PHY, Resistive Touch
Controller and Audio Codec.

For additional specifications please visit:
https://www.toradex.com/computer-on-modules/apalis-arm-family/freescale-imx-6
https://www.toradex.com/computer-on-modules/colibri-arm-family/freescale-imx6

Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
---
 conf/machine/apalis-imx6.conf  | 29 +++++++++++++++++++++++++++++
 conf/machine/colibri-imx6.conf | 22 ++++++++++++++++++++++
 2 files changed, 51 insertions(+)
 create mode 100644 conf/machine/apalis-imx6.conf
 create mode 100644 conf/machine/colibri-imx6.conf

diff --git a/conf/machine/apalis-imx6.conf b/conf/machine/apalis-imx6.conf
new file mode 100644
index 0000000..5fa405e
--- /dev/null
+++ b/conf/machine/apalis-imx6.conf
@@ -0,0 +1,29 @@
+#@TYPE: Machine
+#@NAME: Toradex Apalis iMX6Q/D
+#@SOC: i.MX6
+#@DESCRIPTION: Machine configuration for Toradex Apalis iMX6 SOM
+#@MAINTAINER: Max Krummenacher <max.krummenacher@toradex.com>
+
+include conf/machine/include/imx-base.inc
+include conf/machine/include/tune-cortexa9.inc
+
+SOC_FAMILY = "mx6:mx6q"
+
+PREFERRED_PROVIDER_virtual/kernel = "linux-toradex"
+KERNEL_DEVICETREE = "imx6q-apalis-eval.dtb imx6q-apalis_v1_0-eval.dtb \
+                     imx6q-apalis-ixora.dtb imx6q-apalis_v1_0-ixora.dtb"
+KERNEL_IMAGETYPE = "uImage"
+
+PREFERRED_PROVIDER_u-boot = "u-boot-toradex"
+PREFERRED_PROVIDER_virtual/bootloader = "u-boot-toradex"
+# Modules in commercial and industrial temperature range have different RAM.
+# Using apalis_imx6_it_defconfig builds an U-Boot working for both temperature
+# ranges, however, on commercially rated modules the RAM bandwidth is 5-10%
+# higher when using the optimized settings from apalis_imx6_defconfig.
+# The following builds both binaries, but uses the IT one in an SD image.
+UBOOT_CONFIG = "com it"
+UBOOT_MACHINE = "apalis_imx6_defconfig apalis_imx6_it_defconfig"
+
+SERIAL_CONSOLE = "115200 ttymxc0"
+
+MACHINE_FEATURES += "screen usbgadget usbhost vfat ext2 alsa touchscreen wifi bluetooth 3g pci"
diff --git a/conf/machine/colibri-imx6.conf b/conf/machine/colibri-imx6.conf
new file mode 100644
index 0000000..64987a6
--- /dev/null
+++ b/conf/machine/colibri-imx6.conf
@@ -0,0 +1,22 @@
+#@TYPE: Machine
+#@NAME: Toradex Colibri iMX6DL/S
+#@SOC: i.MX6 DL/S
+#@DESCRIPTION: Machine configuration for Toradex Colibri iMX6 SOM
+#@MAINTAINER: Max Krummenacher <max.krummenacher@toradex.com>
+
+include conf/machine/include/imx-base.inc
+include conf/machine/include/tune-cortexa9.inc
+
+SOC_FAMILY = "mx6:mx6dl"
+
+PREFERRED_PROVIDER_virtual/kernel = "linux-toradex"
+KERNEL_DEVICETREE = "imx6dl-colibri-eval-v3.dtb imx6dl-colibri-cam-eval-v3.dtb"
+KERNEL_IMAGETYPE = "uImage"
+
+PREFERRED_PROVIDER_u-boot = "u-boot-toradex"
+PREFERRED_PROVIDER_virtual/bootloader = "u-boot-toradex"
+UBOOT_MACHINE = "colibri_imx6_defconfig"
+
+SERIAL_CONSOLE = "115200 ttymxc0"
+
+MACHINE_FEATURES += "screen usbgadget usbhost vfat ext2 alsa touchscreen wifi bluetooth 3g"
-- 
1.9.3

Re: [meta-fsl-arm-extra][PATCH 1/3] u-boot-toradex: add U-Boot recipe for Toradex i.MX 6 based modules

[Stefan Agner]

Hi Max, Hi Otavio,

On 2015-12-03 08:47, Max Krummenacher wrote:
> This allows building U-Boot supporting Toradex modules based on i.MX 6
> Apalis iMX6 and Colibri iMX6.
> The source is combined with the source already used for our Vybrid based
> modules and fetched directly from our Git server at git.toradex.com.
> 
>   - based on upstream U-Boot 2015.04
>   - environment storage in eMMC
>   - Ethernet
>   - enabled gpio command line interface
>   - enabled DFU and Mass Storage on USB client
>   - framebuffer support
>   - MMC/SD cards
>   - eMMC flash
>   - RAM size auto detection
>   - serial console debug UART1
>   - Toradex Apalis configuration block handling
>   - USB storage as host on USB host ports
> 
> Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
> ---
>  recipes-bsp/u-boot/u-boot-toradex_2015.04.bb | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/recipes-bsp/u-boot/u-boot-toradex_2015.04.bb
> b/recipes-bsp/u-boot/u-boot-toradex_2015.04.bb
> index 175add2..17c9267 100644
> --- a/recipes-bsp/u-boot/u-boot-toradex_2015.04.bb
> +++ b/recipes-bsp/u-boot/u-boot-toradex_2015.04.bb
> @@ -4,4 +4,4 @@ PV = "v2015.04-v2.5b2+git${SRCPV}"
>  
>  SRCREV = "1ef4a29e8cea0239411dde64f9617ad76248fd02"
>  SRCBRANCH = "2015.04-toradex"
> -COMPATIBLE_MACHINE = "(vf)"
> +COMPATIBLE_MACHINE = "(apalis-imx6|colibri-imx6|vf)"

We have now a bit a mix and match between SoC's and machines. Maybe
specify the machines explicitly as Max did is the better choice since
that is what we tested with that tree (although, I guess whatever works
upstream should also work with our tree, we usually do not break other
stuff on purpose :-))

@Otavio, any preference?

Otherwise,
Acked-by: Stefan Agner <stefan.agner@toradex.com>

--
Stefan

Re: [meta-fsl-arm-extra][PATCH 1/3] u-boot-toradex: add U-Boot recipe for Toradex i.MX 6 based modules

[Otavio Salvador]

Hello Stefan,

On Thu, Dec 3, 2015 at 3:58 PM, Stefan Agner <stefan@agner.ch> wrote:
> On 2015-12-03 08:47, Max Krummenacher wrote:
>> This allows building U-Boot supporting Toradex modules based on i.MX 6
>> Apalis iMX6 and Colibri iMX6.
>> The source is combined with the source already used for our Vybrid based
>> modules and fetched directly from our Git server at git.toradex.com.
>>
>>   - based on upstream U-Boot 2015.04
>>   - environment storage in eMMC
>>   - Ethernet
>>   - enabled gpio command line interface
>>   - enabled DFU and Mass Storage on USB client
>>   - framebuffer support
>>   - MMC/SD cards
>>   - eMMC flash
>>   - RAM size auto detection
>>   - serial console debug UART1
>>   - Toradex Apalis configuration block handling
>>   - USB storage as host on USB host ports
>>
>> Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
>> ---
>>  recipes-bsp/u-boot/u-boot-toradex_2015.04.bb | 2 +-
>>  1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/recipes-bsp/u-boot/u-boot-toradex_2015.04.bb
>> b/recipes-bsp/u-boot/u-boot-toradex_2015.04.bb
>> index 175add2..17c9267 100644
>> --- a/recipes-bsp/u-boot/u-boot-toradex_2015.04.bb
>> +++ b/recipes-bsp/u-boot/u-boot-toradex_2015.04.bb
>> @@ -4,4 +4,4 @@ PV = "v2015.04-v2.5b2+git${SRCPV}"
>>
>>  SRCREV = "1ef4a29e8cea0239411dde64f9617ad76248fd02"
>>  SRCBRANCH = "2015.04-toradex"
>> -COMPATIBLE_MACHINE = "(vf)"
>> +COMPATIBLE_MACHINE = "(apalis-imx6|colibri-imx6|vf)"
>
> We have now a bit a mix and match between SoC's and machines. Maybe
> specify the machines explicitly as Max did is the better choice since
> that is what we tested with that tree (although, I guess whatever works
> upstream should also work with our tree, we usually do not break other
> stuff on purpose :-))
>
> @Otavio, any preference?

I prefer SoC family as it makes easier for end customers to customized
it without need to override the compatibility set in a bbappend. As
this provides a SoM it is common it ends being used in a custom
carrier board and eventually a new machine file in a customer layer
can reuse the recipe.

-- 
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] apalis-imx6/colibri-imx6: add machine configuration

[Otavio Salvador]

On Thu, Dec 3, 2015 at 2:47 PM, Max Krummenacher <max.oss.09@gmail.com> wrote:
> The Toradex Apalis iMX6 and Colibri iMX6 computer modules are based on i.MX 6.
>
> The Apalis iMX6 is a member of the pincompatible Apalis family while
> the Colibri iMX6 belongs to the Colibri family.
>
> They feature on module RAM and EMMC, Ethernet PHY, Resistive Touch
> Controller and Audio Codec.
>
> For additional specifications please visit:
> https://www.toradex.com/computer-on-modules/apalis-arm-family/freescale-imx-6
> https://www.toradex.com/computer-on-modules/colibri-arm-family/freescale-imx6

Please split this on two commits.

>
> Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
> ---
>  conf/machine/apalis-imx6.conf  | 29 +++++++++++++++++++++++++++++
>  conf/machine/colibri-imx6.conf | 22 ++++++++++++++++++++++
>  2 files changed, 51 insertions(+)
>  create mode 100644 conf/machine/apalis-imx6.conf
>  create mode 100644 conf/machine/colibri-imx6.conf
>
> diff --git a/conf/machine/apalis-imx6.conf b/conf/machine/apalis-imx6.conf
> new file mode 100644
> index 0000000..5fa405e
> --- /dev/null
> +++ b/conf/machine/apalis-imx6.conf
> @@ -0,0 +1,29 @@
> +#@TYPE: Machine
> +#@NAME: Toradex Apalis iMX6Q/D
> +#@SOC: i.MX6
> +#@DESCRIPTION: Machine configuration for Toradex Apalis iMX6 SOM
> +#@MAINTAINER: Max Krummenacher <max.krummenacher@toradex.com>
> +
> +include conf/machine/include/imx-base.inc
> +include conf/machine/include/tune-cortexa9.inc
> +
> +SOC_FAMILY = "mx6:mx6q"
> +
> +PREFERRED_PROVIDER_virtual/kernel = "linux-toradex"
> +KERNEL_DEVICETREE = "imx6q-apalis-eval.dtb imx6q-apalis_v1_0-eval.dtb \
> +                     imx6q-apalis-ixora.dtb imx6q-apalis_v1_0-ixora.dtb"
> +KERNEL_IMAGETYPE = "uImage"
> +
> +PREFERRED_PROVIDER_u-boot = "u-boot-toradex"
> +PREFERRED_PROVIDER_virtual/bootloader = "u-boot-toradex"
> +# Modules in commercial and industrial temperature range have different RAM.
> +# Using apalis_imx6_it_defconfig builds an U-Boot working for both temperature
> +# ranges, however, on commercially rated modules the RAM bandwidth is 5-10%
> +# higher when using the optimized settings from apalis_imx6_defconfig.
> +# The following builds both binaries, but uses the IT one in an SD image.
> +UBOOT_CONFIG = "com it"
> +UBOOT_MACHINE = "apalis_imx6_defconfig apalis_imx6_it_defconfig"

You ought to use UBOOT_CONFIG[com] ... and it counterparts. See other
machies for how to use it.


-- 
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/3] linux-toradex: add Linux recipe for Toradex i.MX 6 based modules

[Otavio Salvador]

On Thu, Dec 3, 2015 at 2:47 PM, Max Krummenacher <max.oss.09@gmail.com> wrote:
> This recipe provides a kernel for the Freescale i.MX 6 based modules
> Colibri iMX6 and Apalis iMX6.
>
>   - based on Freescale's BSP release imx_3.14.28_1.0.0_ga release and patches from Boundary Devices
>   - GPIOlib /sys/class/gpio
>   - PWM LEDs /sys/class/leds/
>   - temperature sensor CPU /sys/devices/virtual/thermal/thermal_zone0/temp
>       board: /sys/devices/soc0/soc.1/2100000.aips-bus/21a4000.i2c/i2c-1/1-0041/stmpe-adc/iio:device0/in_temp8_raw
>   - Ethernet
>   - eMMC/SD/MMC
>   - serial console debug UART1
>   - UARTs
>   - I2C via /dev/i2c-X
>   - framebuffer console
>   - HDMI audio
>   - analogue audio playback and capture, resistive touch
>   - S/PDIF
>   - SPI via /dev/spidev
>   - serial number and board revision
>   - USB host port
>   - USB device Ethernet RNDIS
>   - automatic USB device/host switching
>   - analog input via IIO framework
>   - parallel camera interface
>   - DVFS power management
>   - suspend LP1
>   - watchdog
>   Apalis only
>   - CAN on via can0 and can1
>   - PCIe (regular ports and mini-PCIe slot)
>   - SATA (regular port or mSATA slot)
>
> Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>

I saw you have two defconfig files. If this is really need, please
split the commit on two.

-- 
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/3] u-boot-toradex: add U-Boot recipe for Toradex i.MX 6 based modules

[Stefan Agner]

On 2015-12-03 10:17, Otavio Salvador wrote:
> Hello Stefan,
> 
> On Thu, Dec 3, 2015 at 3:58 PM, Stefan Agner <stefan@agner.ch> wrote:
>> On 2015-12-03 08:47, Max Krummenacher wrote:
>>> This allows building U-Boot supporting Toradex modules based on i.MX 6
>>> Apalis iMX6 and Colibri iMX6.
>>> The source is combined with the source already used for our Vybrid based
>>> modules and fetched directly from our Git server at git.toradex.com.
>>>
>>>   - based on upstream U-Boot 2015.04
>>>   - environment storage in eMMC
>>>   - Ethernet
>>>   - enabled gpio command line interface
>>>   - enabled DFU and Mass Storage on USB client
>>>   - framebuffer support
>>>   - MMC/SD cards
>>>   - eMMC flash
>>>   - RAM size auto detection
>>>   - serial console debug UART1
>>>   - Toradex Apalis configuration block handling
>>>   - USB storage as host on USB host ports
>>>
>>> Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
>>> ---
>>>  recipes-bsp/u-boot/u-boot-toradex_2015.04.bb | 2 +-
>>>  1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> diff --git a/recipes-bsp/u-boot/u-boot-toradex_2015.04.bb
>>> b/recipes-bsp/u-boot/u-boot-toradex_2015.04.bb
>>> index 175add2..17c9267 100644
>>> --- a/recipes-bsp/u-boot/u-boot-toradex_2015.04.bb
>>> +++ b/recipes-bsp/u-boot/u-boot-toradex_2015.04.bb
>>> @@ -4,4 +4,4 @@ PV = "v2015.04-v2.5b2+git${SRCPV}"
>>>
>>>  SRCREV = "1ef4a29e8cea0239411dde64f9617ad76248fd02"
>>>  SRCBRANCH = "2015.04-toradex"
>>> -COMPATIBLE_MACHINE = "(vf)"
>>> +COMPATIBLE_MACHINE = "(apalis-imx6|colibri-imx6|vf)"
>>
>> We have now a bit a mix and match between SoC's and machines. Maybe
>> specify the machines explicitly as Max did is the better choice since
>> that is what we tested with that tree (although, I guess whatever works
>> upstream should also work with our tree, we usually do not break other
>> stuff on purpose :-))
>>
>> @Otavio, any preference?
> 
> I prefer SoC family as it makes easier for end customers to customized
> it without need to override the compatibility set in a bbappend. As
> this provides a SoM it is common it ends being used in a custom
> carrier board and eventually a new machine file in a customer layer
> can reuse the recipe.

This is a good point, so e.g. if somebody would need to alter the
machine and would create a machine like apalis-imx6-mycarrier. We
actually would need another inheritance like SoC, for boards/carrier
boards...

--
Stefan

Re: [meta-fsl-arm-extra][PATCH 1/3] u-boot-toradex: add U-Boot recipe for Toradex i.MX 6 based modules

[Daiane Angolini]

On Thu, Dec 3, 2015 at 4:17 PM, Otavio Salvador
<otavio.salvador@ossystems.com.br> wrote:
> Hello Stefan,
>
> On Thu, Dec 3, 2015 at 3:58 PM, Stefan Agner <stefan@agner.ch> wrote:
>> On 2015-12-03 08:47, Max Krummenacher wrote:
>>> This allows building U-Boot supporting Toradex modules based on i.MX 6
>>> Apalis iMX6 and Colibri iMX6.
>>> The source is combined with the source already used for our Vybrid based
>>> modules and fetched directly from our Git server at git.toradex.com.
>>>
>>>   - based on upstream U-Boot 2015.04
>>>   - environment storage in eMMC
>>>   - Ethernet
>>>   - enabled gpio command line interface
>>>   - enabled DFU and Mass Storage on USB client
>>>   - framebuffer support
>>>   - MMC/SD cards
>>>   - eMMC flash
>>>   - RAM size auto detection
>>>   - serial console debug UART1
>>>   - Toradex Apalis configuration block handling
>>>   - USB storage as host on USB host ports
>>>
>>> Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
>>> ---
>>>  recipes-bsp/u-boot/u-boot-toradex_2015.04.bb | 2 +-
>>>  1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> diff --git a/recipes-bsp/u-boot/u-boot-toradex_2015.04.bb
>>> b/recipes-bsp/u-boot/u-boot-toradex_2015.04.bb
>>> index 175add2..17c9267 100644
>>> --- a/recipes-bsp/u-boot/u-boot-toradex_2015.04.bb
>>> +++ b/recipes-bsp/u-boot/u-boot-toradex_2015.04.bb
>>> @@ -4,4 +4,4 @@ PV = "v2015.04-v2.5b2+git${SRCPV}"
>>>
>>>  SRCREV = "1ef4a29e8cea0239411dde64f9617ad76248fd02"
>>>  SRCBRANCH = "2015.04-toradex"
>>> -COMPATIBLE_MACHINE = "(vf)"
>>> +COMPATIBLE_MACHINE = "(apalis-imx6|colibri-imx6|vf)"
>>
>> We have now a bit a mix and match between SoC's and machines. Maybe
>> specify the machines explicitly as Max did is the better choice since
>> that is what we tested with that tree (although, I guess whatever works
>> upstream should also work with our tree, we usually do not break other
>> stuff on purpose :-))
>>
>> @Otavio, any preference?
>
> I prefer SoC family as it makes easier for end customers to customized
> it without need to override the compatibility set in a bbappend. As
> this provides a SoM it is common it ends being used in a custom
> carrier board and eventually a new machine file in a customer layer
> can reuse the recipe.

+1

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

Re: [meta-fsl-arm-extra][PATCH 1/3] u-boot-toradex: add U-Boot recipe for Toradex i.MX 6 based modules

[Otavio Salvador]

On Thu, Dec 3, 2015 at 4:24 PM, Stefan Agner <stefan@agner.ch> wrote:
> On 2015-12-03 10:17, Otavio Salvador wrote:
>> I prefer SoC family as it makes easier for end customers to customized
>> it without need to override the compatibility set in a bbappend. As
>> this provides a SoM it is common it ends being used in a custom
>> carrier board and eventually a new machine file in a customer layer
>> can reuse the recipe.
>
> This is a good point, so e.g. if somebody would need to alter the
> machine and would create a machine like apalis-imx6-mycarrier. We
> actually would need another inheritance like SoC, for boards/carrier
> boards...

Yes but this can be add on the machine itself. The compatibile would
demand a bbappend usually.

-- 
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/3] u-boot-toradex: add U-Boot recipe for Toradex i.MX 6 based modules

[Stefan Agner]

On 2015-12-03 10:28, Otavio Salvador wrote:
> On Thu, Dec 3, 2015 at 4:24 PM, Stefan Agner <stefan@agner.ch> wrote:
>> On 2015-12-03 10:17, Otavio Salvador wrote:
>>> I prefer SoC family as it makes easier for end customers to customized
>>> it without need to override the compatibility set in a bbappend. As
>>> this provides a SoM it is common it ends being used in a custom
>>> carrier board and eventually a new machine file in a customer layer
>>> can reuse the recipe.
>>
>> This is a good point, so e.g. if somebody would need to alter the
>> machine and would create a machine like apalis-imx6-mycarrier. We
>> actually would need another inheritance like SoC, for boards/carrier
>> boards...
> 
> Yes but this can be add on the machine itself. The compatibile would
> demand a bbappend usually.

How can this be added? By using the module name "apalis-imx6" as
SOC_FAMILY?

In that case, a COMPATIBLE on module level would be good enough (e.g. as
it is now, just apalis/colibri-imx6 would be the module level).

However, so far customization needs on machine level hasn't really come
up so far. Customers typically use our default machines, and customize
the image by other means...

--
Stefan

Re: [meta-fsl-arm-extra][PATCH 1/3] u-boot-toradex: add U-Boot recipe for Toradex i.MX 6 based modules

[Otavio Salvador]

On Thu, Dec 3, 2015 at 4:43 PM, Stefan Agner <stefan@agner.ch> wrote:
> On 2015-12-03 10:28, Otavio Salvador wrote:
>> On Thu, Dec 3, 2015 at 4:24 PM, Stefan Agner <stefan@agner.ch> wrote:
>>> On 2015-12-03 10:17, Otavio Salvador wrote:
>>>> I prefer SoC family as it makes easier for end customers to customized
>>>> it without need to override the compatibility set in a bbappend. As
>>>> this provides a SoM it is common it ends being used in a custom
>>>> carrier board and eventually a new machine file in a customer layer
>>>> can reuse the recipe.
>>>
>>> This is a good point, so e.g. if somebody would need to alter the
>>> machine and would create a machine like apalis-imx6-mycarrier. We
>>> actually would need another inheritance like SoC, for boards/carrier
>>> boards...
>>
>> Yes but this can be add on the machine itself. The compatibile would
>> demand a bbappend usually.
>
> How can this be added? By using the module name "apalis-imx6" as
> SOC_FAMILY?
>
> In that case, a COMPATIBLE on module level would be good enough (e.g. as
> it is now, just apalis/colibri-imx6 would be the module level).

Yes; so it is added to the MACHINEOVERRIDES and ends being used as
fallback. This is done for Wandboard in the past and I think is still
used for OLinuxIno boards.

> However, so far customization needs on machine level hasn't really come
> up so far. Customers typically use our default machines, and customize
> the image by other means...

Yes but I see no problem in making it easier for end-users, do you?

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

Re: [meta-fsl-arm-extra][PATCH 1/3] u-boot-toradex: add U-Boot recipe for Toradex i.MX 6 based modules

[Stefan Agner]

On 2015-12-03 10:49, Otavio Salvador wrote:
> On Thu, Dec 3, 2015 at 4:43 PM, Stefan Agner <stefan@agner.ch> wrote:
>> On 2015-12-03 10:28, Otavio Salvador wrote:
>>> On Thu, Dec 3, 2015 at 4:24 PM, Stefan Agner <stefan@agner.ch> wrote:
>>>> On 2015-12-03 10:17, Otavio Salvador wrote:
>>>>> I prefer SoC family as it makes easier for end customers to customized
>>>>> it without need to override the compatibility set in a bbappend. As
>>>>> this provides a SoM it is common it ends being used in a custom
>>>>> carrier board and eventually a new machine file in a customer layer
>>>>> can reuse the recipe.
>>>>
>>>> This is a good point, so e.g. if somebody would need to alter the
>>>> machine and would create a machine like apalis-imx6-mycarrier. We
>>>> actually would need another inheritance like SoC, for boards/carrier
>>>> boards...
>>>
>>> Yes but this can be add on the machine itself. The compatibile would
>>> demand a bbappend usually.
>>
>> How can this be added? By using the module name "apalis-imx6" as
>> SOC_FAMILY?
>>
>> In that case, a COMPATIBLE on module level would be good enough (e.g. as
>> it is now, just apalis/colibri-imx6 would be the module level).
> 
> Yes; so it is added to the MACHINEOVERRIDES and ends being used as
> fallback. This is done for Wandboard in the past and I think is still
> used for OLinuxIno boards.
> 

I see.

>> However, so far customization needs on machine level hasn't really come
>> up so far. Customers typically use our default machines, and customize
>> the image by other means...
> 
> Yes but I see no problem in making it easier for end-users, do you?

It would be a big change, since all machines are now called according to
the module name. I guess you can't use the same name of a SOC level and
a machine... Hence we would have to rename all machines... taking care
of Documentation, etc...

I guess we need to discuss this internally and look at things a little
closer to understand the implications. Maybe we can postpone such a
change?

--
Stefan

Re: [meta-fsl-arm-extra][PATCH 1/3] u-boot-toradex: add U-Boot recipe for Toradex i.MX 6 based modules

[Otavio Salvador]

On Thu, Dec 3, 2015 at 5:25 PM, Stefan Agner <stefan@agner.ch> wrote:
> On 2015-12-03 10:49, Otavio Salvador wrote:
>> On Thu, Dec 3, 2015 at 4:43 PM, Stefan Agner <stefan@agner.ch> wrote:
>>> On 2015-12-03 10:28, Otavio Salvador wrote:
>>>> On Thu, Dec 3, 2015 at 4:24 PM, Stefan Agner <stefan@agner.ch> wrote:
>>>>> On 2015-12-03 10:17, Otavio Salvador wrote:
>>>>>> I prefer SoC family as it makes easier for end customers to customized
>>>>>> it without need to override the compatibility set in a bbappend. As
>>>>>> this provides a SoM it is common it ends being used in a custom
>>>>>> carrier board and eventually a new machine file in a customer layer
>>>>>> can reuse the recipe.
>>>>>
>>>>> This is a good point, so e.g. if somebody would need to alter the
>>>>> machine and would create a machine like apalis-imx6-mycarrier. We
>>>>> actually would need another inheritance like SoC, for boards/carrier
>>>>> boards...
>>>>
>>>> Yes but this can be add on the machine itself. The compatibile would
>>>> demand a bbappend usually.
>>>
>>> How can this be added? By using the module name "apalis-imx6" as
>>> SOC_FAMILY?
>>>
>>> In that case, a COMPATIBLE on module level would be good enough (e.g. as
>>> it is now, just apalis/colibri-imx6 would be the module level).
>>
>> Yes; so it is added to the MACHINEOVERRIDES and ends being used as
>> fallback. This is done for Wandboard in the past and I think is still
>> used for OLinuxIno boards.
>>
>
> I see.
>
>>> However, so far customization needs on machine level hasn't really come
>>> up so far. Customers typically use our default machines, and customize
>>> the image by other means...
>>
>> Yes but I see no problem in making it easier for end-users, do you?
>
> It would be a big change, since all machines are now called according to
> the module name. I guess you can't use the same name of a SOC level and
> a machine... Hence we would have to rename all machines... taking care
> of Documentation, etc...
>
> I guess we need to discuss this internally and look at things a little
> closer to understand the implications. Maybe we can postpone such a
> change?

Yes however please send the COMPATIBLE_MACHINES set for the SoC family
for now then. It helps and goes to the right direction.

-- 
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/3] linux-toradex: add Linux recipe for Toradex i.MX 6 based modules

[Max Krummenacher]

Hi Otavio, Stefan, Daiane

Thanks for the review!

Am Donnerstag, den 03.12.2015, 16:22 -0200 schrieb Otavio Salvador:
> On Thu, Dec 3, 2015 at 2:47 PM, Max Krummenacher <max.oss.09@gmail.com> wrote:
> > This recipe provides a kernel for the Freescale i.MX 6 based modules
> I saw you have two defconfig files. If this is really need, please
> split the commit on two.

The Apalis iMX6 allows access to PCIe/SATA/LVDS/analog RGB which the
Colibri iMX6 does not.
Having these subsystems in the kernel increases the kernel size by about
0.5 MB of dead code.
I think that merits the additional defconfig in the kernel recipe and I
like to keep two
separate defconfigs.

I will send a v2 of the patch series shortly with the review comments
addressed.

Max