[Buildroot] [PATCH v5 1/3] board: Add Vyasa RK3288 board support

[Buildroot] [PATCH v5 1/3] board: Add Vyasa RK3288 board support

[Jagan Teki]

Add Vyasa board, from rk3288 family SOC.

Signed-off-by: Jagan Teki <jagan@amarulasolutions.com>
---
Changes for v5:
- Add host-uboot-tools
- Fix commit message
- Drop Qt5 configs
Changes for v4:
- Use liux-next
- Add linux_gmac.fragment, rockchip gmac as module
- Add evetest command
- enable BR2_LINUX_KERNEL_INSTALL_TARGET
Changes for v3:
- Fix ascending order in DEVELOPERS
- Fix u-boot-dtb.img offset
- Fix extlinux.conf label
Changes for v2:
- Bump to U-Boot v2017.11
- Bump to linux-next

 .gitlab-ci.yml                          |  1 +
 DEVELOPERS                              |  2 ++
 board/amarula/vyasa/extlinux.conf       |  4 +++
 board/amarula/vyasa/genimage.cfg        | 21 +++++++++++++++
 board/amarula/vyasa/linux_gmac.fragment |  3 +++
 board/amarula/vyasa/post-build.sh       |  9 +++++++
 board/amarula/vyasa/readme.txt          | 31 ++++++++++++++++++++++
 configs/amarula_vyasa_rk3288_defconfig  | 46 +++++++++++++++++++++++++++++++++
 8 files changed, 117 insertions(+)
 create mode 100644 board/amarula/vyasa/extlinux.conf
 create mode 100644 board/amarula/vyasa/genimage.cfg
 create mode 100644 board/amarula/vyasa/linux_gmac.fragment
 create mode 100755 board/amarula/vyasa/post-build.sh
 create mode 100644 board/amarula/vyasa/readme.txt
 create mode 100644 configs/amarula_vyasa_rk3288_defconfig

diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index c34d2f7..e3b6510 100644
--- a/.gitlab-ci.yml
+++ b/.gitlab-ci.yml
@@ -62,6 +62,7 @@ acmesystems_aria_g25_128mb_defconfig: *defconfig
 acmesystems_aria_g25_256mb_defconfig: *defconfig
 acmesystems_arietta_g25_128mb_defconfig: *defconfig
 acmesystems_arietta_g25_256mb_defconfig: *defconfig
+amarula_vyasa_rk3288_defconfig: *defconfig
 arcturus_ucp1020_defconfig: *defconfig
 arm_foundationv8_defconfig: *defconfig
 arm_juno_defconfig: *defconfig
diff --git a/DEVELOPERS b/DEVELOPERS
index e4aeae6..181f118 100644
--- a/DEVELOPERS
+++ b/DEVELOPERS
@@ -752,8 +752,10 @@ N:	Ilias Apalodimas <apalos@gmail.com>
 F:	package/keepalived/
 
 N:	Jagan Teki <jagan@amarulasolutions.com>
+F:	board/amarula/
 F:	board/bananapi/
 F:	board/engicam/
+F:	configs/amarula_vyasa_rk3288_defconfig
 F:	configs/bananapi_m1_defconfig
 F:	configs/engicam_imx6qdl_icore_defconfig
 F:	configs/engicam_imx6qdl_icore_qt5_defconfig
