Skip to contentSkip to conversation

Board: Add Engicam i.MX6 SOMs

PATCH Superseded Jagan Teki 3 participants 19 messages Jun 19, 2017 – Jun 20, 2017 Arm i.MX and Layerscape

v4 of 5 Superseded Latest is v5 →

lore
Share & tools
lore

Jagan Teki

author
#0 lore raw

v4 cover Board: Add Engicam i.MX6 SOMs

From: Jagan Teki <[email protected]>

This version of series has all supported features and fixes.

This series add buildroot support for Engicam i.MX6 SOM's
- i.CoreM6 DualLite/Solo
- i.CoreM6 RQS
- GEAM6UL
- Is.IoT MX6UL

Jagan Teki (6):
board: Add support for Engicam i.CoreM6 DualLite/Solo boards
board: engicam: Rename defconfig engicam_imx6qdl_icore_mmc_defconfig
board: Add support for Engicam i.CoreM6 RQS SOM
board: engicam: Add icorem6 for i.CoreM6 support
board: Add support for Engicam GEAM6UL SOM
board: Add support for Engicam Is.IoT MX6UL SOM

 .gitlab-ci.yml                                     |  5 +-
 DEVELOPERS                                         |  5 +-
 board/engicam/geam6ul/genimage.cfg                 | 38 ++++++++++++
 board/engicam/geam6ul/readme.txt                   | 65 +++++++++++++++++++++
 board/engicam/{ => icorem6}/genimage.cfg           |  1 +
 board/engicam/{ => icorem6}/readme.txt             | 20 ++++---
 board/engicam/icorem6_rqs/genimage.cfg             | 39 +++++++++++++
 board/engicam/icorem6_rqs/readme.txt               | 68 ++++++++++++++++++++++
 board/engicam/isiot/genimage.cfg                   | 38 ++++++++++++
 board/engicam/isiot/readme.txt                     | 65 +++++++++++++++++++++
 ...fconfig => engicam_imx6qdl_icore_mmc_defconfig} | 12 ++--
 configs/engicam_imx6qdl_icore_rqs_mmc_defconfig    | 41 +++++++++++++
 configs/engicam_imx6ul_geam_mmc_defconfig          | 41 +++++++++++++
 configs/engicam_imx6ul_isiot_mmc_defconfig         | 41 +++++++++++++
 14 files changed, 462 insertions(+), 17 deletions(-)
 create mode 100644 board/engicam/geam6ul/genimage.cfg
 create mode 100644 board/engicam/geam6ul/readme.txt
 rename board/engicam/{ => icorem6}/genimage.cfg (95%)
 rename board/engicam/{ => icorem6}/readme.txt (72%)
 create mode 100644 board/engicam/icorem6_rqs/genimage.cfg
 create mode 100644 board/engicam/icorem6_rqs/readme.txt
 create mode 100644 board/engicam/isiot/genimage.cfg
 create mode 100644 board/engicam/isiot/readme.txt
 rename configs/{engicam_imx6q_icore_defconfig => engicam_imx6qdl_icore_mmc_defconfig} (69%)
 create mode 100644 configs/engicam_imx6qdl_icore_rqs_mmc_defconfig
 create mode 100644 configs/engicam_imx6ul_geam_mmc_defconfig
 create mode 100644 configs/engicam_imx6ul_isiot_mmc_defconfig
Signature · 1 line
2.7.4
author
#1 lore raw

PATCH v4 1/6 board: Add support for Engicam i.CoreM6 DualLite/Solo boards

From: Jagan Teki <[email protected]>

Add initial support for Engicam i.CoreM6 DualLite/Solo board with below features:
- U-Boot 2017.05-rc1
- Linux 4.11.5
- Default packages from buildroot

U-Boot 2017.05-rc1 has common u-boot defconfig for All i.CoreM6 variant boards, so this patch update the same along with buildroot defconfig that reflect the common name.

---
Changes for v4:
- Update .gitlab-ci.yml
Changes for v3:
- Use kernel version 4.11.5
Changes for v2:
- Fix genimage.cfg path in readme.txt
- Remove exctra " in BR2_LINUX_KERNEL_INTREE_DTS_NAME

 .gitlab-ci.yml                                                 |  2 +-
 DEVELOPERS                                                     |  2 +-
 board/engicam/genimage.cfg                                     |  1 +
 board/engicam/readme.txt                                       |  6 ++++--
 ...m_imx6q_icore_defconfig => engicam_imx6qdl_icore_defconfig} | 10 +++++-----
 5 files changed, 12 insertions(+), 9 deletions(-)
 rename configs/{engicam_imx6q_icore_defconfig => engicam_imx6qdl_icore_defconfig} (74%)
.gitlab-ci.yml +1 -1
index 45c9b87..36ef1d1 100644
@@ -89,7 +89,7 @@ ci20_defconfig: *defconfig
 ci40_defconfig: *defconfig
 csky_gx6605s_defconfig: *defconfig
 cubieboard2_defconfig: *defconfig
