[PATCH 0/7] introduce rockchip offical linux support to meta-rockchip

[PATCH 0/7] introduce rockchip offical linux support to meta-rockchip

[Jacob Chen]

This series of patches add below features, will add more supports in the future(medias, more chips).

1. rockchip 4.4 kernel

Rockchip 4.4 kernel is currently the latest version of the rockchip offical kernel, will be an upstream tracking branch. 
We regularly release the kernel through github. It support all rockchip 64-bit chips and a few 32-bit chips.

2. rockchip next-dev U-boot

Rockchip next-dev U-boot is the next generation of rockchip u-boot, will also be an upstream tracking branch.
At present, this branch is just a rebased upstream u-boot.

3. graphics

We have plans for the acceleration in wayland, x11 in the rockchip platform, but in this series of patches, we only include the mali bianry support.

4. rockchip-next-image

Being different from the previous rk-u-boot which use parameter, next-dev u-boot use gpt partition, so it needs to generate a different image.


Jacob Chen (7):
  recipes-kernel: linux-rockchip: Add new recipe for 4.4
  machine: Add machine file for the rk3288 linux Boards
  machine: firefly: use linux-rockchip by default
  recipes-graphics: Add support for mali-userspace
  recipes-bsp: add u-boot-rockchip support
  rk3288.inc: add some variables
  rockchip-next-image: introduce image for rockchip next-dev u-boot

 classes/rockchip-next-image.bbclass                | 130 +++++++++++++++++++++
 conf/machine/evb-rk3288.conf                       |  12 ++
 conf/machine/fennec-rk3288.conf                    |  12 ++
 conf/machine/firefly-rk3288.conf                   |   4 +
 conf/machine/include/rk-linux.inc                  |  20 ++++
 conf/machine/include/rk3288.inc                    |  10 +-
 conf/machine/tinker-rk3288.conf                    |  13 +++
 recipes-bsp/u-boot/u-boot-rockchip_next.bb         |  17 +++
 recipes-graphics/mali-userspace/mali-userspace.inc |  57 +++++++++
 .../mali-userspace/mali-userspace_t76x.bb          |  18 +++
 recipes-graphics/mesa/mesa_%.bbappend              |   9 ++
 recipes-kernel/linux/linux-rockchip_4.4.bb         |  20 ++++
 12 files changed, 321 insertions(+), 1 deletion(-)
 create mode 100644 classes/rockchip-next-image.bbclass
 create mode 100644 conf/machine/evb-rk3288.conf
 create mode 100644 conf/machine/fennec-rk3288.conf
 create mode 100644 conf/machine/include/rk-linux.inc
 create mode 100644 conf/machine/tinker-rk3288.conf
 create mode 100644 recipes-bsp/u-boot/u-boot-rockchip_next.bb
 create mode 100644 recipes-graphics/mali-userspace/mali-userspace.inc
 create mode 100644 recipes-graphics/mali-userspace/mali-userspace_t76x.bb
 create mode 100644 recipes-graphics/mesa/mesa_%.bbappend
 create mode 100644 recipes-kernel/linux/linux-rockchip_4.4.bb

-- 
2.7.4

[PATCH 1/7] recipes-kernel: linux-rockchip: Add new recipe for 4.4

[Jacob Chen]

Rockchip 4.4 kernel is currently the latest version of the rockchip offical kernel,
will be an upstream tracking branch.
We regularly release the kernel through github.
It support all rockchip 64-bit chips and a few 32-bit chips.

Signed-off-by: Jacob Chen <jacob-chen@iotwrt.com>
---
 recipes-kernel/linux/linux-rockchip_4.4.bb | 20 ++++++++++++++++++++
 1 file changed, 20 insertions(+)
 create mode 100644 recipes-kernel/linux/linux-rockchip_4.4.bb

diff --git a/recipes-kernel/linux/linux-rockchip_4.4.bb b/recipes-kernel/linux/linux-rockchip_4.4.bb
new file mode 100644
index 0000000..ca3674e
--- /dev/null
+++ b/recipes-kernel/linux/linux-rockchip_4.4.bb
@@ -0,0 +1,20 @@
+# Copyright (C) 2017 Fuzhou Rockchip Electronics Co., Ltd
+# Released under the MIT license (see COPYING.MIT for the terms)
+
+require recipes-kernel/linux/linux-yocto.inc
+
+SRC_URI = "git://github.com/rockchip-linux/kernel.git;branch=release-4.4;"
+
+SRCREV = "${AUTOREV}"
+LINUX_VERSION = "4.4.41"
+# Override local version in order to use the one generated by linux build system
+# And not "yocto-standard"
+LINUX_VERSION_EXTENSION = ""
+PR = "r1"
+PV = "${LINUX_VERSION}"
+
+# Include only supported boards for now
+COMPATIBLE_MACHINE = "(rk3288)"
+deltask kernel_configme
+
+KBUILD_DEFCONFIG = "rockchip_linux_defconfig"
-- 
2.7.4

[PATCH 2/7] machine: Add machine file for the rk3288 linux Boards

[Jacob Chen]

Evb-rk3288 is the offical evaluate board, add it to help myself develop.

Fennec-rk3288 and Tinker-rk3288 is rk3288 based SBCs.
    .
Tinker Boards:
http://www.cnx-software.com/2017/01/05/asus-tinker-board-is-a-raspberry-pi-3-alternative-based-on-rockchip-rk3288-processor/

Signed-off-by: Jacob Chen <jacob-chen@rock-chips.com>
---
 conf/machine/evb-rk3288.conf      | 12 ++++++++++++
 conf/machine/fennec-rk3288.conf   | 12 ++++++++++++
 conf/machine/include/rk-linux.inc | 20 ++++++++++++++++++++
 conf/machine/tinker-rk3288.conf   | 13 +++++++++++++
 4 files changed, 57 insertions(+)
 create mode 100644 conf/machine/evb-rk3288.conf
 create mode 100644 conf/machine/fennec-rk3288.conf
 create mode 100644 conf/machine/include/rk-linux.inc
 create mode 100644 conf/machine/tinker-rk3288.conf

diff --git a/conf/machine/evb-rk3288.conf b/conf/machine/evb-rk3288.conf
new file mode 100644
index 0000000..88a5f78
--- /dev/null
+++ b/conf/machine/evb-rk3288.conf
@@ -0,0 +1,12 @@
+# Copyright (C) 2017 Fuzhou Rockchip Electronics Co., Ltd
+# Released under the MIT license (see COPYING.MIT for the terms)
+
+#@TYPE: Machine
+#@NAME: EVB 3288
+
+include conf/machine/include/rk3288.inc
+include conf/machine/include/rk-linux.inc
+
+KERNEL_DEVICETREE = "rk3288-evb-act8846.dtb"
+
+UBOOT_MACHINE = "evb-rk3288_defconfig"
diff --git a/conf/machine/fennec-rk3288.conf b/conf/machine/fennec-rk3288.conf
new file mode 100644
index 0000000..a85045f
--- /dev/null
+++ b/conf/machine/fennec-rk3288.conf
@@ -0,0 +1,12 @@
+# Copyright (C) 2017 Fuzhou Rockchip Electronics Co., Ltd
+# Released under the MIT license (see COPYING.MIT for the terms)
+
+#@TYPE: Machine
+#@NAME: FENNEC RK3288
+
+include conf/machine/include/rk3288.inc
+include conf/machine/include/rk-linux.inc
+
+KERNEL_DEVICETREE = "rk3288-fennec.dtb"
+
+UBOOT_MACHINE = "fennec-rk3288_defconfig"
diff --git a/conf/machine/include/rk-linux.inc b/conf/machine/include/rk-linux.inc
new file mode 100644
index 0000000..6abaa0d
--- /dev/null
+++ b/conf/machine/include/rk-linux.inc
@@ -0,0 +1,20 @@
+# Rockchip BSP default settings
+
+PREFERRED_PROVIDER_virtual/egl = "mali-userspace"
+PREFERRED_PROVIDER_virtual/libgles1 = "mali-userspace"
+PREFERRED_PROVIDER_virtual/libgles2 = "mali-userspace"
+PREFERRED_PROVIDER_virtual/libopencl = "mali-userspace"
+
+# Workaround: libmali.so provided by rk having no SONAME field in it
+# so add it to fix rdepends problems
+ASSUME_SHLIBS += "libEGL.so:mali-userspace"
+ASSUME_SHLIBS += "libGLESv1_CM.so:mali-userspace"
+ASSUME_SHLIBS += "libGLESv2.so:mali-userspace"
+ASSUME_SHLIBS += "libOpenCL.so:mali-userspace"
+ASSUME_SHLIBS += "libgbm.so:mali-userspace"
+ASSUME_SHLIBS += "libwayland-egl.so:mali-userspace"
+
+PREFERRED_PROVIDER_virtual/kernel = "linux-rockchip"
+PREFERRED_PROVIDER_virtual/bootloader = "u-boot-rockchip"
+
+IMAGE_CLASSES += "rockchip-next-image"
diff --git a/conf/machine/tinker-rk3288.conf b/conf/machine/tinker-rk3288.conf
new file mode 100644
index 0000000..0464133
--- /dev/null
+++ b/conf/machine/tinker-rk3288.conf
@@ -0,0 +1,13 @@
+# Copyright (C) 2017 Fuzhou Rockchip Electronics Co., Ltd
+# Released under the MIT license (see COPYING.MIT for the terms)
+
+#@TYPE: Machine
+#@NAME: Tinker RK3288
+#@DESCRIPTION: ASUS Tinker Board is a Raspberry Pi 3 Alternative based on Rockchip RK3288 Processor.
+
+include conf/machine/include/rk3288.inc
+include conf/machine/include/rk-linux.inc
+
+KERNEL_DEVICETREE = "rk3288-miniarm.dtb"
+
+UBOOT_MACHINE = "miniarm-rk3288_defconfig"
-- 
2.7.4

[PATCH 3/7] machine: firefly: use linux-rockchip by default

[Jacob Chen]

This is the kernel vendor that supports all hw components for this board,
so we use it by default.

Signed-off-by: Jacob Chen <jacob-chen@iotwrt.com>
---
 conf/machine/firefly-rk3288.conf | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/conf/machine/firefly-rk3288.conf b/conf/machine/firefly-rk3288.conf