diff --git a/board/amarula/vyasa/extlinux.conf b/board/amarula/vyasa/extlinux.conf
new file mode 100644
index 0000000..a8fcc35
--- /dev/null
+++ b/board/amarula/vyasa/extlinux.conf
@@ -0,0 +1,4 @@
+label Vyasa linux-next
+  kernel /boot/uImage
+  devicetree /boot/rk3288-vyasa.dtb
+  append console=ttyS2,115200n8 root=/dev/mmcblk0p1 rootwait
diff --git a/board/amarula/vyasa/genimage.cfg b/board/amarula/vyasa/genimage.cfg
new file mode 100644
index 0000000..fa41de3
--- /dev/null
+++ b/board/amarula/vyasa/genimage.cfg
@@ -0,0 +1,21 @@
+image sdcard.img {
+	hdimage {
+	}
+
+	partition u-boot-tpl-spl-dtb {
+		in-partition-table = "no"
+		image = "u-boot-tpl-spl-dtb.img"
+		offset = 32K
+	}
+
+	partition u-boot-dtb {
+		in-partition-table = "no"
+		image = "u-boot-dtb.img"
+		offset = 8M
+	}
+
+	partition rootfs {
+		partition-type = 0x83
+		image = "rootfs.ext4"
+	}
+}
diff --git a/board/amarula/vyasa/linux_gmac.fragment b/board/amarula/vyasa/linux_gmac.fragment
new file mode 100644
index 0000000..dd458c7
--- /dev/null
+++ b/board/amarula/vyasa/linux_gmac.fragment
@@ -0,0 +1,3 @@
+# Currently kernel mainline exhibits issues when running rockchip gmac
+# on the board, so enable it as loadable module and insert it later
+CONFIG_DWMAC_ROCKCHIP=m
diff --git a/board/amarula/vyasa/post-build.sh b/board/amarula/vyasa/post-build.sh
new file mode 100755
index 0000000..ffbbcde
--- /dev/null
+++ b/board/amarula/vyasa/post-build.sh
@@ -0,0 +1,9 @@
+#!/bin/sh
+
+MKIMAGE=$HOST_DIR/bin/mkimage
+BOARD_DIR="$(dirname $0)"
+
+$MKIMAGE -n rk3288 -T rksd -d $BINARIES_DIR/u-boot-tpl.bin $BINARIES_DIR/u-boot-tpl.img
+cat $BINARIES_DIR/u-boot-tpl.img $BINARIES_DIR/u-boot-spl-dtb.bin > $BINARIES_DIR/u-boot-tpl-spl-dtb.img
+
+install -m 0644 -D $BOARD_DIR/extlinux.conf $TARGET_DIR/boot/extlinux/extlinux.conf
diff --git a/board/amarula/vyasa/readme.txt b/board/amarula/vyasa/readme.txt
new file mode 100644
index 0000000..b95889e
--- /dev/null
+++ b/board/amarula/vyasa/readme.txt
@@ -0,0 +1,31 @@
+Vyasa RK3288
+============
+
+Vyasa is RK3288 based Single board computer with fully supported opensource software.
+
+https://openedev.amarulasolutions.com/display/ODWIKI/Vyasa+RK3288
+
+How to build it
+===============
+
+  $ make amarula_vyasa_rk3288_defconfig
+
+Then you can edit the build options using
+
+  $ make menuconfig
+
+Compile all and build rootfs image:
+
+  $ make
+
+Prepare your SDCard
+===================
+
+Buildroot generates a ready-to-use SD card image that you can flash directly to
+the card. The image will be in output/images/sdcard.img.
+You can write this image directly to an SD card device (i.e. /dev/xxx):
+
+  $ sudo dd if=output/images/sdcard.img of=/dev/xxx
+  $ sudo sync
+
+Finally, you can insert the SD card to the Vyasa RK3288 board, close J4 and boot it.
diff --git a/configs/amarula_vyasa_rk3288_defconfig b/configs/amarula_vyasa_rk3288_defconfig
new file mode 100644
index 0000000..bd7b162
--- /dev/null
+++ b/configs/amarula_vyasa_rk3288_defconfig
@@ -0,0 +1,46 @@
+# Architecture
+BR2_arm=y
+BR2_cortex_a17=y
+BR2_ARM_FPU_NEON_VFPV4=y
+
+# Linux headers same as kernel, a 4.14 series
+BR2_KERNEL_HEADERS_4_14=y
+
+# Bootloader
+BR2_TARGET_UBOOT=y
+BR2_TARGET_UBOOT_BUILD_SYSTEM_KCONFIG=y
+BR2_TARGET_UBOOT_CUSTOM_VERSION=y
+BR2_TARGET_UBOOT_CUSTOM_VERSION_VALUE="2017.11"
+BR2_TARGET_UBOOT_BOARD_DEFCONFIG="vyasa-rk3288"
+BR2_TARGET_UBOOT_NEEDS_DTC=y
+BR2_TARGET_UBOOT_NEEDS_OPENSSL=y
+BR2_TARGET_UBOOT_FORMAT_DTB_IMG=y
+BR2_TARGET_UBOOT_SPL=y
+BR2_TARGET_UBOOT_SPL_NAME="spl/u-boot-spl-dtb.bin tpl/u-boot-tpl.bin"
+
+# Kernel
+BR2_LINUX_KERNEL=y
+BR2_LINUX_KERNEL_CUSTOM_GIT=y
+BR2_LINUX_KERNEL_CUSTOM_REPO_URL="git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git"
+BR2_LINUX_KERNEL_CUSTOM_REPO_VERSION="87f89ace81d0978a1049a92c6a9921de5aa0a9e3"
+BR2_LINUX_KERNEL_DEFCONFIG="multi_v7"
+BR2_LINUX_KERNEL_UIMAGE=y
+BR2_LINUX_KERNEL_UIMAGE_LOADADDR="0x02000000"
+BR2_LINUX_KERNEL_DTS_SUPPORT=y
+BR2_LINUX_KERNEL_INTREE_DTS_NAME="rk3288-vyasa"
+BR2_LINUX_KERNEL_INSTALL_TARGET=y
+BR2_LINUX_KERNEL_CONFIG_FRAGMENT_FILES="board/amarula/vyasa/linux_gmac.fragment"
+
+# Filesystem
+BR2_TARGET_GENERIC_HOSTNAME="vyasa-rk3288"
+BR2_TARGET_GENERIC_ISSUE="Welcome to VYASA RK3288!"
+BR2_TARGET_ROOTFS_EXT2=y
+BR2_TARGET_ROOTFS_EXT2_4=y
+BR2_TARGET_ROOTFS_EXT2_SIZE="512M"
+BR2_PACKAGE_HOST_DOSFSTOOLS=y
+BR2_PACKAGE_HOST_GENIMAGE=y
+BR2_PACKAGE_HOST_MTOOLS=y
+BR2_PACKAGE_HOST_UBOOT_TOOLS=y
+BR2_ROOTFS_POST_IMAGE_SCRIPT="support/scripts/genimage.sh"
+BR2_ROOTFS_POST_SCRIPT_ARGS="-c board/amarula/vyasa/genimage.cfg"
+BR2_ROOTFS_POST_BUILD_SCRIPT="board/amarula/vyasa/post-build.sh"
-- 
1.9.1