-engicam_imx6q_icore_defconfig: *defconfig
+engicam_imx6qdl_icore_defconfig: *defconfig
 firefly_rk3288_defconfig: *defconfig
 firefly_rk3288_demo_defconfig: *defconfig
 freescale_imx28evk_defconfig: *defconfig
DEVELOPERS +1 -1
index f86a5dc..9a8b586 100644
@@ -837,7 +837,7 @@ F:	package/keepalived/
 
 N:	Jagan Teki <[email protected]>
 F:	board/engicam/
-F:	configs/engicam_imx6q_icore_defconfig
+F:	configs/engicam_imx6qdl_icore_defconfig
 
 N:	James Knight <[email protected]>
 F:	package/atkmm/
board/engicam/genimage.cfg +1 -0
index 43c81cf..cdccc90 100644
@@ -2,6 +2,7 @@ image boot.vfat {
 	vfat {
 		files = {
 			"uImage",
+			"imx6dl-icore.dtb",
 			"imx6q-icore.dtb"
 		}
 	}
board/engicam/readme.txt +4 -2
index eb7503f..d02c3af 100644
@@ -5,7 +5,7 @@ Buildroot for Engicam i.MX6 SOM platforms:
 This file documents the Buildroot support for all Engicam i.MX6 SOM
 platform boards.
 
-i.CoreM6 Quad/Dual SOM Starter kits:
+i.CoreM6 Quad/Dual/DualLite/Solo SOM Starter kits:
 https://www.engicam.com/vis-prod/101120
 
 This configuration uses U-Boot mainline and kernel mainline.
@@ -17,7 +17,7 @@ First, configure Buildroot for the Engicam i.MX SOM's:
 
 - for i.CoreM6 Quad/Dual:
 
-  make engicam_imx6q_icore_defconfig
+  make engicam_imx6qdl_icore_defconfig
 
 Build all components:
 
@@ -26,6 +26,8 @@ Build all components:
 You will find the following files in output/images/:
 - for i.CoreM6 Quad/Dual:
   - imx6q-icore.dtb
+- for i.CoreM6 DualLite/Solo:
+  - imx6dl-icore.dtb
   - rootfs.ext4
   - rootfs.tar
   - sdcard.img
configs/engicam_imx6qdl_icore_defconfig renamed from configs/engicam_imx6q_icore_defconfig +5 -5
similarity index 74%
rename from configs/engicam_imx6q_icore_defconfig
rename to configs/engicam_imx6qdl_icore_defconfig
index 63454ee..ffb3546 100644
@@ -14,8 +14,8 @@ BR2_TARGET_GENERIC_GETTY_PORT="ttymxc3"
 BR2_TARGET_UBOOT=y
 BR2_TARGET_UBOOT_BUILD_SYSTEM_KCONFIG=y
 BR2_TARGET_UBOOT_CUSTOM_VERSION=y
-BR2_TARGET_UBOOT_CUSTOM_VERSION_VALUE="2017.05"
-BR2_TARGET_UBOOT_BOARD_DEFCONFIG="imx6q_icore_mmc"
+BR2_TARGET_UBOOT_CUSTOM_VERSION_VALUE="2017.05-rc1"
+BR2_TARGET_UBOOT_BOARD_DEFCONFIG="imx6qdl_icore_mmc"
 BR2_TARGET_UBOOT_NEEDS_DTC=y
 BR2_TARGET_UBOOT_NEEDS_OPENSSL=y
 BR2_TARGET_UBOOT_FORMAT_DTB_IMG=y
@@ -25,15 +25,15 @@ BR2_TARGET_UBOOT_SPL_NAME="SPL"
 # Kernel
 BR2_LINUX_KERNEL=y
 BR2_LINUX_KERNEL_CUSTOM_VERSION=y
-BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="4.11"
+BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="4.11.5"
 BR2_LINUX_KERNEL_DEFCONFIG="imx_v6_v7"
 BR2_LINUX_KERNEL_UIMAGE=y
 BR2_LINUX_KERNEL_UIMAGE_LOADADDR="0x10008000"
 BR2_LINUX_KERNEL_DTS_SUPPORT=y
-BR2_LINUX_KERNEL_INTREE_DTS_NAME="imx6q-icore"
+BR2_LINUX_KERNEL_INTREE_DTS_NAME="imx6dl-icore imx6q-icore"
 
 # Filesystem
-BR2_TARGET_GENERIC_ISSUE="Welcome to Engicam i.CoreM6 Quad/Dual Starter Kit"
+BR2_TARGET_GENERIC_ISSUE="Welcome to Engicam i.CoreM6 Quad/Dual/DualLite/Solo Starter Kit"
 BR2_TARGET_ROOTFS_EXT2=y
 BR2_TARGET_ROOTFS_EXT2_4=y
 BR2_PACKAGE_HOST_GENIMAGE=y
Signature · 1 line
2.7.4
#2 lore raw

PATCH v4 1/6 board: Add support for Engicam i.CoreM6 DualLite/Solo boards

Hello,

configs/engicam_imx6qdl_icore_defconfig BR2_TARGET_GENERIC_GETTY_PORT="ttymxc3" · line 17

Quoted 3 lines · Jagan Teki
configs/engicam_imx6qdl_icore_defconfig renamed from configs/engicam_imx6q_icore_defconfig +1 -2
-BR2_TARGET_UBOOT_CUSTOM_VERSION_VALUE="2017.05"
-BR2_TARGET_UBOOT_BOARD_DEFCONFIG="imx6q_icore_mmc"
+BR2_TARGET_UBOOT_CUSTOM_VERSION_VALUE="2017.05-rc1"

This doesn't make sense. Why are you rolling back from 2017.05 to 2017.05-rc1 ?

I assume a feature present in the -rc1 is also present in the final release. Otherwise, it means the feature has been reverted, which is a bad sign.

Maybe you wanted to use 2017.07-rc1 instead?

If so, could you please fix this?

Thanks,

Thomas

Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
#3 lore raw

PATCH v4 1/6 board: Add support for Engicam i.CoreM6 DualLite/Solo boards

Quoted 11 lines · Thomas Petazzoni

Hello,

configs/engicam_imx6qdl_icore_defconfig BR2_TARGET_GENERIC_GETTY_PORT="ttymxc3" · line 17

Quoted 3 lines · Jagan Teki
configs/engicam_imx6qdl_icore_defconfig renamed from configs/engicam_imx6q_icore_defconfig +1 -2
-BR2_TARGET_UBOOT_CUSTOM_VERSION_VALUE="2017.05"
-BR2_TARGET_UBOOT_BOARD_DEFCONFIG="imx6q_icore_mmc"
+BR2_TARGET_UBOOT_CUSTOM_VERSION_VALUE="2017.05-rc1"

This doesn't make sense. Why are you rolling back from 2017.05 to 2017.05-rc1 ?

Quoted 5 lines

I assume a feature present in the -rc1 is also present in the final release. Otherwise, it means the feature has been reverted, which is a bad sign.

Maybe you wanted to use 2017.07-rc1 instead?

Yes I need to use -rc1 because this feature is present in it. I was trying for explicitly applying patches, but those are more.

thanks!

Signature · 4 lines
Jagan Teki
Senior Linux Kernel Engineer | Amarula Solutions
U-Boot, Linux | Upstream Maintainer
Hyderabad, India.
#4 lore raw

PATCH v4 1/6 board: Add support for Engicam i.CoreM6 DualLite/Solo boards

Hello,

Quoted 7 lines · Jagan Teki
Quoted 7 lines

configs/engicam_imx6qdl_icore_defconfig BR2_TARGET_GENERIC_GETTY_PORT="ttymxc3" · line 17

Quoted 3 lines
configs/engicam_imx6qdl_icore_defconfig renamed from configs/engicam_imx6q_icore_defconfig +1 -2
-BR2_TARGET_UBOOT_CUSTOM_VERSION_VALUE="2017.05"
-BR2_TARGET_UBOOT_BOARD_DEFCONFIG="imx6q_icore_mmc"
+BR2_TARGET_UBOOT_CUSTOM_VERSION_VALUE="2017.05-rc1"  

This doesn't make sense. Why are you rolling back from 2017.05 to 2017.05-rc1 ?

Quoted 8 lines
Quoted 5 lines

I assume a feature present in the -rc1 is also present in the final release. Otherwise, it means the feature has been reverted, which is a bad sign.

Maybe you wanted to use 2017.07-rc1 instead?

Yes I need to use -rc1 because this feature is present in it. I was trying for explicitly applying patches, but those are more.

Did you read what I wrote? Your patch is using 2017.05-rc1, which is most likely not what you intended, because 2017.05 final is available. Wasn't your intention to use 2017.07-rc1.

Please re-read carefully your patch and my review. Thanks!

Thomas

Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
#5 lore raw

PATCH v4 1/6 board: Add support for Engicam i.CoreM6 DualLite/Solo boards

Quoted 15 lines · Thomas Petazzoni

Hello,

Quoted 11 lines · Jagan Teki
Quoted 11 lines

configs/engicam_imx6qdl_icore_defconfig BR2_TARGET_GENERIC_GETTY_PORT="ttymxc3" · line 17

Quoted 3 lines
configs/engicam_imx6qdl_icore_defconfig renamed from configs/engicam_imx6q_icore_defconfig +1 -2
-BR2_TARGET_UBOOT_CUSTOM_VERSION_VALUE="2017.05"
-BR2_TARGET_UBOOT_BOARD_DEFCONFIG="imx6q_icore_mmc"
+BR2_TARGET_UBOOT_CUSTOM_VERSION_VALUE="2017.05-rc1"

This doesn't make sense. Why are you rolling back from 2017.05 to 2017.05-rc1 ?

I assume a feature present in the -rc1 is also present in the final release. Otherwise, it means the feature has been reverted, which is a bad sign.

Quoted 8 lines
Quoted 4 lines
Quoted 1 line

Maybe you wanted to use 2017.07-rc1 instead?

Yes I need to use -rc1 because this feature is present in it. I was trying for explicitly applying patches, but those are more.

Did you read what I wrote? Your patch is using 2017.05-rc1, which is most likely not what you intended, because 2017.05 final is available. Wasn't your intention to use 2017.07-rc1.

Sorry, my intention here is to use 2017.07-rc1, I think I sent wrong patch.

thanks!

Signature · 4 lines
Jagan Teki
Senior Linux Kernel Engineer | Amarula Solutions
U-Boot, Linux | Upstream Maintainer
Hyderabad, India.
author
#6 lore raw

PATCH v4 2/6 board: engicam: Rename defconfig engicam_imx6qdl_icore_mmc_defconfig

In reply to Jagan Teki

From: Jagan Teki <[email protected]>

Since the board have support for nand, better to explicitly name it with mmc.

engicam_imx6qdl_icore_defconfig => engicam_imx6qdl_icore_mmc_defconfig

---
Changes for v4:
- Update .gitlab-ci.yml
Changes for v3:
- none
Changes for v2:
- Fix genimage.cfg path in readme.txt

 .gitlab-ci.yml                                                          | 2 +-
 DEVELOPERS                                                              | 2 +-
 board/engicam/readme.txt                                                | 2 +-
 ...icam_imx6qdl_icore_defconfig => engicam_imx6qdl_icore_mmc_defconfig} | 0
 4 files changed, 3 insertions(+), 3 deletions(-)
 rename configs/{engicam_imx6qdl_icore_defconfig => engicam_imx6qdl_icore_mmc_defconfig} (100%)