index 8fa005d..47e63e1 100644
--- a/conf/machine/firefly-rk3288.conf
+++ b/conf/machine/firefly-rk3288.conf
@@ -7,4 +7,8 @@
 #http://www.t-firefly.com/en/
 
 include conf/machine/include/rk3288.inc
+include conf/machine/include/rk-linux.inc
+
 KERNEL_DEVICETREE = "rk3288-firefly.dtb"
+
+UBOOT_MACHINE = "firefly-rk3288_defconfig"
-- 
2.7.4

[PATCH 4/7] recipes-graphics: Add support for mali-userspace

[Jacob Chen]

Add support for mali userspace which are binaries that can be run
with weston and X11.

Signed-off-by: Jacob Chen <jacob-chen@iotwrt.com>
---
 recipes-graphics/mali-userspace/mali-userspace.inc | 57 ++++++++++++++++++++++
 .../mali-userspace/mali-userspace_t76x.bb          | 18 +++++++
 recipes-graphics/mesa/mesa_%.bbappend              |  9 ++++
 3 files changed, 84 insertions(+)
 create mode 100644 recipes-graphics/mali-userspace/mali-userspace.inc
 create mode 100644 recipes-graphics/mali-userspace/mali-userspace_t76x.bb
 create mode 100644 recipes-graphics/mesa/mesa_%.bbappend

diff --git a/recipes-graphics/mali-userspace/mali-userspace.inc b/recipes-graphics/mali-userspace/mali-userspace.inc
new file mode 100644
index 0000000..d40f583
--- /dev/null
+++ b/recipes-graphics/mali-userspace/mali-userspace.inc
@@ -0,0 +1,57 @@
+SUMMARY = "Userspace mali driver for Midgard-T76x"
+DESCRIPTION = "Userspace mali driver for Midgard-T76x"
+LICENSE = "CLOSED"
+SECTION = "libs"
+
+DEPENDS = "libdrm"
+DEPENDS += "${@bb.utils.contains("DISTRO_FEATURES", "wayland", " mesa", " ", d)}"
+
+PROVIDES += "virtual/egl virtual/libgles1 virtual/libgles2 virtual/libopencl libgbm"
+PROVIDES += "${@bb.utils.contains("DISTRO_FEATURES", "wayland", " virtual/libwayland-egl", " ", d)}"
+
+S = "${WORKDIR}"
+
+SRC_URI = "git://github.com/rockchip-linux/libmali.git;branch=rockchip;"
+SRCREV_pn-${PN} = "${AUTOREV}"
+
+INSANE_SKIP_${PN} = "already-stripped ldflags dev-so"
+
+INHIBIT_PACKAGE_DEBUG_SPLIT = "1"
+INHIBIT_PACKAGE_STRIP = "1"
+
+USE_X11 = "${@bb.utils.contains("DISTRO_FEATURES", "x11", "yes", "no", d)}"
+USE_WL = "${@bb.utils.contains("DISTRO_FEATURES", "wayland", "yes", "no", d)}"
+
+do_configure[noexec] = "1"
+do_compile[noexec] = "1"
+
+do_install () {
+	# Create MALI manifest
+	install -m 755 -d ${D}/${libdir}
+	if [ "${USE_X11}" = "yes" ]; then
+		install ${S}/x11/libmali.so ${D}/${libdir}
+	elif [ "${USE_WL}" = "yes" ]; then
+		install ${S}/wayland/libmali.so ${D}/${libdir}
+	fi
+
+	ln -sf libmali.so ${D}/${libdir}/libEGL.so
+	ln -sf libmali.so ${D}/${libdir}/libGLESv1_CM.so
+	ln -sf libmali.so ${D}/${libdir}/libGLESv2.so
+	ln -sf libmali.so ${D}/${libdir}/libOpenCL.so
+	ln -sf libmali.so ${D}/${libdir}/libgbm.so
+
+	if [ "${USE_WL}" = "yes" ]; then
+		ln -sf libmali.so ${D}/${libdir}/libwayland-egl.so
+	fi
+}
+
+PACKAGES = "${PN}"
+FILES_${PN} += "${libdir}/*.so"
+
+RREPLACES_${PN} = "libegl libgles1 libglesv1-cm1 libgles2 libglesv2-2 libgbm"
+RPROVIDES_${PN} = "libegl libgles1 libglesv1-cm1 libgles2 libglesv2-2 libgbm"
+RCONFLICTS_${PN} = "libegl libgles1 libglesv1-cm1 libgles2 libglesv2-2 libgbm"
+
+# Workaround: libmali.so provided by rk having no SONAME field in it
+# so add it to fix rdepends problems
+RPROVIDES_${PN} += "libwayland-egl.so libgbm.so libGLESv1_CM.so libGLESv2.so libEGL.so libOpenCL.so"
diff --git a/recipes-graphics/mali-userspace/mali-userspace_t76x.bb b/recipes-graphics/mali-userspace/mali-userspace_t76x.bb
new file mode 100644
index 0000000..3281ac0
--- /dev/null
+++ b/recipes-graphics/mali-userspace/mali-userspace_t76x.bb
@@ -0,0 +1,18 @@
+require mali-userspace.inc
+
+TYPE = "midgard"
+SW_VER = "r13p0"
+HW_VER = "r0p0"
+
+LIB_PATH = "arm-linux-gnueabihf"
+
+MALI_X11 = "libmali-${TYPE}-${SW_VER}-${HW_VER}.so"
+MALI_WAYLAND = "libmali-${TYPE}-${SW_VER}-${HW_VER}-wayland.so"
+
+do_install_prepend () {
+	mkdir -p x11
+	cp git/lib/${LIB_PATH}/${MALI_X11} x11/libmali.so
+
+	mkdir -p wayland
+	cp git/lib/${LIB_PATH}/${MALI_WAYLAND}  wayland/libmali.so
+}
diff --git a/recipes-graphics/mesa/mesa_%.bbappend b/recipes-graphics/mesa/mesa_%.bbappend
new file mode 100644
index 0000000..d9cab75
--- /dev/null
+++ b/recipes-graphics/mesa/mesa_%.bbappend
@@ -0,0 +1,9 @@
+PROVIDES_remove = "virtual/libgles1 virtual/libgles2 virtual/egl virtual/libwayland-egl"
+
+do_install_append () {
+    rm -f ${D}/${libdir}/libEGL*
+    rm -f ${D}/${libdir}/libGLESv1_CM.*
+    rm -f ${D}/${libdir}/libGLESv2.*
+    rm -f ${D}/${libdir}/libgbm*
+    rm -f ${D}/${libdir}/libwayland-egl*
+}
-- 
2.7.4

[PATCH 5/7] recipes-bsp: add u-boot-rockchip support

[Jacob Chen]

Rockchip next-dev U-boot is the next generation of rockchip u-boot, will also be an upstream tracking branch.
At present, this branch is just a rebased upstream u-boot.

Signed-off-by: Jacob Chen <jacob-chen@iotwrt.com>
---
 recipes-bsp/u-boot/u-boot-rockchip_next.bb | 17 +++++++++++++++++
 1 file changed, 17 insertions(+)
 create mode 100644 recipes-bsp/u-boot/u-boot-rockchip_next.bb

diff --git a/recipes-bsp/u-boot/u-boot-rockchip_next.bb b/recipes-bsp/u-boot/u-boot-rockchip_next.bb
new file mode 100644
index 0000000..30d16b0
--- /dev/null
+++ b/recipes-bsp/u-boot/u-boot-rockchip_next.bb
@@ -0,0 +1,17 @@
+# Copyright (C) 2017 Fuzhou Rockchip Electronics Co., Ltd
+# Released under the MIT license (see COPYING.MIT for the terms)
+
+require recipes-bsp/u-boot/u-boot.inc
+
+DESCRIPTION = "Rockchip next-dev U-Boot"
+LICENSE = "GPLv2+"
+LIC_FILES_CHKSUM = "file://Licenses/README;md5=a2c678cfd4a4d97135585cad908541c6"
+COMPATIBLE_MACHINE = "(rk3288)"
+
+SRC_URI = "git://github.com/rockchip-linux/u-boot.git;branch=release;"
+SRCREV = "${AUTOREV}"
+
+do_install_prepend () {
+	# copy to default search path
+	cp ${B}/spl/${SPL_BINARY} ${B}/
+}
-- 
2.7.4

[PATCH 6/7] rk3288.inc: add some variables

[Jacob Chen]

change tune to cortexa17hf-neon:
Using the soft floating point abi is incompatible with some binary libaries.

Set preferred mali version to t76x.

Add APPEND which will be used in extlinux.conf.

Add SOC_FAMILY to help add chip specific changes.

Add SPL_BINARY to support build u-boot spl

Signed-off-by: Jacob Chen <jacob-chen@iotwrt.com>
---
 conf/machine/include/rk3288.inc | 10 +++++++++-
 1 file changed, 9 insertions(+), 1 deletion(-)

diff --git a/conf/machine/include/rk3288.inc b/conf/machine/include/rk3288.inc
index e6c19a2..9e7804a 100644
--- a/conf/machine/include/rk3288.inc
+++ b/conf/machine/include/rk3288.inc
@@ -1,10 +1,18 @@
 # Copyright (C) 2015 Romain Perier
 # Released under the MIT license (see COPYING.MIT for the terms)
 
+SOC_FAMILY  = "rk3288"
+
 require conf/machine/include/tune-cortexa17.inc
+require conf/machine/include/soc-family.inc
 
-DEFAULTTUNE="cortexa17-neon"
+DEFAULTTUNE="cortexa17hf-neon"
 PREFERRED_PROVIDER_virtual/kernel = "linux"
 SERIAL_CONSOLES = "115200;ttyS2"
+SPL_BINARY = "u-boot-spl-dtb.bin"
 KERNEL_IMAGETYPE = "zImage"
 KBUILD_DEFCONFIG = "multi_v7_defconfig"
+
+PREFERRED_VERSION_mali-userspace = "t76x"
+
+APPEND = "console=tty1 console=ttyS2,115200n8 rw root=/dev/mmcblk2p7 rootfstype=ext4 init=/sbin/init"
-- 
2.7.4

[PATCH 7/7] rockchip-next-image: introduce image for rockchip next-dev u-boot

[Jacob Chen]

Being different from the previous rk-boot which use parameter, next-dev u-boot use gpt
 partition, so it needs to generate a different image.