[Buildroot] [PATCH v5 2/3] board: vyasa: Add qst5 configuration

[Jagan Teki]

This configuration build qt5 along with MALI T76X
for vyasa rk3288 board.

Signed-off-by: Jagan Teki <jagan@amarulasolutions.com>
---
Changes for v5:
- New patch

 .gitlab-ci.yml                             |  1 +
 DEVELOPERS                                 |  1 +
 board/amarula/vyasa/readme.txt             | 19 ++++++++++
 configs/amarula_vyasa_rk3288_qt5_defconfig | 59 ++++++++++++++++++++++++++++++
 4 files changed, 80 insertions(+)
 create mode 100644 configs/amarula_vyasa_rk3288_qt5_defconfig

diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index e3b6510..ee56fbb 100644
--- a/.gitlab-ci.yml
+++ b/.gitlab-ci.yml
@@ -63,6 +63,7 @@ acmesystems_aria_g25_256mb_defconfig: *defconfig
 acmesystems_arietta_g25_128mb_defconfig: *defconfig
 acmesystems_arietta_g25_256mb_defconfig: *defconfig
 amarula_vyasa_rk3288_defconfig: *defconfig
+amarula_vyasa_rk3288_qt5_defconfig: *defconfig
 arcturus_ucp1020_defconfig: *defconfig
 arm_foundationv8_defconfig: *defconfig
 arm_juno_defconfig: *defconfig
diff --git a/DEVELOPERS b/DEVELOPERS
index 181f118..639c49a 100644
--- a/DEVELOPERS
+++ b/DEVELOPERS
@@ -756,6 +756,7 @@ F:	board/amarula/
 F:	board/bananapi/
 F:	board/engicam/
 F:	configs/amarula_vyasa_rk3288_defconfig
+F:	configs/amarula_vyasa_rk3288_qt5_defconfig
 F:	configs/bananapi_m1_defconfig
 F:	configs/engicam_imx6qdl_icore_defconfig
 F:	configs/engicam_imx6qdl_icore_qt5_defconfig
diff --git a/board/amarula/vyasa/readme.txt b/board/amarula/vyasa/readme.txt
index b95889e..167c594 100644
--- a/board/amarula/vyasa/readme.txt
+++ b/board/amarula/vyasa/readme.txt
@@ -29,3 +29,22 @@ You can write this image directly to an SD card device (i.e. /dev/xxx):
   $ sudo sync
 
 Finally, you can insert the SD card to the Vyasa RK3288 board, close J4 and boot it.