.gitlab-ci.yml +1 -1
index 36ef1d1..c4bf90d 100644
@@ -89,7 +89,7 @@ ci20_defconfig: *defconfig
 ci40_defconfig: *defconfig
 csky_gx6605s_defconfig: *defconfig
 cubieboard2_defconfig: *defconfig
-engicam_imx6qdl_icore_defconfig: *defconfig
+engicam_imx6qdl_icore_mmc_defconfig: *defconfig
 firefly_rk3288_defconfig: *defconfig
 firefly_rk3288_demo_defconfig: *defconfig
 freescale_imx28evk_defconfig: *defconfig
DEVELOPERS +1 -1
index 9a8b586..85d81dc 100644
@@ -837,7 +837,7 @@ F:	package/keepalived/
 
 N:	Jagan Teki <[email protected]>
 F:	board/engicam/
-F:	configs/engicam_imx6qdl_icore_defconfig
+F:	configs/engicam_imx6qdl_icore_mmc_defconfig
 
 N:	James Knight <[email protected]>
 F:	package/atkmm/
board/engicam/readme.txt +1 -1
index d02c3af..0ef108d 100644
@@ -17,7 +17,7 @@ First, configure Buildroot for the Engicam i.MX SOM's:
 
 - for i.CoreM6 Quad/Dual:
 