Signed-off-by: Jacob Chen <jacob-chen@iotwrt.com>
---
 classes/rockchip-next-image.bbclass | 130 ++++++++++++++++++++++++++++++++++++
 1 file changed, 130 insertions(+)
 create mode 100644 classes/rockchip-next-image.bbclass

diff --git a/classes/rockchip-next-image.bbclass b/classes/rockchip-next-image.bbclass
new file mode 100644
index 0000000..cd87dee
--- /dev/null
+++ b/classes/rockchip-next-image.bbclass
@@ -0,0 +1,130 @@
+# Copyright (C) 2017 Fuzhou Rockchip Electronics Co., Ltd
+# Released under the MIT license (see COPYING.MIT for the terms)
+
+inherit image_types
+
+# Use an uncompressed ext4 by default as rootfs
+IMG_ROOTFS_TYPE = "ext4"
+IMG_ROOTFS = "${IMGDEPLOYDIR}/${IMAGE_NAME}.rootfs.${IMG_ROOTFS_TYPE}"
+
+# This image depends on the rootfs image
+IMAGE_TYPEDEP_rockchip-next-img = "${IMG_ROOTFS_TYPE}"
+
+NEXT_IMG       = "${IMAGE_NAME}.next.img"
+BOOT_IMG       = "boot.img"
+MINILOADER     = "loader.bin"
+UBOOT          = "u-boot.out"
+TRUST          = "trust.out"
+
+# Target image total size [in MiB]
+NEXT_IMG_SIZE ?= "4096"
+
+# default partitions [in Sectors]
+# More info at http://rockchip.wikidot.com/partitions
+LOADER1_SIZE = "8000"
+RESERVED1_SIZE = "128"
+RESERVED2_SIZE = "8192"
+LOADER2_SIZE = "8192"
+ATF_SIZE = "8192"
+BOOT_SIZE = "229376"
+
+IMAGE_DEPENDS_rockchip-next-img = "parted-native \
+	u-boot-mkimage-native \
+	mtools-native \
+	dosfstools-native \
+	virtual/kernel:do_deploy \
+	virtual/bootloader:do_deploy"
+
+PER_CHIP_IMG_GENERATION_COMMAND_rk3288 = "generate_rk3288_image"
+
+IMAGE_CMD_rockchip-next-img () {
+	# Change to image directory
+	cd ${DEPLOY_DIR_IMAGE}
+
+	create_rk_image
+
+	${PER_CHIP_IMG_GENERATION_COMMAND}
+}
+
+create_rk_image () {
+
+	echo "Creating filesystem with total size ${NEXT_IMG_SIZE} MiB"
+
+	# Remove the exist image
+	rm -rf *.next.img
+
+	# Initialize sdcard image file
+	dd if=/dev/zero of=${NEXT_IMG} bs=1M count=0 seek=${NEXT_IMG_SIZE}
+
+	# Create partition table
+	parted -s ${NEXT_IMG} mklabel gpt
+
+	# Create vendor defined partitions
+	LOADER1_START=64
+	RESERVED1_START=`expr ${LOADER1_START}  + ${LOADER1_SIZE}`
+	RESERVED2_START=`expr ${RESERVED1_START}  + ${RESERVED1_SIZE}`
+	LOADER2_START=`expr ${RESERVED2_START}  + ${RESERVED2_SIZE}`
+	ATF_START=`expr ${LOADER2_START}  + ${LOADER2_SIZE}`
+	BOOT_START=`expr ${ATF_START}  + ${ATF_SIZE}`
+	ROOTFS_START=`expr ${BOOT_START}  + ${BOOT_SIZE}`
+
+	parted -s ${NEXT_IMG} unit s mkpart loader1 ${LOADER1_START} `expr ${RESERVED1_START} - 1`
+	parted -s ${NEXT_IMG} unit s mkpart reserved1 ${RESERVED1_START} `expr ${RESERVED2_START} - 1`
+	parted -s ${NEXT_IMG} unit s mkpart reserved2 ${RESERVED2_START} `expr ${LOADER2_START} - 1`
+	parted -s ${NEXT_IMG} unit s mkpart loader2 ${LOADER2_START} `expr ${ATF_START} - 1`
+	parted -s ${NEXT_IMG} unit s mkpart atf ${ATF_START} `expr ${BOOT_START} - 1`
+
+	# Create boot partition and mark it as bootable
+	parted -s ${NEXT_IMG} unit s mkpart boot ${BOOT_START} `expr ${ROOTFS_START} - 1`
+	parted -s ${NEXT_IMG} set 6 boot on
+
+	# Create rootfs partition
+	parted -s ${NEXT_IMG} unit s mkpart root ${ROOTFS_START} 100%
+
+	parted ${NEXT_IMG} print
+
+	# Delete the boot image to avoid trouble with the build cache
+	rm -f ${WORKDIR}/${BOOT_IMG}
+
+	# Create boot partition image
+	BOOT_BLOCKS=$(LC_ALL=C parted -s ${NEXT_IMG} unit b print | awk '/ 6 / { print substr($4, 1, length($4 -1)) / 512 /2 }')
+	BOOT_BLOCKS=`expr $BOOT_BLOCKS / 63 \* 63`
+
+	mkfs.vfat -n "boot" -S 512 -C ${WORKDIR}/${BOOT_IMG} $BOOT_BLOCKS
+	mcopy -i ${WORKDIR}/${BOOT_IMG} -s ${DEPLOY_DIR_IMAGE}/${KERNEL_IMAGETYPE}-${MACHINE}.bin ::${KERNEL_IMAGETYPE}
+
+	DEVICETREE_DEFAULT=""
+	for DTS_FILE in ${KERNEL_DEVICETREE}; do
+		[ -n "${DEVICETREE_DEFAULT}"] && DEVICETREE_DEFAULT="${DTS_FILE}"
+		mcopy -i ${WORKDIR}/${BOOT_IMG} -s ${DEPLOY_DIR_IMAGE}/${KERNEL_IMAGETYPE}-${DTS_FILE} ::${DTS_FILE}
+	done
+
+	# Create extlinux config file
+	cat > ${WORKDIR}/extlinux.conf <<EOF
+default yocto
+
+label yocto
+	kernel /${KERNEL_IMAGETYPE}
+	devicetree /${DEVICETREE_DEFAULT}
+	append ${APPEND}
+EOF
+
+	mmd -i ${WORKDIR}/${BOOT_IMG} ::/extlinux
+	mcopy -i ${WORKDIR}/${BOOT_IMG} -s ${WORKDIR}/extlinux.conf ::/extlinux/
+
+	# Burn Boot Partition
+	dd if=${WORKDIR}/${BOOT_IMG} of=${NEXT_IMG} conv=notrunc,fsync seek=${BOOT_START}
+
+	# Burn Rootfs Partition
+	dd if=${IMG_ROOTFS} of=${NEXT_IMG} seek=${ROOTFS_START}
+
+}
+
+generate_rk3288_image () {
+
+	# Burn bootloader
+	mkimage -n rk3288 -T rksd -d ${DEPLOY_DIR_IMAGE}/${SPL_BINARY} ${WORKDIR}/${UBOOT}
+	cat ${DEPLOY_DIR_IMAGE}/u-boot-${MACHINE}.bin >>  ${WORKDIR}/${UBOOT}
+	dd if=${WORKDIR}/${UBOOT} of=${NEXT_IMG} conv=notrunc,fsync seek=64
+
+}
-- 
2.7.4

Re: [PATCH 0/7] introduce rockchip offical linux support to meta-rockchip

[Jacob Chen]

2017-01-19 18:09 GMT+08:00 Jacob Chen <jacob-chen@iotwrt.com>:
> This series of patches add below features, will add more supports in the future(medias, more chips).
>
> 1. rockchip 4.4 kernel
>
> Rockchip 4.4 kernel is currently the latest version of the rockchip offical kernel, will be an upstream tracking branch.
> We regularly release the kernel through github. It support all rockchip 64-bit chips and a few 32-bit chips.
>
> 2. rockchip next-dev U-boot
>
> Rockchip next-dev U-boot is the next generation of rockchip u-boot, will also be an upstream tracking branch.
> At present, this branch is just a rebased upstream u-boot.
>
> 3. graphics
>
> We have plans for the acceleration in wayland, x11 in the rockchip platform, but in this series of patches, we only include the mali bianry support.
>
> 4. rockchip-next-image
>
> Being different from the previous rk-u-boot which use parameter, next-dev u-boot use gpt partition, so it needs to generate a different image.
>
>
> Jacob Chen (7):
>   recipes-kernel: linux-rockchip: Add new recipe for 4.4
>   machine: Add machine file for the rk3288 linux Boards
>   machine: firefly: use linux-rockchip by default
>   recipes-graphics: Add support for mali-userspace
>   recipes-bsp: add u-boot-rockchip support
>   rk3288.inc: add some variables
>   rockchip-next-image: introduce image for rockchip next-dev u-boot
>
>  classes/rockchip-next-image.bbclass                | 130 +++++++++++++++++++++
>  conf/machine/evb-rk3288.conf                       |  12 ++
>  conf/machine/fennec-rk3288.conf                    |  12 ++
>  conf/machine/firefly-rk3288.conf                   |   4 +
>  conf/machine/include/rk-linux.inc                  |  20 ++++
>  conf/machine/include/rk3288.inc                    |  10 +-
>  conf/machine/tinker-rk3288.conf                    |  13 +++
>  recipes-bsp/u-boot/u-boot-rockchip_next.bb         |  17 +++
>  recipes-graphics/mali-userspace/mali-userspace.inc |  57 +++++++++
>  .../mali-userspace/mali-userspace_t76x.bb          |  18 +++
>  recipes-graphics/mesa/mesa_%.bbappend              |   9 ++
>  recipes-kernel/linux/linux-rockchip_4.4.bb         |  20 ++++
>  12 files changed, 321 insertions(+), 1 deletion(-)
>  create mode 100644 classes/rockchip-next-image.bbclass
>  create mode 100644 conf/machine/evb-rk3288.conf
>  create mode 100644 conf/machine/fennec-rk3288.conf
>  create mode 100644 conf/machine/include/rk-linux.inc
>  create mode 100644 conf/machine/tinker-rk3288.conf
>  create mode 100644 recipes-bsp/u-boot/u-boot-rockchip_next.bb
>  create mode 100644 recipes-graphics/mali-userspace/mali-userspace.inc
>  create mode 100644 recipes-graphics/mali-userspace/mali-userspace_t76x.bb
>  create mode 100644 recipes-graphics/mesa/mesa_%.bbappend
>  create mode 100644 recipes-kernel/linux/linux-rockchip_4.4.bb
>
> --
> 2.7.4
>