+
+Testing graphics on Vysa RK3288
+===============================
+
+Built Mali T76X, Qt5 and demo application:
+
+   $ make amarula_vyasa_rk3288_qt5_defconfig
+   $ make
+
+Test procedure:
+- insert require modules
+# modprobe -a rockchipdrm
+# modprobe -a governor_simpleondemand
+
+- build kernel mali driver as module and insert
+
+- run qt hellowindow
+# cd /usr/lib/qt/examples/opengl/
+# ./hellowindow/hellowindow
diff --git a/configs/amarula_vyasa_rk3288_qt5_defconfig b/configs/amarula_vyasa_rk3288_qt5_defconfig
new file mode 100644
index 0000000..29fc2a6
--- /dev/null
+++ b/configs/amarula_vyasa_rk3288_qt5_defconfig
@@ -0,0 +1,59 @@
+# Architecture
+BR2_arm=y
+BR2_cortex_a17=y
+BR2_ARM_FPU_NEON_VFPV4=y
+
+# Linux headers same as kernel, a 4.14 series
+BR2_KERNEL_HEADERS_4_14=y
+
+# Bootloader
+BR2_TARGET_UBOOT=y
+BR2_TARGET_UBOOT_BUILD_SYSTEM_KCONFIG=y
+BR2_TARGET_UBOOT_CUSTOM_VERSION=y
+BR2_TARGET_UBOOT_CUSTOM_VERSION_VALUE="2017.11"
+BR2_TARGET_UBOOT_BOARD_DEFCONFIG="vyasa-rk3288"
+BR2_TARGET_UBOOT_NEEDS_DTC=y
+BR2_TARGET_UBOOT_NEEDS_OPENSSL=y
+BR2_TARGET_UBOOT_FORMAT_DTB_IMG=y
+BR2_TARGET_UBOOT_SPL=y
+BR2_TARGET_UBOOT_SPL_NAME="spl/u-boot-spl-dtb.bin tpl/u-boot-tpl.bin"
+
+# Kernel
+BR2_LINUX_KERNEL=y
+BR2_LINUX_KERNEL_CUSTOM_GIT=y
+BR2_LINUX_KERNEL_CUSTOM_REPO_URL="git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git"
+BR2_LINUX_KERNEL_CUSTOM_REPO_VERSION="87f89ace81d0978a1049a92c6a9921de5aa0a9e3"
+BR2_LINUX_KERNEL_DEFCONFIG="multi_v7"
+BR2_LINUX_KERNEL_UIMAGE=y
+BR2_LINUX_KERNEL_UIMAGE_LOADADDR="0x02000000"
+BR2_LINUX_KERNEL_DTS_SUPPORT=y
+BR2_LINUX_KERNEL_INTREE_DTS_NAME="rk3288-vyasa"
+BR2_LINUX_KERNEL_INSTALL_TARGET=y
+BR2_LINUX_KERNEL_CONFIG_FRAGMENT_FILES="board/amarula/vyasa/linux_gmac.fragment"
+
+# Filesystem
+BR2_TARGET_GENERIC_HOSTNAME="vyasa-rk3288"
+BR2_TARGET_GENERIC_ISSUE="Welcome to VYASA RK3288!"
+BR2_TARGET_ROOTFS_EXT2=y
+BR2_TARGET_ROOTFS_EXT2_4=y
+BR2_TARGET_ROOTFS_EXT2_SIZE="512M"
+BR2_PACKAGE_HOST_DOSFSTOOLS=y
+BR2_PACKAGE_HOST_GENIMAGE=y
+BR2_PACKAGE_HOST_MTOOLS=y
+BR2_PACKAGE_HOST_UBOOT_TOOLS=y
+BR2_ROOTFS_POST_IMAGE_SCRIPT="support/scripts/genimage.sh"
+BR2_ROOTFS_POST_SCRIPT_ARGS="-c board/amarula/vyasa/genimage.cfg"
+BR2_ROOTFS_POST_BUILD_SCRIPT="board/amarula/vyasa/post-build.sh"
+
+# mali t76x dependency
+BR2_TOOLCHAIN_BUILDROOT_GLIBC=y
+
+# qt5 dependency
+BR2_TOOLCHAIN_BUILDROOT_CXX=y
+
+# qt5
+BR2_PACKAGE_QT5=y
+BR2_PACKAGE_QT5BASE_EXAMPLES=y
+BR2_PACKAGE_QT5BASE_GUI=y
+BR2_PACKAGE_QT5BASE_EGLFS=y
+BR2_PACKAGE_MALI_T76X=y
-- 
1.9.1