-  make engicam_imx6qdl_icore_defconfig
+  make engicam_imx6qdl_icore_mmc_defconfig
 
 Build all components:
 
configs/engicam_imx6qdl_icore_mmc_defconfig renamed from configs/engicam_imx6qdl_icore_defconfig +0 -0
similarity index 100%
rename from configs/engicam_imx6qdl_icore_defconfig
rename to configs/engicam_imx6qdl_icore_mmc_defconfig
Signature · 1 line
2.7.4
#7 lore raw

PATCH v4 2/6 board: engicam: Rename defconfig engicam_imx6qdl_icore_mmc_defconfig

Hello,

Quoted 8 lines · Jagan Teki

From: Jagan Teki <[email protected]>

Since the board have support for nand, better to explicitly name it with mmc.

engicam_imx6qdl_icore_defconfig => engicam_imx6qdl_icore_mmc_defconfig

Unless we are going to introduce other configurations for the same board (to support NAND booting), then I would prefer to keep the name without the "mmc". The readme.txt can explain that the configuration supports MMC booting.

Also, in the follow-up patches, please avoid the _mmc_ part in the defconfig name.

Thanks,

Thomas

Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
#8 lore raw

PATCH v4 2/6 board: engicam: Rename defconfig engicam_imx6qdl_icore_mmc_defconfig

Quoted 8 lines · Thomas Petazzoni

Hello,

Quoted 5 lines · Jagan Teki

From: Jagan Teki <[email protected]>

Since the board have support for nand, better to explicitly name it with mmc.

Quoted 8 lines
Quoted 3 lines

engicam_imx6qdl_icore_defconfig => engicam_imx6qdl_icore_mmc_defconfig

Unless we are going to introduce other configurations for the same board (to support NAND booting), then I would prefer to keep the name without the "mmc". The readme.txt can explain that the configuration supports MMC booting.

I see a point where these defconfig names is in-line with U-Boot defconfig - since like U-Boot have defconfig based on boot-modes buildroot have similar approach.