Yocto is really amazing.
It truly have a powerful customization architecture.  : )

I'm going to get the gstreamer-rk working with yocto and then plan to
add more chips to it (rk3036,rk3399,rk3328)....

Re: [PATCH 0/7] introduce rockchip offical linux support to meta-rockchip

[Burton, Ross]

[-- Attachment #1: Type: text/plain, Size: 3186 bytes --]

(CCing the layer maintainers as listed in the README to ensure this gets
noticed)



On 19 January 2017 at 10:09, Jacob Chen <jacob-chen@iotwrt.com> wrote:

> This series of patches add below features, will add more supports in the
> future(medias, more chips).
>
> 1. rockchip 4.4 kernel
>
> Rockchip 4.4 kernel is currently the latest version of the rockchip
> offical kernel, will be an upstream tracking branch.
> We regularly release the kernel through github. It support all rockchip
> 64-bit chips and a few 32-bit chips.
>
> 2. rockchip next-dev U-boot
>
> Rockchip next-dev U-boot is the next generation of rockchip u-boot, will
> also be an upstream tracking branch.
> At present, this branch is just a rebased upstream u-boot.
>
> 3. graphics
>
> We have plans for the acceleration in wayland, x11 in the rockchip
> platform, but in this series of patches, we only include the mali bianry
> support.
>
> 4. rockchip-next-image
>
> Being different from the previous rk-u-boot which use parameter, next-dev
> u-boot use gpt partition, so it needs to generate a different image.
>
>
> Jacob Chen (7):
>   recipes-kernel: linux-rockchip: Add new recipe for 4.4
>   machine: Add machine file for the rk3288 linux Boards
>   machine: firefly: use linux-rockchip by default
>   recipes-graphics: Add support for mali-userspace
>   recipes-bsp: add u-boot-rockchip support
>   rk3288.inc: add some variables
>   rockchip-next-image: introduce image for rockchip next-dev u-boot
>
>  classes/rockchip-next-image.bbclass                | 130
> +++++++++++++++++++++
>  conf/machine/evb-rk3288.conf                       |  12 ++
>  conf/machine/fennec-rk3288.conf                    |  12 ++
>  conf/machine/firefly-rk3288.conf                   |   4 +
>  conf/machine/include/rk-linux.inc                  |  20 ++++
>  conf/machine/include/rk3288.inc                    |  10 +-
>  conf/machine/tinker-rk3288.conf                    |  13 +++
>  recipes-bsp/u-boot/u-boot-rockchip_next.bb         |  17 +++
>  recipes-graphics/mali-userspace/mali-userspace.inc |  57 +++++++++
>  .../mali-userspace/mali-userspace_t76x.bb          |  18 +++
>  recipes-graphics/mesa/mesa_%.bbappend              |   9 ++
>  recipes-kernel/linux/linux-rockchip_4.4.bb         |  20 ++++
>  12 files changed, 321 insertions(+), 1 deletion(-)
>  create mode 100644 classes/rockchip-next-image.bbclass
>  create mode 100644 conf/machine/evb-rk3288.conf
>  create mode 100644 conf/machine/fennec-rk3288.conf
>  create mode 100644 conf/machine/include/rk-linux.inc
>  create mode 100644 conf/machine/tinker-rk3288.conf
>  create mode 100644 recipes-bsp/u-boot/u-boot-rockchip_next.bb
>  create mode 100644 recipes-graphics/mali-userspace/mali-userspace.inc
>  create mode 100644 recipes-graphics/mali-userspace/mali-userspace_t76x.bb
>  create mode 100644 recipes-graphics/mesa/mesa_%.bbappend
>  create mode 100644 recipes-kernel/linux/linux-rockchip_4.4.bb
>
> --
> 2.7.4
>
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>

[-- Attachment #2: Type: text/html, Size: 4518 bytes --]

Re: [PATCH 0/7] introduce rockchip offical linux support to meta-rockchip

[=?gb18030?B?SmFjb2IgQ2hlbg==?=]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="gb18030", Size: 3671 bytes --]

Thanks for reminding, I've already added them.
But it seems I forgot to add the prefix "meta-rockchip"





------------------ Original ------------------
From:  "Burton, Ross";<ross.burton@intel.com>;
Date:  Thu, Jan 19, 2017 07:30 PM
To:  "Jacob Chen"<jacob-chen@iotwrt.com>; 
Cc:  "yocto@yoctoproject.org"<yocto@yoctoproject.org>; "eddie.cai"<eddie.cai@rock-chips.com>; "romain.perier"<romain.perier@gmail.com>; "Trevor Woerner"<twoerner@gmail.com>; 
Subject:  Re: [yocto] [PATCH 0/7] introduce rockchip offical linux support to meta-rockchip



(CCing the layer maintainers as listed in the README to ensure this gets noticed)




On 19 January 2017 at 10:09, Jacob Chen <jacob-chen@iotwrt.com> wrote:
This series of patches add below features, will add more supports in the future(medias, more chips).
 
 1. rockchip 4.4 kernel
 
 Rockchip 4.4 kernel is currently the latest version of the rockchip offical kernel, will be an upstream tracking branch.
 We regularly release the kernel through github. It support all rockchip 64-bit chips and a few 32-bit chips.
 
 2. rockchip next-dev U-boot
 
 Rockchip next-dev U-boot is the next generation of rockchip u-boot, will also be an upstream tracking branch.
 At present, this branch is just a rebased upstream u-boot.
 
 3. graphics
 
 We have plans for the acceleration in wayland, x11 in the rockchip platform, but in this series of patches, we only include the mali bianry support.
 
 4. rockchip-next-image
 
 Being different from the previous rk-u-boot which use parameter, next-dev u-boot use gpt partition, so it needs to generate a different image.
 
 
 Jacob Chen (7):
   recipes-kernel: linux-rockchip: Add new recipe for 4.4
   machine: Add machine file for the rk3288 linux Boards
   machine: firefly: use linux-rockchip by default
   recipes-graphics: Add support for mali-userspace
   recipes-bsp: add u-boot-rockchip support
   rk3288.inc: add some variables
   rockchip-next-image: introduce image for rockchip next-dev u-boot
 
  classes/rockchip-next-image.bbclass                | 130 +++++++++++++++++++++
  conf/machine/evb-rk3288.conf                       |  12 ++
  conf/machine/fennec-rk3288.conf                    |  12 ++
  conf/machine/firefly-rk3288.conf                   |   4 +
  conf/machine/include/rk-linux.inc                  |  20 ++++
  conf/machine/include/rk3288.inc                    |  10 +-
  conf/machine/tinker-rk3288.conf                    |  13 +++
  recipes-bsp/u-boot/u-boot-rockchip_next.bb         |  17 +++
  recipes-graphics/mali-userspace/mali-userspace.inc |  57 +++++++++
  .../mali-userspace/mali-userspace_t76x.bb          |  18 +++
  recipes-graphics/mesa/mesa_%.bbappend              |   9 ++
  recipes-kernel/linux/linux-rockchip_4.4.bb         |  20 ++++
  12 files changed, 321 insertions(+), 1 deletion(-)
  create mode 100644 classes/rockchip-next-image.bbclass
  create mode 100644 conf/machine/evb-rk3288.conf
  create mode 100644 conf/machine/fennec-rk3288.conf
  create mode 100644 conf/machine/include/rk-linux.inc
  create mode 100644 conf/machine/tinker-rk3288.conf
  create mode 100644 recipes-bsp/u-boot/u-boot-rockchip_next.bb
  create mode 100644 recipes-graphics/mali-userspace/mali-userspace.inc
  create mode 100644 recipes-graphics/mali-userspace/mali-userspace_t76x.bb
  create mode 100644 recipes-graphics/mesa/mesa_%.bbappend
  create mode 100644 recipes-kernel/linux/linux-rockchip_4.4.bb
 
 --
 2.7.4
 
 --
 _______________________________________________
 yocto mailing list
 yocto@yoctoproject.org
 https://lists.yoctoproject.org/listinfo/yocto

[-- Attachment #2: Type: text/html, Size: 4871 bytes --]

Re: [PATCH 0/7] introduce rockchip offical linux support to meta-rockchip

[Gary Thomas]

On 2017-01-19 12:30, Burton, Ross wrote:
> (CCing the layer maintainers as listed in the README to ensure this gets noticed)
>

Shouldn't this have [meta-rockchip] (or some such) in the subject? - it's certainly
not OE-core or even Poky AFAICT

>
> On 19 January 2017 at 10:09, Jacob Chen <jacob-chen@iotwrt.com <mailto:jacob-chen@iotwrt.com>> wrote:
>
>     This series of patches add below features, will add more supports in the future(medias, more chips).
>
>     1. rockchip 4.4 kernel
>
>     Rockchip 4.4 kernel is currently the latest version of the rockchip offical kernel, will be an upstream tracking branch.
>     We regularly release the kernel through github. It support all rockchip 64-bit chips and a few 32-bit chips.
>
>     2. rockchip next-dev U-boot
>
>     Rockchip next-dev U-boot is the next generation of rockchip u-boot, will also be an upstream tracking branch.
>     At present, this branch is just a rebased upstream u-boot.
>
>     3. graphics
>
>     We have plans for the acceleration in wayland, x11 in the rockchip platform, but in this series of patches, we only
>     include the mali bianry support.
>
>     4. rockchip-next-image
>
>     Being different from the previous rk-u-boot which use parameter, next-dev u-boot use gpt partition, so it needs to
>     generate a different image.
>
>
>     Jacob Chen (7):
>       recipes-kernel: linux-rockchip: Add new recipe for 4.4
>       machine: Add machine file for the rk3288 linux Boards
>       machine: firefly: use linux-rockchip by default
>       recipes-graphics: Add support for mali-userspace
>       recipes-bsp: add u-boot-rockchip support
>       rk3288.inc: add some variables
>       rockchip-next-image: introduce image for rockchip next-dev u-boot
>
>      classes/rockchip-next-image.bbclass                | 130 +++++++++++++++++++++
>      conf/machine/evb-rk3288.conf                       |  12 ++
>      conf/machine/fennec-rk3288.conf                    |  12 ++
>      conf/machine/firefly-rk3288.conf                   |   4 +
>      conf/machine/include/rk-linux.inc                  |  20 ++++
>      conf/machine/include/rk3288.inc                    |  10 +-
>      conf/machine/tinker-rk3288.conf                    |  13 +++
>      recipes-bsp/u-boot/u-boot-rockchip_next.bb <http://u-boot-rockchip_next.bb>         |  17 +++
>      recipes-graphics/mali-userspace/mali-userspace.inc |  57 +++++++++
>      .../mali-userspace/mali-userspace_t76x.bb <http://mali-userspace_t76x.bb>          |  18 +++
>      recipes-graphics/mesa/mesa_%.bbappend              |   9 ++
>      recipes-kernel/linux/linux-rockchip_4.4.bb <http://linux-rockchip_4.4.bb>         |  20 ++++
>      12 files changed, 321 insertions(+), 1 deletion(-)
>      create mode 100644 classes/rockchip-next-image.bbclass
>      create mode 100644 conf/machine/evb-rk3288.conf
>      create mode 100644 conf/machine/fennec-rk3288.conf
>      create mode 100644 conf/machine/include/rk-linux.inc
>      create mode 100644 conf/machine/tinker-rk3288.conf
>      create mode 100644 recipes-bsp/u-boot/u-boot-rockchip_next.bb <http://u-boot-rockchip_next.bb>
>      create mode 100644 recipes-graphics/mali-userspace/mali-userspace.inc
>      create mode 100644 recipes-graphics/mali-userspace/mali-userspace_t76x.bb <http://mali-userspace_t76x.bb>
>      create mode 100644 recipes-graphics/mesa/mesa_%.bbappend
>      create mode 100644 recipes-kernel/linux/linux-rockchip_4.4.bb <http://linux-rockchip_4.4.bb>

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

Re: [PATCH 1/7] recipes-kernel: linux-rockchip: Add new recipe for 4.4

[Bruce Ashfield]

[-- Attachment #1: Type: text/plain, Size: 2246 bytes --]

On Thu, Jan 19, 2017 at 5:09 AM, Jacob Chen <jacob-chen@iotwrt.com> wrote:

> Rockchip 4.4 kernel is currently the latest version of the rockchip
> offical kernel,
> will be an upstream tracking branch.
> We regularly release the kernel through github.
> It support all rockchip 64-bit chips and a few 32-bit chips.
>

If I missed a 0/N explaining this series, sorry about my comments/questions!

These packages belong in a BSP layer, not in the core meta data itself. A
quick check of
the layer index shows one hit for rockchip already:

https://layers.openembedded.org/layerindex/branch/master/machines/?q=rockchip

So that layer may be a good place for these recipes, or a completely  new
layer that you
could create on github (or wherever you prefer).

Bruce


>
> Signed-off-by: Jacob Chen <jacob-chen@iotwrt.com>
> ---
>  recipes-kernel/linux/linux-rockchip_4.4.bb | 20 ++++++++++++++++++++
>  1 file changed, 20 insertions(+)
>  create mode 100644 recipes-kernel/linux/linux-rockchip_4.4.bb
>
> diff --git a/recipes-kernel/linux/linux-rockchip_4.4.bb
> b/recipes-kernel/linux/linux-rockchip_4.4.bb
> new file mode 100644
> index 0000000..ca3674e
> --- /dev/null
> +++ b/recipes-kernel/linux/linux-rockchip_4.4.bb
> @@ -0,0 +1,20 @@
> +# Copyright (C) 2017 Fuzhou Rockchip Electronics Co., Ltd
> +# Released under the MIT license (see COPYING.MIT for the terms)
> +
> +require recipes-kernel/linux/linux-yocto.inc
> +
> +SRC_URI = "git://github.com/rockchip-linux/kernel.git;branch=release-4.4
> ;"
> +
> +SRCREV = "${AUTOREV}"
> +LINUX_VERSION = "4.4.41"
> +# Override local version in order to use the one generated by linux build
> system
> +# And not "yocto-standard"
> +LINUX_VERSION_EXTENSION = ""
> +PR = "r1"
> +PV = "${LINUX_VERSION}"
> +
> +# Include only supported boards for now
> +COMPATIBLE_MACHINE = "(rk3288)"
> +deltask kernel_configme
> +
> +KBUILD_DEFCONFIG = "rockchip_linux_defconfig"
> --
> 2.7.4
>
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>



-- 
"Thou shalt not follow the NULL pointer, for chaos and madness await thee
at its end"

[-- Attachment #2: Type: text/html, Size: 3916 bytes --]

Re: [PATCH 0/7] introduce rockchip offical linux support to meta-rockchip

[Bruce Ashfield]

[-- Attachment #1: Type: text/plain, Size: 3375 bytes --]

On Thu, Jan 19, 2017 at 5:09 AM, Jacob Chen <jacob-chen@iotwrt.com> wrote:

> This series of patches add below features, will add more supports in the
> future(medias, more chips).
>
> 1. rockchip 4.4 kernel
>
> Rockchip 4.4 kernel is currently the latest version of the rockchip
> offical kernel, will be an upstream tracking branch.
> We regularly release the kernel through github. It support all rockchip
> 64-bit chips and a few 32-bit chips.
>
>
Aha. Here was the 0/N that I was missing when I wrote my first reply. See
my comments in
reply to the kernel recipe as to where this should land.

Cheers,

Bruce


> 2. rockchip next-dev U-boot
>
> Rockchip next-dev U-boot is the next generation of rockchip u-boot, will
> also be an upstream tracking branch.
> At present, this branch is just a rebased upstream u-boot.
>
> 3. graphics
>
> We have plans for the acceleration in wayland, x11 in the rockchip
> platform, but in this series of patches, we only include the mali bianry
> support.
>
> 4. rockchip-next-image
>
> Being different from the previous rk-u-boot which use parameter, next-dev
> u-boot use gpt partition, so it needs to generate a different image.
>
>
> Jacob Chen (7):
>   recipes-kernel: linux-rockchip: Add new recipe for 4.4
>   machine: Add machine file for the rk3288 linux Boards
>   machine: firefly: use linux-rockchip by default
>   recipes-graphics: Add support for mali-userspace
>   recipes-bsp: add u-boot-rockchip support
>   rk3288.inc: add some variables
>   rockchip-next-image: introduce image for rockchip next-dev u-boot
>
>  classes/rockchip-next-image.bbclass                | 130
> +++++++++++++++++++++
>  conf/machine/evb-rk3288.conf                       |  12 ++
>  conf/machine/fennec-rk3288.conf                    |  12 ++
>  conf/machine/firefly-rk3288.conf                   |   4 +
>  conf/machine/include/rk-linux.inc                  |  20 ++++
>  conf/machine/include/rk3288.inc                    |  10 +-
>  conf/machine/tinker-rk3288.conf                    |  13 +++
>  recipes-bsp/u-boot/u-boot-rockchip_next.bb         |  17 +++
>  recipes-graphics/mali-userspace/mali-userspace.inc |  57 +++++++++
>  .../mali-userspace/mali-userspace_t76x.bb          |  18 +++
>  recipes-graphics/mesa/mesa_%.bbappend              |   9 ++
>  recipes-kernel/linux/linux-rockchip_4.4.bb         |  20 ++++
>  12 files changed, 321 insertions(+), 1 deletion(-)
>  create mode 100644 classes/rockchip-next-image.bbclass
>  create mode 100644 conf/machine/evb-rk3288.conf
>  create mode 100644 conf/machine/fennec-rk3288.conf
>  create mode 100644 conf/machine/include/rk-linux.inc
>  create mode 100644 conf/machine/tinker-rk3288.conf
>  create mode 100644 recipes-bsp/u-boot/u-boot-rockchip_next.bb
>  create mode 100644 recipes-graphics/mali-userspace/mali-userspace.inc
>  create mode 100644 recipes-graphics/mali-userspace/mali-userspace_t76x.bb
>  create mode 100644 recipes-graphics/mesa/mesa_%.bbappend
>  create mode 100644 recipes-kernel/linux/linux-rockchip_4.4.bb
>
> --
> 2.7.4
>
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>



-- 
"Thou shalt not follow the NULL pointer, for chaos and madness await thee
at its end"

[-- Attachment #2: Type: text/html, Size: 4974 bytes --]

Re: [PATCH 0/7] introduce rockchip offical linux support to meta-rockchip

[Jacob Chen]

Sorry for sending without prefix, and make you guys confused.
This series patches is sending for meta-rockchip, not core meta data.

I will resend it and add prefix.

2017-01-19 20:49 GMT+08:00 Gary Thomas <gary@mlbassoc.com>:
> On 2017-01-19 12:30, Burton, Ross wrote:
>>
>> (CCing the layer maintainers as listed in the README to ensure this gets
>> noticed)
>>
>
> Shouldn't this have [meta-rockchip] (or some such) in the subject? - it's
> certainly
> not OE-core or even Poky AFAICT
>
>>
>> On 19 January 2017 at 10:09, Jacob Chen <jacob-chen@iotwrt.com
>> <mailto:jacob-chen@iotwrt.com>> wrote:
>>
>>     This series of patches add below features, will add more supports in
>> the future(medias, more chips).
>>
>>     1. rockchip 4.4 kernel
>>
>>     Rockchip 4.4 kernel is currently the latest version of the rockchip
>> offical kernel, will be an upstream tracking branch.
>>     We regularly release the kernel through github. It support all
>> rockchip 64-bit chips and a few 32-bit chips.
>>
>>     2. rockchip next-dev U-boot
>>
>>     Rockchip next-dev U-boot is the next generation of rockchip u-boot,
>> will also be an upstream tracking branch.
>>     At present, this branch is just a rebased upstream u-boot.
>>
>>     3. graphics
>>
>>     We have plans for the acceleration in wayland, x11 in the rockchip
>> platform, but in this series of patches, we only
>>     include the mali bianry support.
>>
>>     4. rockchip-next-image
>>
>>     Being different from the previous rk-u-boot which use parameter,
>> next-dev u-boot use gpt partition, so it needs to
>>     generate a different image.
>>
>>
>>     Jacob Chen (7):
>>       recipes-kernel: linux-rockchip: Add new recipe for 4.4
>>       machine: Add machine file for the rk3288 linux Boards
>>       machine: firefly: use linux-rockchip by default
>>       recipes-graphics: Add support for mali-userspace
>>       recipes-bsp: add u-boot-rockchip support
>>       rk3288.inc: add some variables
>>       rockchip-next-image: introduce image for rockchip next-dev u-boot
>>
>>      classes/rockchip-next-image.bbclass                | 130
>> +++++++++++++++++++++
>>      conf/machine/evb-rk3288.conf                       |  12 ++
>>      conf/machine/fennec-rk3288.conf                    |  12 ++
>>      conf/machine/firefly-rk3288.conf                   |   4 +
>>      conf/machine/include/rk-linux.inc                  |  20 ++++
>>      conf/machine/include/rk3288.inc                    |  10 +-
>>      conf/machine/tinker-rk3288.conf                    |  13 +++
>>      recipes-bsp/u-boot/u-boot-rockchip_next.bb
>> <http://u-boot-rockchip_next.bb>         |  17 +++
>>      recipes-graphics/mali-userspace/mali-userspace.inc |  57 +++++++++
>>      .../mali-userspace/mali-userspace_t76x.bb
>> <http://mali-userspace_t76x.bb>          |  18 +++
>>      recipes-graphics/mesa/mesa_%.bbappend              |   9 ++
>>      recipes-kernel/linux/linux-rockchip_4.4.bb
>> <http://linux-rockchip_4.4.bb>         |  20 ++++
>>      12 files changed, 321 insertions(+), 1 deletion(-)
>>      create mode 100644 classes/rockchip-next-image.bbclass
>>      create mode 100644 conf/machine/evb-rk3288.conf
>>      create mode 100644 conf/machine/fennec-rk3288.conf
>>      create mode 100644 conf/machine/include/rk-linux.inc
>>      create mode 100644 conf/machine/tinker-rk3288.conf
>>      create mode 100644 recipes-bsp/u-boot/u-boot-rockchip_next.bb
>> <http://u-boot-rockchip_next.bb>
>>      create mode 100644 recipes-graphics/mali-userspace/mali-userspace.inc
>>      create mode 100644
>> recipes-graphics/mali-userspace/mali-userspace_t76x.bb
>> <http://mali-userspace_t76x.bb>
>>      create mode 100644 recipes-graphics/mesa/mesa_%.bbappend
>>      create mode 100644 recipes-kernel/linux/linux-rockchip_4.4.bb
>> <http://linux-rockchip_4.4.bb>
>
>
> --
> ------------------------------------------------------------
> Gary Thomas                 |  Consulting for the
> MLB Associates              |    Embedded world
> ------------------------------------------------------------
>
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

Re: [PATCH 0/7] introduce rockchip offical linux support to meta-rockchip

[Jacob Chen]

Sorry for bothring : ).....

2017-01-19 21:55 GMT+08:00 Jacob Chen <jacobchen110@gmail.com>:
> Sorry for sending without prefix, and make you guys confused.
> This series patches is sending for meta-rockchip, not core meta data.
>
> I will resend it and add prefix.
>
> 2017-01-19 20:49 GMT+08:00 Gary Thomas <gary@mlbassoc.com>:
>> On 2017-01-19 12:30, Burton, Ross wrote:
>>>
>>> (CCing the layer maintainers as listed in the README to ensure this gets
>>> noticed)
>>>
>>
>> Shouldn't this have [meta-rockchip] (or some such) in the subject? - it's
>> certainly
>> not OE-core or even Poky AFAICT
>>
>>>
>>> On 19 January 2017 at 10:09, Jacob Chen <jacob-chen@iotwrt.com
>>> <mailto:jacob-chen@iotwrt.com>> wrote:
>>>
>>>     This series of patches add below features, will add more supports in
>>> the future(medias, more chips).
>>>
>>>     1. rockchip 4.4 kernel
>>>
>>>     Rockchip 4.4 kernel is currently the latest version of the rockchip
>>> offical kernel, will be an upstream tracking branch.
>>>     We regularly release the kernel through github. It support all
>>> rockchip 64-bit chips and a few 32-bit chips.
>>>
>>>     2. rockchip next-dev U-boot
>>>
>>>     Rockchip next-dev U-boot is the next generation of rockchip u-boot,
>>> will also be an upstream tracking branch.
>>>     At present, this branch is just a rebased upstream u-boot.
>>>
>>>     3. graphics
>>>
>>>     We have plans for the acceleration in wayland, x11 in the rockchip
>>> platform, but in this series of patches, we only
>>>     include the mali bianry support.
>>>
>>>     4. rockchip-next-image
>>>
>>>     Being different from the previous rk-u-boot which use parameter,
>>> next-dev u-boot use gpt partition, so it needs to
>>>     generate a different image.
>>>
>>>
>>>     Jacob Chen (7):
>>>       recipes-kernel: linux-rockchip: Add new recipe for 4.4
>>>       machine: Add machine file for the rk3288 linux Boards
>>>       machine: firefly: use linux-rockchip by default
>>>       recipes-graphics: Add support for mali-userspace
>>>       recipes-bsp: add u-boot-rockchip support
>>>       rk3288.inc: add some variables
>>>       rockchip-next-image: introduce image for rockchip next-dev u-boot
>>>
>>>      classes/rockchip-next-image.bbclass                | 130
>>> +++++++++++++++++++++
>>>      conf/machine/evb-rk3288.conf                       |  12 ++
>>>      conf/machine/fennec-rk3288.conf                    |  12 ++
>>>      conf/machine/firefly-rk3288.conf                   |   4 +
>>>      conf/machine/include/rk-linux.inc                  |  20 ++++
>>>      conf/machine/include/rk3288.inc                    |  10 +-
>>>      conf/machine/tinker-rk3288.conf                    |  13 +++
>>>      recipes-bsp/u-boot/u-boot-rockchip_next.bb
>>> <http://u-boot-rockchip_next.bb>         |  17 +++
>>>      recipes-graphics/mali-userspace/mali-userspace.inc |  57 +++++++++
>>>      .../mali-userspace/mali-userspace_t76x.bb
>>> <http://mali-userspace_t76x.bb>          |  18 +++
>>>      recipes-graphics/mesa/mesa_%.bbappend              |   9 ++
>>>      recipes-kernel/linux/linux-rockchip_4.4.bb
>>> <http://linux-rockchip_4.4.bb>         |  20 ++++
>>>      12 files changed, 321 insertions(+), 1 deletion(-)
>>>      create mode 100644 classes/rockchip-next-image.bbclass
>>>      create mode 100644 conf/machine/evb-rk3288.conf
>>>      create mode 100644 conf/machine/fennec-rk3288.conf
>>>      create mode 100644 conf/machine/include/rk-linux.inc
>>>      create mode 100644 conf/machine/tinker-rk3288.conf
>>>      create mode 100644 recipes-bsp/u-boot/u-boot-rockchip_next.bb
>>> <http://u-boot-rockchip_next.bb>
>>>      create mode 100644 recipes-graphics/mali-userspace/mali-userspace.inc
>>>      create mode 100644
>>> recipes-graphics/mali-userspace/mali-userspace_t76x.bb
>>> <http://mali-userspace_t76x.bb>
>>>      create mode 100644 recipes-graphics/mesa/mesa_%.bbappend
>>>      create mode 100644 recipes-kernel/linux/linux-rockchip_4.4.bb
>>> <http://linux-rockchip_4.4.bb>
>>
>>
>> --
>> ------------------------------------------------------------
>> Gary Thomas                 |  Consulting for the
>> MLB Associates              |    Embedded world
>> ------------------------------------------------------------
>>
>> --
>> _______________________________________________
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto

Re: [PATCH 3/7] machine: firefly: use linux-rockchip by default

[Eddie Cai]

Hi

2017-01-19 18:09 GMT+08:00 Jacob Chen <jacob-chen@iotwrt.com>:
> This is the kernel vendor that supports all hw components for this board,
> so we use it by default.
The title and commit message didn't match the your content. Linux
rockchip should refer to http://github.com/linux-rockchip.
firefly-rk3288.conf already using http://github.com/linux-rockchip
>
> Signed-off-by: Jacob Chen <jacob-chen@iotwrt.com>
> ---
>  conf/machine/firefly-rk3288.conf | 4 ++++
>  1 file changed, 4 insertions(+)
>
> diff --git a/conf/machine/firefly-rk3288.conf b/conf/machine/firefly-rk3288.conf
> index 8fa005d..47e63e1 100644
> --- a/conf/machine/firefly-rk3288.conf
> +++ b/conf/machine/firefly-rk3288.conf
> @@ -7,4 +7,8 @@
>  #http://www.t-firefly.com/en/
>
>  include conf/machine/include/rk3288.inc
> +include conf/machine/include/rk-linux.inc
> +
>  KERNEL_DEVICETREE = "rk3288-firefly.dtb"
> +
> +UBOOT_MACHINE = "firefly-rk3288_defconfig"
> --
> 2.7.4
>
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

Re: [PATCH 0/7] introduce rockchip offical linux support to meta-rockchip

[Leon Woestenberg]

[-- Attachment #1: Type: text/plain, Size: 1068 bytes --]

Hi Jacob,

On Thu, Jan 19, 2017 at 11:09 AM, Jacob Chen <jacob-chen@iotwrt.com> wrote:

> This series of patches add below features, will add more supports in the
> future(medias, more chips).
> 1
> Rockchip 4.4 kernel is currently the latest version of the rockchip
> offical kernel, will be an upstream tracking branch.
> We regularly release the kernel through github. It support all rockchip
> 64-bit chips and a few 32-bit chips.
>
> The topic mentions "official kernel" and you mention "we".

Does this mean this is a rock-chips driven effort?

Good to see such (vendor) support, welcome aboard, but please understand
the "layers" system of Yocto, like the others already pointed out in this
email thread.

- Basically you create a (BSP) layer, that sits on top of Yocto /
OpenEmbedded core.
- Also, it is good practice to also support the same GIT branch names for
the different Yocto releases (such as krogoth, morty) such that users can
easily match the correct branches so that everything just builds correctly.

Regards,

Leon.

[-- Attachment #2: Type: text/html, Size: 1548 bytes --]

Re: [PATCH 0/7] introduce rockchip offical linux support to meta-rockchip

[Trevor Woerner]

Hi Jacob,

Sorry for the delay, I hadn't noticed the patches initially because
the tag was missing, then I was busy with other things. I'm taking a
look at them now.

On Thu, Jan 19, 2017 at 10:17 AM, Leon Woestenberg <leon@sidebranch.com> wrote:
> Hi Jacob,
>
> On Thu, Jan 19, 2017 at 11:09 AM, Jacob Chen <jacob-chen@iotwrt.com> wrote:
>>
>> This series of patches add below features, will add more supports in the
>> future(medias, more chips).
>> 1
>> Rockchip 4.4 kernel is currently the latest version of the rockchip
>> offical kernel, will be an upstream tracking branch.
>> We regularly release the kernel through github. It support all rockchip
>> 64-bit chips and a few 32-bit chips.
>>
> The topic mentions "official kernel" and you mention "we".
>
> Does this mean this is a rock-chips driven effort?
>
> Good to see such (vendor) support, welcome aboard, but please understand the
> "layers" system of Yocto, like the others already pointed out in this email
> thread.
>
> - Basically you create a (BSP) layer, that sits on top of Yocto /
> OpenEmbedded core.
> - Also, it is good practice to also support the same GIT branch names for
> the different Yocto releases (such as krogoth, morty) such that users can
> easily match the correct branches so that everything just builds correctly.
>
> Regards,
>
> Leon.
>
>
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>

Re: [PATCH 5/7] recipes-bsp: add u-boot-rockchip support

[Romain Perier]

[-- Attachment #1: Type: text/plain, Size: 2086 bytes --]

Hi all,


2017-01-19 11:09 GMT+01:00 Jacob Chen <jacob-chen@iotwrt.com>:

> Rockchip next-dev U-boot is the next generation of rockchip u-boot, will
> also be an upstream tracking branch.
> At present, this branch is just a rebased upstream u-boot.
>
> Signed-off-by: Jacob Chen <jacob-chen@iotwrt.com>
> ---
>  recipes-bsp/u-boot/u-boot-rockchip_next.bb | 17 +++++++++++++++++
>  1 file changed, 17 insertions(+)
>  create mode 100644 recipes-bsp/u-boot/u-boot-rockchip_next.bb
>
> diff --git a/recipes-bsp/u-boot/u-boot-rockchip_next.bb
> b/recipes-bsp/u-boot/u-boot-rockchip_next.bb
> new file mode 100644
> index 0000000..30d16b0
> --- /dev/null
> +++ b/recipes-bsp/u-boot/u-boot-rockchip_next.bb
> @@ -0,0 +1,17 @@
> +# Copyright (C) 2017 Fuzhou Rockchip Electronics Co., Ltd
> +# Released under the MIT license (see COPYING.MIT for the terms)
> +
> +require recipes-bsp/u-boot/u-boot.inc
> +
> +DESCRIPTION = "Rockchip next-dev U-Boot"
> +LICENSE = "GPLv2+"
> +LIC_FILES_CHKSUM = "file://Licenses/README;md5=
> a2c678cfd4a4d97135585cad908541c6"
> +COMPATIBLE_MACHINE = "(rk3288)"
>


So... in this case why not simply use u-boot mainline ? Most of
rk3288-based boards are very well supported with
http://git.denx.de/?p=u-boot/u-boot-rockchip.git ..
Do you need something specific that it is not supported yet by u-boot
mainline ?

My philosophy is simple:  When the SoC and the board is correctly supported
by a project on upstream, we use the mainline version of this project (ex:
the linux kernel, u-boot, etc). When that's not the case, we can write a
specific recipe for a vendor version. This is the case for example for the
kernel vendor "linux-rockchip" (
https://git.yoctoproject.org/cgit/cgit.cgi/meta-rockchip/tree/recipes-kernel/linux/linux-rockchip_3.0.bb?id=0f7f53c00e7787d5e4843752721a1690169f4ffd),
that's basically the kernel vendor 3.0.36 for the radxa rock here because
that's the kernel which supports the most features and I/O (compared to the
mainline kernel for this SoC or this board).


Thanks,
Romain

[-- Attachment #2: Type: text/html, Size: 3313 bytes --]

Re: [PATCH 1/7] recipes-kernel: linux-rockchip: Add new recipe for 4.4

[Romain Perier]

[-- Attachment #1: Type: text/plain, Size: 1954 bytes --]

Hi all,


supposing that this patch series is for meta-rockchip (next time add a
prefix meta-rockchip, as it is explained in the README)

2017-01-19 11:09 GMT+01:00 Jacob Chen <jacob-chen@iotwrt.com>:

> Rockchip 4.4 kernel is currently the latest version of the rockchip
> offical kernel,
> will be an upstream tracking branch.
> We regularly release the kernel through github.
> It support all rockchip 64-bit chips and a few 32-bit chips.
>


Could you be more precise ? if some SoCs are better supported by this
kernel instead the mainline kernel, we can consider to accept this recipe
and use it for a set of boards.



>
> Signed-off-by: Jacob Chen <jacob-chen@iotwrt.com>
> ---
>  recipes-kernel/linux/linux-rockchip_4.4.bb | 20 ++++++++++++++++++++
>  1 file changed, 20 insertions(+)
>  create mode 100644 recipes-kernel/linux/linux-rockchip_4.4.bb
>
> diff --git a/recipes-kernel/linux/linux-rockchip_4.4.bb
> b/recipes-kernel/linux/linux-rockchip_4.4.bb
> new file mode 100644
> index 0000000..ca3674e
> --- /dev/null
> +++ b/recipes-kernel/linux/linux-rockchip_4.4.bb
> @@ -0,0 +1,20 @@
> +# Copyright (C) 2017 Fuzhou Rockchip Electronics Co., Ltd
> +# Released under the MIT license (see COPYING.MIT for the terms)
> +
> +require recipes-kernel/linux/linux-yocto.inc
> +
> +SRC_URI = "git://github.com/rockchip-linux/kernel.git;branch=release-4.4
> ;"
> +
> +SRCREV = "${AUTOREV}"
> +LINUX_VERSION = "4.4.41"
> +# Override local version in order to use the one generated by linux build
> system
> +# And not "yocto-standard"
> +LINUX_VERSION_EXTENSION = ""
> +PR = "r1"
> +PV = "${LINUX_VERSION}"
> +
> +# Include only supported boards for now
> +COMPATIBLE_MACHINE = "(rk3288)"
>
+deltask kernel_configme
>



> +KBUILD_DEFCONFIG = "rockchip_linux_defconfig"
>
>
I think that you can move this to a machine file... (for the board that use
linux-rockchip)

Thanks,
Romain

[-- Attachment #2: Type: text/html, Size: 3508 bytes --]

Re: [PATCH 3/7] machine: firefly: use linux-rockchip by default

[Romain Perier]

[-- Attachment #1: Type: text/plain, Size: 1907 bytes --]

Hi all,

1. Add more details to your commits
2. As I said in a previous patch, I don't like this... rk-linux.inc , the
name of the file is not clear at all... and I don't like its content for
now.
3. There is really a small differences between a kernel mainline and your
kernel rk3288 nowadays... Do you have a working VPU in your kernel ?
perhaps that it might be interesting for this... (if I remember, it's not
supported in upstream)


Thanks,
Romain

2017-01-19 15:40 GMT+01:00 Eddie Cai <eddie.cai.linux@gmail.com>:

> Hi
>
> 2017-01-19 18:09 GMT+08:00 Jacob Chen <jacob-chen@iotwrt.com>:
> > This is the kernel vendor that supports all hw components for this board,
> > so we use it by default.
> The title and commit message didn't match the your content. Linux
> rockchip should refer to http://github.com/linux-rockchip.
> firefly-rk3288.conf already using http://github.com/linux-rockchip
> >
> > Signed-off-by: Jacob Chen <jacob-chen@iotwrt.com>
> > ---
> >  conf/machine/firefly-rk3288.conf | 4 ++++
> >  1 file changed, 4 insertions(+)
> >
> > diff --git a/conf/machine/firefly-rk3288.conf
> b/conf/machine/firefly-rk3288.conf
> > index 8fa005d..47e63e1 100644
> > --- a/conf/machine/firefly-rk3288.conf
> > +++ b/conf/machine/firefly-rk3288.conf
> > @@ -7,4 +7,8 @@
> >  #http://www.t-firefly.com/en/
> >
> >  include conf/machine/include/rk3288.inc
> > +include conf/machine/include/rk-linux.inc
> > +
> >  KERNEL_DEVICETREE = "rk3288-firefly.dtb"
> > +
> > +UBOOT_MACHINE = "firefly-rk3288_defconfig"
> > --
> > 2.7.4
> >
> > --
> > _______________________________________________
> > yocto mailing list
> > yocto@yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/yocto
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>

[-- Attachment #2: Type: text/html, Size: 3276 bytes --]

Re: [PATCH 3/7] machine: firefly: use linux-rockchip by default

[Jacob Chen]

[-- Attachment #1: Type: text/plain, Size: 3228 bytes --]

Hi,


Romain Perier wrote on 2017年01月27日 23:27:
> Hi all,
>
> 1. Add more details to your commits
> 2. As I said in a previous patch, I don't like this... rk-linux.inc , 
> the name of the file is not clear at all... and I don't like its 
> content for now.
> 3. There is really a small differences between a kernel mainline and 
> your kernel rk3288 nowadays... Do you have a working VPU in your 
> kernel ? perhaps that it might be interesting for this... (if I 
> remember, it's not supported in upstream)
>

Yes,  we will push all changes from 4.4 kernel to upstream,  but there 
are many things are not being accepted in upstream ( like VPU, GPU, ISP, 
RGA, special dvfs code, special vop code).

I still hope to use this 4.4 kernel by default because our Linux support 
is mostly about media and graphics which can't work with mainline kernel.

Of course, we also hope to make them work with mainline, just it have 
too much trouble to make upstream accepted them. There is a people who 
makes those drivers buildable out-of-tree  on mainline kernel 
(https://github.com/phhusson/rockchip_forwardports), I think it's a good 
way, maybe we can support it in meta-rockchip.


>
> Thanks,
> Romain
>
> 2017-01-19 15:40 GMT+01:00 Eddie Cai <eddie.cai.linux@gmail.com 
> <mailto:eddie.cai.linux@gmail.com>>:
>
>     Hi
>
>     2017-01-19 18:09 GMT+08:00 Jacob Chen <jacob-chen@iotwrt.com
>     <mailto:jacob-chen@iotwrt.com>>:
>     > This is the kernel vendor that supports all hw components for
>     this board,
>     > so we use it by default.
>     The title and commit message didn't match the your content. Linux
>     rockchip should refer to http://github.com/linux-rockchip
>     <http://github.com/linux-rockchip>.
>     firefly-rk3288.conf already using http://github.com/linux-rockchip
>     <http://github.com/linux-rockchip>
>     >
>     > Signed-off-by: Jacob Chen <jacob-chen@iotwrt.com
>     <mailto:jacob-chen@iotwrt.com>>
>     > ---
>     >  conf/machine/firefly-rk3288.conf | 4 ++++
>     >  1 file changed, 4 insertions(+)
>     >
>     > diff --git a/conf/machine/firefly-rk3288.conf
>     b/conf/machine/firefly-rk3288.conf
>     > index 8fa005d..47e63e1 100644
>     > --- a/conf/machine/firefly-rk3288.conf
>     > +++ b/conf/machine/firefly-rk3288.conf
>     > @@ -7,4 +7,8 @@
>     >  #http://www.t-firefly.com/en/
>     >
>     >  include conf/machine/include/rk3288.inc
>     > +include conf/machine/include/rk-linux.inc
>     > +
>     >  KERNEL_DEVICETREE = "rk3288-firefly.dtb"
>     > +
>     > +UBOOT_MACHINE = "firefly-rk3288_defconfig"
>     > --
>     > 2.7.4
>     >
>     > --
>     > _______________________________________________
>     > yocto mailing list
>     > yocto@yoctoproject.org <mailto:yocto@yoctoproject.org>
>     > https://lists.yoctoproject.org/listinfo/yocto
>     <https://lists.yoctoproject.org/listinfo/yocto>
>     --
>     _______________________________________________
>     yocto mailing list
>     yocto@yoctoproject.org <mailto:yocto@yoctoproject.org>
>     https://lists.yoctoproject.org/listinfo/yocto
>     <https://lists.yoctoproject.org/listinfo/yocto>
>
>


[-- Attachment #2: Type: text/html, Size: 7138 bytes --]

Re: [PATCH 5/7] recipes-bsp: add u-boot-rockchip support

[Jacob Chen]

[-- Attachment #1: Type: text/plain, Size: 3046 bytes --]

Hi,


Romain Perier wrote on 2017年01月27日 22:48:
> Hi all,
>
>
> 2017-01-19 11:09 GMT+01:00 Jacob Chen <jacob-chen@iotwrt.com 
> <mailto:jacob-chen@iotwrt.com>>:
>
>     Rockchip next-dev U-boot is the next generation of rockchip
>     u-boot, will also be an upstream tracking branch.
>     At present, this branch is just a rebased upstream u-boot.
>
>     Signed-off-by: Jacob Chen <jacob-chen@iotwrt.com
>     <mailto:jacob-chen@iotwrt.com>>
>     ---
>      recipes-bsp/u-boot/u-boot-rockchip_next.bb
>     <http://u-boot-rockchip_next.bb> | 17 +++++++++++++++++
>      1 file changed, 17 insertions(+)
>      create mode 100644 recipes-bsp/u-boot/u-boot-rockchip_next.bb
>     <http://u-boot-rockchip_next.bb>
>
>     diff --git a/recipes-bsp/u-boot/u-boot-rockchip_next.bb
>     <http://u-boot-rockchip_next.bb>
>     b/recipes-bsp/u-boot/u-boot-rockchip_next.bb
>     <http://u-boot-rockchip_next.bb>
>     new file mode 100644
>     index 0000000..30d16b0
>     --- /dev/null
>     +++ b/recipes-bsp/u-boot/u-boot-rockchip_next.bb
>     <http://u-boot-rockchip_next.bb>
>     @@ -0,0 +1,17 @@
>     +# Copyright (C) 2017 Fuzhou Rockchip Electronics Co., Ltd
>     +# Released under the MIT license (see COPYING.MIT for the terms)
>     +
>     +require recipes-bsp/u-boot/u-boot.inc
>     +
>     +DESCRIPTION = "Rockchip next-dev U-Boot"
>     +LICENSE = "GPLv2+"
>     +LIC_FILES_CHKSUM =
>     "file://Licenses/README;md5=a2c678cfd4a4d97135585cad908541c6"
>     +COMPATIBLE_MACHINE = "(rk3288)"
>
>
>
> So... in this case why not simply use u-boot mainline ? Most of 
> rk3288-based boards are very well supported with 
> http://git.denx.de/?p=u-boot/u-boot-rockchip.git ..
> Do you need something specific that it is not supported yet by u-boot 
> mainline ?
>

In fact, no difference now, I will change SRC_URI  to denx git.

We are still exploring how to deal with the relationship between our lts 
branch and mainline branch.
U-boot community can respond quickly, So unlike kernel, now we don't 
have something specific in this branch.


> My philosophy is simple:  When the SoC and the board is correctly 
> supported by a project on upstream, we use the mainline version of 
> this project (ex: the linux kernel, u-boot, etc). When that's not the 
> case, we can write a specific recipe for a vendor version. This is the 
> case for example for the kernel vendor "linux-rockchip" 
> (https://git.yoctoproject.org/cgit/cgit.cgi/meta-rockchip/tree/recipes-kernel/linux/linux-rockchip_3.0.bb?id=0f7f53c00e7787d5e4843752721a1690169f4ffd), 
> that's basically the kernel vendor 3.0.36 for the radxa rock here 
> because that's the kernel which supports the most features and I/O 
> (compared to the mainline kernel for this SoC or this board).
>

I agree, just I think media and graphics is  very important features, 
especially for Rockchip SOC.
I'd perfer to use version of project that have media and graphics support.

>
> Thanks,
> Romain
>


[-- Attachment #2: Type: text/html, Size: 6767 bytes --]

Re: [PATCH 0/7] introduce rockchip offical linux support to meta-rockchip

[=?gb18030?B?SmFjb2IgQ2hlbg==?=]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="gb18030", Size: 3886 bytes --]

Sorry for sending without prefix, and make you guys confused.
This series patches is sending for meta-rockchip, not core meta data.
I'm new to here,  and I just fllow readme in meta-rockchip  to send patches.


------------------ Original ------------------
From: "Bruce Ashfield";<bruce.ashfield@gmail.com>;
Date: Thu, Jan 19, 2017 09:40 PM
To: "Jacob Chen"<jacob-chen@iotwrt.com>; 
Cc: "Yocto Project Discussion"<yocto@yoctoproject.org>; "eddie.cai"<eddie.cai@rock-chips.com>; 
Subject: Re: [yocto] [PATCH 0/7] introduce rockchip offical linux support to meta-rockchip


On Thu, Jan 19, 2017 at 5:09 AM, Jacob Chen <jacob-chen@iotwrt.com> wrote:
This series of patches add below features, will add more supports in the future(medias, more chips).
 
 1. rockchip 4.4 kernel
 
 Rockchip 4.4 kernel is currently the latest version of the rockchip offical kernel, will be an upstream tracking branch.
 We regularly release the kernel through github. It support all rockchip 64-bit chips and a few 32-bit chips.
 



Aha. Here was the 0/N that I was missing when I wrote my first reply. See my comments in

reply to the kernel recipe as to where this should land.


Cheers,


Bruce


 2. rockchip next-dev U-boot
 
 Rockchip next-dev U-boot is the next generation of rockchip u-boot, will also be an upstream tracking branch.
 At present, this branch is just a rebased upstream u-boot.
 
 3. graphics
 
 We have plans for the acceleration in wayland, x11 in the rockchip platform, but in this series of patches, we only include the mali bianry support.
 
 4. rockchip-next-image
 
 Being different from the previous rk-u-boot which use parameter, next-dev u-boot use gpt partition, so it needs to generate a different image.
 
 
 Jacob Chen (7):
   recipes-kernel: linux-rockchip: Add new recipe for 4.4
   machine: Add machine file for the rk3288 linux Boards
   machine: firefly: use linux-rockchip by default
   recipes-graphics: Add support for mali-userspace
   recipes-bsp: add u-boot-rockchip support
   rk3288.inc: add some variables
   rockchip-next-image: introduce image for rockchip next-dev u-boot
 
  classes/rockchip-next-image.bbclass                | 130 +++++++++++++++++++++
  conf/machine/evb-rk3288.conf                       |  12 ++
  conf/machine/fennec-rk3288.conf                    |  12 ++
  conf/machine/firefly-rk3288.conf                   |   4 +
  conf/machine/include/rk-linux.inc                  |  20 ++++
  conf/machine/include/rk3288.inc                    |  10 +-
  conf/machine/tinker-rk3288.conf                    |  13 +++
  recipes-bsp/u-boot/u-boot-rockchip_next.bb         |  17 +++
  recipes-graphics/mali-userspace/mali-userspace.inc |  57 +++++++++
  .../mali-userspace/mali-userspace_t76x.bb          |  18 +++
  recipes-graphics/mesa/mesa_%.bbappend              |   9 ++
  recipes-kernel/linux/linux-rockchip_4.4.bb         |  20 ++++
  12 files changed, 321 insertions(+), 1 deletion(-)
  create mode 100644 classes/rockchip-next-image.bbclass
  create mode 100644 conf/machine/evb-rk3288.conf
  create mode 100644 conf/machine/fennec-rk3288.conf
  create mode 100644 conf/machine/include/rk-linux.inc
  create mode 100644 conf/machine/tinker-rk3288.conf
  create mode 100644 recipes-bsp/u-boot/u-boot-rockchip_next.bb
  create mode 100644 recipes-graphics/mali-userspace/mali-userspace.inc
  create mode 100644 recipes-graphics/mali-userspace/mali-userspace_t76x.bb
  create mode 100644 recipes-graphics/mesa/mesa_%.bbappend
  create mode 100644 recipes-kernel/linux/linux-rockchip_4.4.bb
 
 --
 2.7.4
 
 --
 _______________________________________________
 yocto mailing list
 yocto@yoctoproject.org
 https://lists.yoctoproject.org/listinfo/yocto
 
-- 

"Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end"

[-- Attachment #2: Type: text/html, Size: 4981 bytes --]