[Buildroot] [PATCH v5 3/3] board: Add Tinker RK3288 board support

[Jagan Teki]

Add Tinker board, from rk3288 family SOC.

Signed-off-by: Jagan Teki <jagan@amarulasolutions.com>
---
Changes for v5:
- Add host-uboot-tools
- Fix commit message
- Drop Qt5 configs
Changes for v4:
- enable BR2_LINUX_KERNEL_INSTALL_TARGET
- enable BR2_TARGET_UBOOT_FORMAT_DTB_BINe
- Create single u-boot binary
- Use linux-4.12 along with same headers

 .gitlab-ci.yml                       |  1 +
 DEVELOPERS                           |  2 ++
 board/asus/tinker/extlinux.conf      |  4 ++++
 board/asus/tinker/genimage.cfg       | 15 ++++++++++++
 board/asus/tinker/post-build.sh      |  9 ++++++++
 board/asus/tinker/readme.txt         | 37 +++++++++++++++++++++++++++++
 configs/asus_tinker_rk3288_defconfig | 45 ++++++++++++++++++++++++++++++++++++
 7 files changed, 113 insertions(+)
 create mode 100644 board/asus/tinker/extlinux.conf
 create mode 100644 board/asus/tinker/genimage.cfg
 create mode 100755 board/asus/tinker/post-build.sh
 create mode 100644 board/asus/tinker/readme.txt
 create mode 100644 configs/asus_tinker_rk3288_defconfig

diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index ee56fbb..0435b12 100644
--- a/.gitlab-ci.yml
+++ b/.gitlab-ci.yml
@@ -70,6 +70,7 @@ arm_juno_defconfig: *defconfig
 armadeus_apf27_defconfig: *defconfig
 armadeus_apf28_defconfig: *defconfig
 armadeus_apf51_defconfig: *defconfig
+asus_tinker_rk3288_defconfig: *defconfig
 at91sam9260eknf_defconfig: *defconfig
 at91sam9g20dfc_defconfig: *defconfig
 at91sam9g45m10ek_defconfig: *defconfig
diff --git a/DEVELOPERS b/DEVELOPERS
index 639c49a..1bb0e4f 100644
--- a/DEVELOPERS
+++ b/DEVELOPERS
@@ -753,10 +753,12 @@ F:	package/keepalived/
 
 N:	Jagan Teki <jagan@amarulasolutions.com>
 F:	board/amarula/
+F:	board/asus/
 F:	board/bananapi/
 F:	board/engicam/
 F:	configs/amarula_vyasa_rk3288_defconfig
 F:	configs/amarula_vyasa_rk3288_qt5_defconfig
+F:	configs/asus_tinker_rk3288_defconfig
 F:	configs/bananapi_m1_defconfig
 F:	configs/engicam_imx6qdl_icore_defconfig
 F:	configs/engicam_imx6qdl_icore_qt5_defconfig