thanks!

Signature · 4 lines
Jagan Teki
Senior Linux Kernel Engineer | Amarula Solutions
U-Boot, Linux | Upstream Maintainer
Hyderabad, India.
#9 lore raw

PATCH v4 2/6 board: engicam: Rename defconfig engicam_imx6qdl_icore_mmc_defconfig

Hello,

Quoted 8 lines · Jagan Teki
Quoted 4 lines

Unless we are going to introduce other configurations for the same board (to support NAND booting), then I would prefer to keep the name without the "mmc". The readme.txt can explain that the configuration supports MMC booting.

I see a point where these defconfig names is in-line with U-Boot defconfig - since like U-Boot have defconfig based on boot-modes buildroot have similar approach.

There is no special reason to have the Buildroot defconfig name match 1:1 the U-Boot name, so please drop the _mmc_ part of the Buildroot defconfig names.

Thanks!

Thomas

Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
author
#10 lore raw

PATCH v4 3/6 board: Add support for Engicam i.CoreM6 RQS SOM

In reply to Jagan Teki

From: Jagan Teki <[email protected]>

Add initial support for Engicam i.CoreM6 Quad/Dual/DualLite/Solo RQS board with below features:
- U-Boot 2017.07-rc1
- Linux 4.11.5
- Default packages from buildroot

---
Changes for v4:
- Update .gitlab-ci.yml
Changes for v3:
- Use kernel version 4.11.5
Changes for v2:
- Fix genimage.cfg path in readme.txt

 .gitlab-ci.yml                                  |  1 +
 DEVELOPERS                                      |  1 +
 board/engicam/icorem6_rqs/genimage.cfg          | 39 ++++++++++++++
 board/engicam/icorem6_rqs/readme.txt            | 68 +++++++++++++++++++++++++
 configs/engicam_imx6qdl_icore_rqs_mmc_defconfig | 41 +++++++++++++++
 5 files changed, 150 insertions(+)
 create mode 100644 board/engicam/icorem6_rqs/genimage.cfg
 create mode 100644 board/engicam/icorem6_rqs/readme.txt
 create mode 100644 configs/engicam_imx6qdl_icore_rqs_mmc_defconfig
.gitlab-ci.yml +1 -0
index c4bf90d..ca51f35 100644
@@ -90,6 +90,7 @@ ci40_defconfig: *defconfig
 csky_gx6605s_defconfig: *defconfig
 cubieboard2_defconfig: *defconfig
 engicam_imx6qdl_icore_mmc_defconfig: *defconfig
+engicam_imx6qdl_icore_rqs_mmc_defconfig: *defconfig
 firefly_rk3288_defconfig: *defconfig
 firefly_rk3288_demo_defconfig: *defconfig
 freescale_imx28evk_defconfig: *defconfig
DEVELOPERS +1 -0
index 85d81dc..feec989 100644
@@ -838,6 +838,7 @@ F:	package/keepalived/
 N:	Jagan Teki <[email protected]>
 F:	board/engicam/
 F:	configs/engicam_imx6qdl_icore_mmc_defconfig
+F:	configs/engicam_imx6qdl_icore_rqs_mmc_defconfig
 
 N:	James Knight <[email protected]>
 F:	package/atkmm/
board/engicam/icorem6_rqs/genimage.cfg new file +39 -0
new file mode 100644
index 0000000..a2ee860
@@ -0,0 +1,39 @@
+image boot.vfat {
+	vfat {
+		files = {
+			"uImage",
+			"imx6dl-icore-rqs.dtb",
+			"imx6q-icore-rqs.dtb"
+		}
+	}
+	size = 16M
+}
+
+image sdcard.img {
+	hdimage {
+	}
+
+	partition SPL {
+		in-partition-table = "no"
+		image = "SPL"
+		offset = 1024
+	}
+
+	partition u-boot-dtb {
+		in-partition-table = "no"
+		image = "u-boot-dtb.img"
+		offset = 69K
+	}
+
+	partition boot {
+		partition-type = 0xC
+		bootable = "true"
+		image = "boot.vfat"
+		offset = 8M
+	}
+
+	partition rootfs {
+		partition-type = 0x83
+		image = "rootfs.ext2"
+	}
+}
board/engicam/icorem6_rqs/readme.txt new file +68 -0

68 lines not on this page · raw message

configs/engicam_imx6qdl_icore_rqs_mmc_defconfig new file +41 -0

41 lines not on this page · raw message

Signature · 1 line
2.7.4
author
#11 lore raw

PATCH v4 4/6 board: engicam: Add icorem6 for i.CoreM6 support

In reply to Jagan Teki

From: Jagan Teki <[email protected]>

Create board/engicam/icorem6 for i.CoreM6 supported files. and update the readme.txt so-that it can list i.CoreM6 board details.

---
Changes for v4:
- Update .gitlab-ci.yml
Changes for v3:
- Use kernel version 4.11.5
Changes for v2:
- Fix genimage.cfg path in readme.txt

 board/engicam/{ => icorem6}/genimage.cfg    |  0
 board/engicam/{ => icorem6}/readme.txt      | 14 +++++++-------
 configs/engicam_imx6qdl_icore_mmc_defconfig |  2 +-
 3 files changed, 8 insertions(+), 8 deletions(-)
 rename board/engicam/{ => icorem6}/genimage.cfg (100%)
 rename board/engicam/{ => icorem6}/readme.txt (81%)
board/engicam/icorem6/genimage.cfg renamed from board/engicam/genimage.cfg +0 -0
similarity index 100%
rename from board/engicam/genimage.cfg
rename to board/engicam/icorem6/genimage.cfg
board/engicam/icorem6/readme.txt renamed from board/engicam/readme.txt +7 -7
similarity index 81%
rename from board/engicam/readme.txt
rename to board/engicam/icorem6/readme.txt
index 0ef108d..a86360b 100644
@@ -1,8 +1,8 @@
-*****************************************
-Buildroot for Engicam i.MX6 SOM platforms:
-*****************************************
+*********************************************
+Buildroot for Engicam i.CoreM6 SOM platforms:
+*********************************************
 
-This file documents the Buildroot support for all Engicam i.MX6 SOM
+This file documents the Buildroot support for Engicam i.CoreM6
 platform boards.
 
 i.CoreM6 Quad/Dual/DualLite/Solo SOM Starter kits:
@@ -13,9 +13,9 @@ This configuration uses U-Boot mainline and kernel mainline.
 Build
 =====
 
-First, configure Buildroot for the Engicam i.MX SOM's:
+First, configure Buildroot for the Engicam i.CoreM6:
 
-- for i.CoreM6 Quad/Dual:
+- for i.CoreM6 Quad/Dual/DualLite/Solo:
 
   make engicam_imx6qdl_icore_mmc_defconfig
 
@@ -52,7 +52,7 @@ command as root:
 *** WARNING! This will destroy all the card content. Use with care! ***
 
 For details about the medium image layout, see the definition in
-board/engicam/genimage.cfg
+board/engicam/icorem6/genimage.cfg
 
 Boot the i.CoreM6 boards with SD boot:
 =====================================
configs/engicam_imx6qdl_icore_mmc_defconfig +1 -1
index ffb3546..25048c4 100644
@@ -38,4 +38,4 @@ BR2_TARGET_ROOTFS_EXT2=y
 BR2_TARGET_ROOTFS_EXT2_4=y
 BR2_PACKAGE_HOST_GENIMAGE=y
 BR2_ROOTFS_POST_IMAGE_SCRIPT="support/scripts/genimage.sh"
-BR2_ROOTFS_POST_SCRIPT_ARGS="-c board/engicam/genimage.cfg"
+BR2_ROOTFS_POST_SCRIPT_ARGS="-c board/engicam/icorem6/genimage.cfg"
Signature · 1 line
2.7.4
author
#12 lore raw

PATCH v4 5/6 board: Add support for Engicam GEAM6UL SOM

In reply to Jagan Teki

From: Jagan Teki <[email protected]>

Add initial support for Engicam GEAM6UL SOM board
with below features:
- U-Boot 2017.07-rc1
- Linux 4.11.5
- Default packages from buildroot

---
Changes for v4:
- Update .gitlab-ci.yml
Changes for v3:
- Use kernel version 4.11.5
- Fix readme.txt file
Changes for v2:
- Fix genimage.cfg path in readme.txt

 .gitlab-ci.yml                            |  1 +
 DEVELOPERS                                |  1 +
 board/engicam/geam6ul/genimage.cfg        | 38 ++++++++++++++++++
 board/engicam/geam6ul/readme.txt          | 65 +++++++++++++++++++++++++++++++
 configs/engicam_imx6ul_geam_mmc_defconfig | 41 +++++++++++++++++++
 5 files changed, 146 insertions(+)
 create mode 100644 board/engicam/geam6ul/genimage.cfg
 create mode 100644 board/engicam/geam6ul/readme.txt
 create mode 100644 configs/engicam_imx6ul_geam_mmc_defconfig
.gitlab-ci.yml +1 -0
index ca51f35..5a7cdc1 100644
@@ -91,6 +91,7 @@ csky_gx6605s_defconfig: *defconfig
 cubieboard2_defconfig: *defconfig
 engicam_imx6qdl_icore_mmc_defconfig: *defconfig
 engicam_imx6qdl_icore_rqs_mmc_defconfig: *defconfig
+engicam_imx6ul_geam_mmc_defconfig: *defconfig
 firefly_rk3288_defconfig: *defconfig
 firefly_rk3288_demo_defconfig: *defconfig
 freescale_imx28evk_defconfig: *defconfig
DEVELOPERS +1 -0
index feec989..1f2ab32 100644
@@ -839,6 +839,7 @@ N:	Jagan Teki <[email protected]>
 F:	board/engicam/
 F:	configs/engicam_imx6qdl_icore_mmc_defconfig
 F:	configs/engicam_imx6qdl_icore_rqs_mmc_defconfig