diff --git a/board/asus/tinker/extlinux.conf b/board/asus/tinker/extlinux.conf
new file mode 100644
index 0000000..136af0d
--- /dev/null
+++ b/board/asus/tinker/extlinux.conf
@@ -0,0 +1,4 @@
+label Tinker linux-next
+  kernel /boot/uImage
+  devicetree /boot/rk3288-tinker.dtb
+  append console=ttyS2,115200n8 root=/dev/mmcblk0p1 rootwait
diff --git a/board/asus/tinker/genimage.cfg b/board/asus/tinker/genimage.cfg
new file mode 100644
index 0000000..a4b1e8d
--- /dev/null
+++ b/board/asus/tinker/genimage.cfg
@@ -0,0 +1,15 @@
+image sdcard.img {
+	hdimage {
+	}
+
+	partition u-boot-spl-dtb {
+		in-partition-table = "no"
+		image = "u-boot-spl-dtb.img"
+		offset = 32K
+	}
+
+	partition rootfs {
+		partition-type = 0x83
+		image = "rootfs.ext4"
+	}
+}
diff --git a/board/asus/tinker/post-build.sh b/board/asus/tinker/post-build.sh
new file mode 100755
index 0000000..8108ed8
--- /dev/null
+++ b/board/asus/tinker/post-build.sh
@@ -0,0 +1,9 @@
+#!/bin/sh
+
+MKIMAGE=$HOST_DIR/bin/mkimage
+BOARD_DIR="$(dirname $0)"
+
+$MKIMAGE -n rk3288 -T rksd -d $BINARIES_DIR/u-boot-spl-dtb.bin $BINARIES_DIR/u-boot-spl-dtb.img
+cat $BINARIES_DIR/u-boot-dtb.bin >> $BINARIES_DIR/u-boot-spl-dtb.img
+
+install -m 0644 -D $BOARD_DIR/extlinux.conf $TARGET_DIR/boot/extlinux/extlinux.conf
diff --git a/board/asus/tinker/readme.txt b/board/asus/tinker/readme.txt
new file mode 100644
index 0000000..7372d29
--- /dev/null
+++ b/board/asus/tinker/readme.txt
@@ -0,0 +1,37 @@
+Tinker RK3288
+=============
+
+Tinker Board is a Single Board Computer (SBC) in an ultra-small form
+factor that offers class-leading performance while leveraging outstanding
+mechanical compatibility.
+
+Tinker link:
+https://www.asus.com/in/Single-Board-Computer/Tinker-Board/
+
+Wiki link:
+https://openedev.amarulasolutions.com/display/ODWIKI/Tinker+RK3288
+
+How to build it
+===============
+
+  $ make asus_tinker_rk3288_defconfig
+
+Then you can edit the build options using
+
+  $ make menuconfig
+
+Compile all and build rootfs image:
+
+  $ make
+
+Prepare your SDCard
+===================
+
+Buildroot generates a ready-to-use SD card image that you can flash directly to
+the card. The image will be in output/images/sdcard.img.
+You can write this image directly to an SD card device (i.e. /dev/xxx):
+
+  $ sudo dd if=output/images/sdcard.img of=/dev/xxx
+  $ sudo sync
+
+Finally, you can insert the SD card to the Tinker RK3288 board and boot it.
diff --git a/configs/asus_tinker_rk3288_defconfig b/configs/asus_tinker_rk3288_defconfig
new file mode 100644
index 0000000..22e9bcd
--- /dev/null
+++ b/configs/asus_tinker_rk3288_defconfig
@@ -0,0 +1,45 @@
+# Architecture
+BR2_arm=y
+BR2_cortex_a17=y
+BR2_ARM_FPU_NEON_VFPV4=y
+
+# Linux headers same as kernel, a 4.12 series
+BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_4_12=y
+
+# Bootloader
+BR2_TARGET_UBOOT=y
+BR2_TARGET_UBOOT_BUILD_SYSTEM_KCONFIG=y
+BR2_TARGET_UBOOT_CUSTOM_VERSION=y
+BR2_TARGET_UBOOT_CUSTOM_VERSION_VALUE="2017.11"
+BR2_TARGET_UBOOT_BOARD_DEFCONFIG="tinker-rk3288"
+BR2_TARGET_UBOOT_NEEDS_DTC=y
+BR2_TARGET_UBOOT_NEEDS_OPENSSL=y
+BR2_TARGET_UBOOT_FORMAT_DTB_IMG=y
+BR2_TARGET_UBOOT_FORMAT_DTB_BIN=y
+BR2_TARGET_UBOOT_SPL=y
+BR2_TARGET_UBOOT_SPL_NAME="spl/u-boot-spl-dtb.bin"
+
+# Kernel
+BR2_LINUX_KERNEL=y
+BR2_LINUX_KERNEL_CUSTOM_VERSION=y
+BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="4.12"
+BR2_LINUX_KERNEL_DEFCONFIG="multi_v7"
+BR2_LINUX_KERNEL_UIMAGE=y
+BR2_LINUX_KERNEL_UIMAGE_LOADADDR="0x02000000"
+BR2_LINUX_KERNEL_DTS_SUPPORT=y
+BR2_LINUX_KERNEL_INTREE_DTS_NAME="rk3288-tinker"
+BR2_LINUX_KERNEL_INSTALL_TARGET=y
+
+# Filesystem
+BR2_TARGET_GENERIC_HOSTNAME="tinker-rk3288"
+BR2_TARGET_GENERIC_ISSUE="Welcome to TINKER RK3288!"
+BR2_TARGET_ROOTFS_EXT2=y
+BR2_TARGET_ROOTFS_EXT2_4=y
+BR2_TARGET_ROOTFS_EXT2_SIZE="512M"
+BR2_PACKAGE_HOST_DOSFSTOOLS=y
+BR2_PACKAGE_HOST_GENIMAGE=y
+BR2_PACKAGE_HOST_MTOOLS=y
+BR2_PACKAGE_HOST_UBOOT_TOOLS=y
+BR2_ROOTFS_POST_IMAGE_SCRIPT="support/scripts/genimage.sh"
+BR2_ROOTFS_POST_SCRIPT_ARGS="-c board/asus/tinker/genimage.cfg"
+BR2_ROOTFS_POST_BUILD_SCRIPT="board/asus/tinker/post-build.sh"
-- 
1.9.1