+F:	configs/engicam_imx6ul_geam_mmc_defconfig
 
 N:	James Knight <[email protected]>
 F:	package/atkmm/
board/engicam/geam6ul/genimage.cfg new file +38 -0
new file mode 100644
index 0000000..3b5a31d
@@ -0,0 +1,38 @@
+image boot.vfat {
+	vfat {
+		files = {
+			"uImage",
+			"imx6ul-geam-kit.dtb"
+		}
+	}
+	size = 16M
+}
+
+image sdcard.img {
+	hdimage {
+	}
+
+	partition SPL {
+		in-partition-table = "no"
+		image = "SPL"
+		offset = 1024
+	}
+
+	partition u-boot-dtb {
+		in-partition-table = "no"
+		image = "u-boot-dtb.img"
+		offset = 69K
+	}
+
+	partition boot {
+		partition-type = 0xC
+		bootable = "true"
+		image = "boot.vfat"
+		offset = 8M
+	}
+
+	partition rootfs {
+		partition-type = 0x83
+		image = "rootfs.ext2"
+	}
+}
board/engicam/geam6ul/readme.txt new file +65 -0

65 lines not on this page · raw message

configs/engicam_imx6ul_geam_mmc_defconfig new file +41 -0

41 lines not on this page · raw message

Signature · 1 line
2.7.4
author
#13 lore raw

PATCH v4 6/6 board: Add support for Engicam Is.IoT MX6UL SOM

In reply to Jagan Teki

From: Jagan Teki <[email protected]>

Add initial support for Engicam Is.IoT MX6UL SOM board with below features:
- U-Boot 2017.07-rc1
- Linux 4.11.5
- Default packages from buildroot

---
Changes for v4:
- Update .gitlab-ci.yml
Changes for v3:
- Newly added patch

 .gitlab-ci.yml                             |  1 +
 DEVELOPERS                                 |  1 +
 board/engicam/isiot/genimage.cfg           | 38 +++++++++++++++++
 board/engicam/isiot/readme.txt             | 65 ++++++++++++++++++++++++++++++
 configs/engicam_imx6ul_isiot_mmc_defconfig | 41 +++++++++++++++++++
 5 files changed, 146 insertions(+)
 create mode 100644 board/engicam/isiot/genimage.cfg
 create mode 100644 board/engicam/isiot/readme.txt
 create mode 100644 configs/engicam_imx6ul_isiot_mmc_defconfig
.gitlab-ci.yml +1 -0
index 5a7cdc1..7ab53c5 100644
@@ -92,6 +92,7 @@ cubieboard2_defconfig: *defconfig
 engicam_imx6qdl_icore_mmc_defconfig: *defconfig
 engicam_imx6qdl_icore_rqs_mmc_defconfig: *defconfig
 engicam_imx6ul_geam_mmc_defconfig: *defconfig
+engicam_imx6ul_isiot_mmc_defconfig: *defconfig
 firefly_rk3288_defconfig: *defconfig
 firefly_rk3288_demo_defconfig: *defconfig
 freescale_imx28evk_defconfig: *defconfig
DEVELOPERS +1 -0
index 1f2ab32..2336172 100644
@@ -840,6 +840,7 @@ F:	board/engicam/
 F:	configs/engicam_imx6qdl_icore_mmc_defconfig
 F:	configs/engicam_imx6qdl_icore_rqs_mmc_defconfig
 F:	configs/engicam_imx6ul_geam_mmc_defconfig
+F:	configs/engicam_imx6ul_isiot_mmc_defconfig
 
 N:	James Knight <[email protected]>
 F:	package/atkmm/
board/engicam/isiot/genimage.cfg new file +38 -0
new file mode 100644
index 0000000..f111a0a
@@ -0,0 +1,38 @@
+image boot.vfat {
+	vfat {
+		files = {
+			"uImage",
+			"imx6ul-isiot-emmc.dtb"
+		}
+	}
+	size = 16M
+}
+
+image sdcard.img {
+	hdimage {
+	}
+
+	partition SPL {
+		in-partition-table = "no"
+		image = "SPL"
+		offset = 1024
+	}
+
+	partition u-boot-dtb {
+		in-partition-table = "no"
+		image = "u-boot-dtb.img"
+		offset = 69K
+	}
+
+	partition boot {
+		partition-type = 0xC
+		bootable = "true"
+		image = "boot.vfat"
+		offset = 8M
+	}
+
+	partition rootfs {
+		partition-type = 0x83
+		image = "rootfs.ext2"
+	}
+}
board/engicam/isiot/readme.txt new file +65 -0

65 lines not on this page · raw message

configs/engicam_imx6ul_isiot_mmc_defconfig new file +41 -0

41 lines not on this page · raw message

Signature · 1 line
2.7.4
#14 lore raw

v4 cover Board: Add Engicam i.MX6 SOMs

In reply to Jagan Teki

Hello,

Quoted 7 lines · Jagan Teki

Jagan Teki (6):
board: Add support for Engicam i.CoreM6 DualLite/Solo boards
board: engicam: Rename defconfig engicam_imx6qdl_icore_mmc_defconfig
board: Add support for Engicam i.CoreM6 RQS SOM
board: engicam: Add icorem6 for i.CoreM6 support
board: Add support for Engicam GEAM6UL SOM
board: Add support for Engicam Is.IoT MX6UL SOM

Thanks for this new iteration and those contributions. Since you're regularly posting new iterations of this patch series, it would be nice if you could create an account on patchwork, and mark yourself the previous iterations of your patch series as "Superseded". This way, it is easier for the maintainers to keep track of what is the latest version of your patch series that should be considered for review/merging.

See https://patchwork.ozlabs.org/project/buildroot/list/. You just need to create an account with the same e-mail address as the one used to send the patches.

Thanks!

Thomas

Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
#15 lore raw

v4 cover Board: Add Engicam i.MX6 SOMs

Quoted 20 lines · Thomas Petazzoni

Hello,

Quoted 7 lines · Jagan Teki

Jagan Teki (6):
board: Add support for Engicam i.CoreM6 DualLite/Solo boards
board: engicam: Rename defconfig engicam_imx6qdl_icore_mmc_defconfig
board: Add support for Engicam i.CoreM6 RQS SOM
board: engicam: Add icorem6 for i.CoreM6 support
board: Add support for Engicam GEAM6UL SOM
board: Add support for Engicam Is.IoT MX6UL SOM

Thanks for this new iteration and those contributions. Since you're regularly posting new iterations of this patch series, it would be nice if you could create an account on patchwork, and mark yourself the previous iterations of your patch series as "Superseded". This way, it is easier for the maintainers to keep track of what is the latest version of your patch series that should be considered for review/merging.

Quoted 3 lines

See https://patchwork.ozlabs.org/project/buildroot/list/. You just need to create an account with the same e-mail address as the one used to send the patches.

I've a patchwork.ozlabs account with different mail id, I guess it is ok to reuse the same. What do you think?

thanks!

Signature · 4 lines
Jagan Teki
Senior Linux Kernel Engineer | Amarula Solutions
U-Boot, Linux | Upstream Maintainer
Hyderabad, India.
#16 lore raw

v4 cover Board: Add Engicam i.MX6 SOMs

Hello,

Quoted 8 lines · Jagan Teki
Quoted 8 lines

Thanks for this new iteration and those contributions. Since you're regularly posting new iterations of this patch series, it would be nice if you could create an account on patchwork, and mark yourself the previous iterations of your patch series as "Superseded". This way, it is easier for the maintainers to keep track of what is the latest version of your patch series that should be considered for review/merging.

Quoted 6 lines
Quoted 3 lines

See https://patchwork.ozlabs.org/project/buildroot/list/. You just need to create an account with the same e-mail address as the one used to send the patches.

I've a patchwork.ozlabs account with different mail id, I guess it is ok to reuse the same. What do you think?

It won't work: patchwork will only allow you to modify the patches for which you are the author, by matching the email of the patchwork account with the email of the patch author.

Best regards,

Thomas

Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
author
#17 lore raw

v4 cover Board: Add Engicam i.MX6 SOMs

Quoted 16 lines · Thomas Petazzoni

Hello,

Quoted 12 lines · Jagan Teki
Quoted 11 lines

Thanks for this new iteration and those contributions. Since you're regularly posting new iterations of this patch series, it would be nice if you could create an account on patchwork, and mark yourself the previous iterations of your patch series as "Superseded". This way, it is easier for the maintainers to keep track of what is the latest version of your patch series that should be considered for review/merging.

See https://patchwork.ozlabs.org/project/buildroot/list/. You just need to create an account with the same e-mail address as the one used to send the patches.

Quoted 6 lines
Quoted 2 lines

I've a patchwork.ozlabs account with different mail id, I guess it is ok to reuse the same. What do you think?

It won't work: patchwork will only allow you to modify the patches for which you are the author, by matching the email of the patchwork account with the email of the patch author.

Created, but I can't mark "Superseded" due to permissions issue if I select 'Delegate to' as you or 'no change'

thanks!

Signature · 4 lines
Jagan Teki
Free Software Engineer | www.openedev.com
U-Boot, Linux | Upstream Maintainer
Hyderabad, India.
#18 lore raw

v4 cover Board: Add Engicam i.MX6 SOMs

Hello,

Quoted 6 lines · Jagan Teki
Quoted 3 lines

It won't work: patchwork will only allow you to modify the patches for which you are the author, by matching the email of the patchwork account with the email of the patch author.

Created, but I can't mark "Superseded" due to permissions issue if I select 'Delegate to' as you or 'no change'

If you can't change the state of your patches, it's because your patchwork account e-mail doesn't match the one of the patches.

Thomas

Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com