[Buildroot] [PATCH v5 1/3] board: Add Vyasa RK3288 board support

[Sergey Matyukevich]

Hello,


> Add Vyasa board, from rk3288 family SOC.
> 
> Signed-off-by: Jagan Teki <jagan@amarulasolutions.com>
> ---
> Changes for v5:
> - Add host-uboot-tools
> - Fix commit message
> - Drop Qt5 configs
> Changes for v4:
> - Use liux-next
> - Add linux_gmac.fragment, rockchip gmac as module
> - Add evetest command
> - enable BR2_LINUX_KERNEL_INSTALL_TARGET
> Changes for v3:
> - Fix ascending order in DEVELOPERS
> - Fix u-boot-dtb.img offset
> - Fix extlinux.conf label
> Changes for v2:
> - Bump to U-Boot v2017.11
> - Bump to linux-next

...

> +# Kernel
> +BR2_LINUX_KERNEL=y
> +BR2_LINUX_KERNEL_CUSTOM_GIT=y
> +BR2_LINUX_KERNEL_CUSTOM_REPO_URL="git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git"
> +BR2_LINUX_KERNEL_CUSTOM_REPO_VERSION="87f89ace81d0978a1049a92c6a9921de5aa0a9e3"

As Thomas mentioned in his review for v4, no way to use linux-next git tree.
It is being rebased all the time. So changing commit ID is not going to help:
it will be changed over and over again.

If you want to add this board to Buildroot before it shows up in mainline, why
don't you use latest stable kernel release and add several patches into the
board directory? You may take a look at nanopi-m1-plus which adds its full
dts as a patch.

Regards,
Sergey

[Buildroot] [PATCH v5 1/3] board: Add Vyasa RK3288 board support

[Jagan Teki]

On Wed, Nov 29, 2017 at 12:15 PM, Sergey Matyukevich <geomatsi@gmail.com> wrote:
> Hello,
>
>
>> Add Vyasa board, from rk3288 family SOC.
>>
>> Signed-off-by: Jagan Teki <jagan@amarulasolutions.com>
>> ---
>> Changes for v5:
>> - Add host-uboot-tools
>> - Fix commit message
>> - Drop Qt5 configs
>> Changes for v4:
>> - Use liux-next
>> - Add linux_gmac.fragment, rockchip gmac as module
>> - Add evetest command
>> - enable BR2_LINUX_KERNEL_INSTALL_TARGET
>> Changes for v3:
>> - Fix ascending order in DEVELOPERS
>> - Fix u-boot-dtb.img offset
>> - Fix extlinux.conf label
>> Changes for v2:
>> - Bump to U-Boot v2017.11
>> - Bump to linux-next
>
> ...
>
>> +# Kernel
>> +BR2_LINUX_KERNEL=y
>> +BR2_LINUX_KERNEL_CUSTOM_GIT=y
>> +BR2_LINUX_KERNEL_CUSTOM_REPO_URL="git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git"
>> +BR2_LINUX_KERNEL_CUSTOM_REPO_VERSION="87f89ace81d0978a1049a92c6a9921de5aa0a9e3"
>
> As Thomas mentioned in his review for v4, no way to use linux-next git tree.
> It is being rebased all the time. So changing commit ID is not going to help:
> it will be changed over and over again.

Thomas never said to use the linux-next, but instead he mentioned to
not use the last sha1 which always changed during rebase. So the sha1
I have used here specific to this board which shouldn't change even
linux-next rebased.

thanks!
-- 
Jagan Teki
Senior Linux Kernel Engineer | Amarula Solutions
U-Boot, Linux | Upstream Maintainer
Hyderabad, India.

[Buildroot] [PATCH v5 1/3] board: Add Vyasa RK3288 board support

[Sergey Matyukevich]

> >> Add Vyasa board, from rk3288 family SOC.
> >>
> >> Signed-off-by: Jagan Teki <jagan@amarulasolutions.com>
> >> ---
> >> Changes for v5:
> >> - Add host-uboot-tools
> >> - Fix commit message
> >> - Drop Qt5 configs
> >> Changes for v4:
> >> - Use liux-next
> >> - Add linux_gmac.fragment, rockchip gmac as module
> >> - Add evetest command
> >> - enable BR2_LINUX_KERNEL_INSTALL_TARGET
> >> Changes for v3:
> >> - Fix ascending order in DEVELOPERS
> >> - Fix u-boot-dtb.img offset
> >> - Fix extlinux.conf label
> >> Changes for v2:
> >> - Bump to U-Boot v2017.11
> >> - Bump to linux-next
> >
> > ...
> >
> >> +# Kernel
> >> +BR2_LINUX_KERNEL=y
> >> +BR2_LINUX_KERNEL_CUSTOM_GIT=y
> >> +BR2_LINUX_KERNEL_CUSTOM_REPO_URL="git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git"
> >> +BR2_LINUX_KERNEL_CUSTOM_REPO_VERSION="87f89ace81d0978a1049a92c6a9921de5aa0a9e3"
> >
> > As Thomas mentioned in his review for v4, no way to use linux-next git tree.
> > It is being rebased all the time. So changing commit ID is not going to help:
> > it will be changed over and over again.
> 
> Thomas never said to use the linux-next, but instead he mentioned to
> not use the last sha1 which always changed during rebase. So the sha1
> I have used here specific to this board which shouldn't change even
> linux-next rebased.

Yeah, the main point was _not_ to use linux-next at all.
I suggest you to check the review comments for v4 once again.

Regards,
Sergey

[Buildroot] [PATCH v5 1/3] board: Add Vyasa RK3288 board support

[Thomas Petazzoni]

Hello,

On Wed, 29 Nov 2017 12:21:24 +0530, Jagan Teki wrote:

> > As Thomas mentioned in his review for v4, no way to use linux-next git tree.
> > It is being rebased all the time. So changing commit ID is not going to help:
> > it will be changed over and over again.  
> 
> Thomas never said to use the linux-next, but instead he mentioned to
> not use the last sha1 which always changed during rebase. So the sha1
> I have used here specific to this board which shouldn't change even
> linux-next rebased.

What you're saying here doesn't make sense.

Either the commit you're referring to is part of Linus tree (and
therefore is stable and will never change), but in this case, there is
no reason to use linux-next at all.

Or the commit you're referring to is not part of Linus tree, but is
really on top of it, part of linux-next, and in this case, the commit
is not stable and it will disappear every day, as linux-next is rebased
every day.

So let's be clear: using linux-next is *not* possible as it simply
doesn't work. Remove your download directory, and try again to build
your defconfig: you will see that it fails.

Best regards,

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

[Buildroot] [PATCH v5 1/3] board: Add Vyasa RK3288 board support

[Baruch Siach]

Hi Thomas,

On Wed, Nov 29, 2017 at 08:53:34AM +0100, Thomas Petazzoni wrote:
> On Wed, 29 Nov 2017 12:21:24 +0530, Jagan Teki wrote:
> 
> > > As Thomas mentioned in his review for v4, no way to use linux-next git tree.
> > > It is being rebased all the time. So changing commit ID is not going to help:
> > > it will be changed over and over again.  
> > 
> > Thomas never said to use the linux-next, but instead he mentioned to
> > not use the last sha1 which always changed during rebase. So the sha1
> > I have used here specific to this board which shouldn't change even
> > linux-next rebased.
> 
> What you're saying here doesn't make sense.
> 
> Either the commit you're referring to is part of Linus tree (and
> therefore is stable and will never change), but in this case, there is
> no reason to use linux-next at all.
> 
> Or the commit you're referring to is not part of Linus tree, but is
> really on top of it, part of linux-next, and in this case, the commit
> is not stable and it will disappear every day, as linux-next is rebased
> every day.

I seems that linux-next preserves older next-[date] tags. It currently goes 
back to next-20170831. The linux-next-history.git tree carries even older 
tags, back to next-20160118. So a specific commit in linux-next{-history} 
should not disappear overnight.

I do agree, though, that having a board/platform specific git tree, or a set 
of patches is easier to work with.

baruch

-- 
     http://baruch.siach.name/blog/                  ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -