from:"Jacob Chen"

[yocto] localhost toaster faild after commit 4602408c6

2017-07-28 Thread Jacob Chen

Hi,

I have use a localhost toaster server as the CI server, and recently
it failed to runbuild.

I try to fix it by editing
"bitbake/lib/toaster/bldcontrol/localhostbecontroller.py", but then I
give up, i'm not familiar with it

Can anyone give it a fix?
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] rdepend for a kernel recipe

2017-05-31 Thread Jacob Chen

Hi all,

I have two recipes.

kernel :
https://github.com/rockchip-linux/meta-rockchip/blob/morty/recipes-kernel/linux/linux-mainline_4.11.bb
and kernel module:
https://github.com/rockchip-linux/meta-rockchip/blob/morty/recipes-kernel/linux-extra/rockchip-forwardports_4.11.bb

I want that if I set "PREFERRED_PROVIDER_virtual / kernel" to
"linux-mainline", then  "rockchip-forwardports" will be automatically
installed in my rootfs.

I have set  "RDEPENDS_${PN} += "rockchip-forwardports"" in kernel, but
it didn't work. How can I slove it?

Are there some ways i can do in kernel recipe or image recipe?
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [PATCH 2/3] recipes-multimedia: gstreamer: update to 1.10.4

2017-03-19 Thread Jacob Chen


Hi randy,


ayaka wrote on 2017年03月20日 01:54:

I need a various of features from the new version.

Signed-off-by: Jacob Chen <jacob-c...@iotwrt.com>
Signed-off-by: ayaka <ay...@soulik.info>
---
  recipes-multimedia/gstreamer/gstreamer1.0-plugins-bad_%.bbappend  | 4 
  recipes-multimedia/gstreamer/gstreamer1.0-plugins-base_%.bbappend | 4 
  recipes-multimedia/gstreamer/gstreamer1.0-plugins-good_%.bbappend | 4 
  recipes-multimedia/gstreamer/gstreamer1.0_%.bbappend  | 4 
  4 files changed, 16 insertions(+)
  create mode 100644 
recipes-multimedia/gstreamer/gstreamer1.0-plugins-bad_%.bbappend
  create mode 100644 
recipes-multimedia/gstreamer/gstreamer1.0-plugins-base_%.bbappend
  create mode 100644 
recipes-multimedia/gstreamer/gstreamer1.0-plugins-good_%.bbappend
  create mode 100644 recipes-multimedia/gstreamer/gstreamer1.0_%.bbappend

diff --git a/recipes-multimedia/gstreamer/gstreamer1.0-plugins-bad_%.bbappend 
b/recipes-multimedia/gstreamer/gstreamer1.0-plugins-bad_%.bbappend
new file mode 100644
index 000..5f2255f
--- /dev/null
+++ b/recipes-multimedia/gstreamer/gstreamer1.0-plugins-bad_%.bbappend
@@ -0,0 +1,4 @@
+PV="1.10.4"
+
+SRC_URI[md5sum] = "2757103e57a096a1a05b3ab85b8381af"
+SRC_URI[sha256sum] = 
"23ddae506b3a223b94869a0d3eea3e9a12e847f94d2d0e0b97102ce13ecd6966"
diff --git a/recipes-multimedia/gstreamer/gstreamer1.0-plugins-base_%.bbappend 
b/recipes-multimedia/gstreamer/gstreamer1.0-plugins-base_%.bbappend
new file mode 100644
index 000..0bc9c6e
--- /dev/null
+++ b/recipes-multimedia/gstreamer/gstreamer1.0-plugins-base_%.bbappend
@@ -0,0 +1,4 @@
+PV="1.10.4"
+
+SRC_URI[md5sum] = "f6b46f8fac01eb773d556e3efc369e86"
+SRC_URI[sha256sum] = 
"f6d245b6b3d4cb733f81ebb021074c525ece83db0c10e932794b339b8d935eb7"
diff --git a/recipes-multimedia/gstreamer/gstreamer1.0-plugins-good_%.bbappend 
b/recipes-multimedia/gstreamer/gstreamer1.0-plugins-good_%.bbappend
new file mode 100644
index 000..5176458
--- /dev/null
+++ b/recipes-multimedia/gstreamer/gstreamer1.0-plugins-good_%.bbappend
@@ -0,0 +1,4 @@
+PV="1.10.4"
+
+SRC_URI[md5sum] = "cc0cc13cdb07d4237600b6886b81f31d"
+SRC_URI[sha256sum] = 
"8a86c61434a8c44665365bd0b3557a040937d1f44bf69caee4e9ea816ce74d7e"
diff --git a/recipes-multimedia/gstreamer/gstreamer1.0_%.bbappend 
b/recipes-multimedia/gstreamer/gstreamer1.0_%.bbappend
new file mode 100644
index 000..83c4c1d
--- /dev/null
+++ b/recipes-multimedia/gstreamer/gstreamer1.0_%.bbappend
@@ -0,0 +1,4 @@
+PV="1.10.4"
+
+SRC_URI[md5sum] = "7c91a97e4a2dc81eafd59d0a2f8b0d6e"
+SRC_URI[sha256sum] = 
"50c2f5af50a6cc6c0a3f3ed43bdd8b5e2bff00bacfb766d4be139ec06d8b5218"


We don't need to update gstreamer version in master branch.

It's already 1.10.4.
http://git.yoctoproject.org/cgit.cgi/poky/tree/meta/recipes-multimedia/gstreamer/gstreamer1.0_1.10.4.bb


--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-rockchip][PATCH v2] recipes-graphics: Add recipe for rockchip-mali

2017-03-13 Thread Jacob Chen

* add this recipe to download rockchip mali drivers
* support X11,gbm-only,wayland backend on rk3036,rk3288,rk3399
* provide egl,gles,gbm,opencl library
* depend on mesa to provide dev-package

Signed-off-by: Jacob Chen <jacob-c...@iotwrt.com>
---
 recipes-graphics/libgles/rockchip-mali_git.bb | 89 +++
 1 file changed, 89 insertions(+)
 create mode 100644 recipes-graphics/libgles/rockchip-mali_git.bb

diff --git a/recipes-graphics/libgles/rockchip-mali_git.bb 
b/recipes-graphics/libgles/rockchip-mali_git.bb
new file mode 100644
index 000..02ba5e1
--- /dev/null
+++ b/recipes-graphics/libgles/rockchip-mali_git.bb
@@ -0,0 +1,89 @@
+DESCRIPTION = "GLES libraries for Rockchip SoCs for a family of Mali GPU"
+SECTION = "libs"
+LICENSE = "BINARY"
+LIC_FILES_CHKSUM = "file://LICENSE.TXT;md5=564e729dd65db6f65f911ce0cd340cf9"
+NO_GENERIC_LICENSE[BINARY] = "LICENSE.TXT"
+
+COMPATIBLE_MACHINE = "(rk3036|rk3288|rk3399)"
+
+# There's only hardfp version available
+python __anonymous() {
+tunes = d.getVar("TUNE_FEATURES", True)
+if not tunes:
+return
+if "callconvention-hard" not in tunes:
+pkgn = d.getVar("PN", True)
+pkgv = d.getVar("PV", True)
+raise bb.parse.SkipPackage("%s-%s ONLY supports hardfp mode for now" % 
(pkgn, pkgv))
+}
+
+DEPENDS = "libdrm mesa"
+
+PROVIDES += "virtual/egl virtual/libgles1 virtual/libgles2 virtual/libopencl 
libgbm"
+PROVIDES += "${@bb.utils.contains("DISTRO_FEATURES", "wayland", " 
virtual/libwayland-egl", " ", d)}"
+
+S = "${WORKDIR}/git"
+
+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)}"
+
+MALI_X11_rk3288 = "arm-linux-gnueabihf/libmali-midgard-r9p0-r0p0.so"
+MALI_WAYLAND_rk3288 = 
"arm-linux-gnueabihf/libmali-midgard-r13p0-r0p0-wayland.so "
+MALI_GBM_rk3288 = "arm-linux-gnueabihf/libmali-midgard-r13p0-r0p0-gbm.so "
+
+MALI_X11_rk3036 = "arm-linux-gnueabihf/libmali-utgard-r6p0.so"
+MALI_WAYLAND_rk3036 = "arm-linux-gnueabihf/libmali-utgard-r7p0-wayland.so"
+MALI_GBM_rk3036 = "arm-linux-gnueabihf/libmali-utgard-r7p0-gbm.so"
+
+MALI_X11_rk3399 = "aarch64-linux-gnu/libmali-midgard-4th-r9p0.so"
+MALI_WAYLAND_rk3399 = "aarch64-linux-gnu/libmali-midgard-4th-r9p0-wayland.so"
+MALI_GBM_rk3399 = "aarch64-linux-gnu/libmali-midgard-4th-r9p0-gbm.so"
+
+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}/lib/${MALI_X11} ${D}/${libdir}/libmali.so
+   elif [ "${USE_WL}" = "yes" ]; then
+   install ${S}/lib/${MALI_WAYLAND} ${D}/${libdir}/libmali.so
+   else
+   install ${S}/lib/${MALI_GBM} ${D}/${libdir}/libmali.so
+   fi
+
+   ln -sf libmali.so ${D}/${libdir}/libEGL.so
+   ln -sf libmali.so ${D}/${libdir}/libEGL.so.1
+   ln -sf libmali.so ${D}/${libdir}/libGLESv1_CM.so
+   ln -sf libmali.so ${D}/${libdir}/libGLESv1_CM.so.1
+   ln -sf libmali.so ${D}/${libdir}/libGLESv2.so
+   ln -sf libmali.so ${D}/${libdir}/libGLESv2.so.2
+   ln -sf libmali.so ${D}/${libdir}/libOpenCL.so
+   ln -sf libmali.so ${D}/${libdir}/libOpenCL.so.1
+   ln -sf libmali.so ${D}/${libdir}/libgbm.so
+   ln -sf libmali.so ${D}/${libdir}/libgbm.so.1
+
+   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"
+RCONFLICTS_${PN} = "libegl libgles1 libglesv1-cm1 libgles2 libglesv2-2 libgbm"
+RPROVIDES_${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"
-- 
2.7.4

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-rockchip][PATCH v2] recipes-graphics: mali-userspace: add

2017-03-06 Thread Jacob Chen

Do some modifying according to meta-sunxi

* add COMPATIBLE_MACHINE statement
* detect hard-float
* combine to one bb file

The difference is it depend on mesa to provide dev-package rather than offer it
by itself, which can save some time to solve the compile errors.

Change-Id: If81c363d4cfb11ade08b6c7cfcbfbe56e9d8824b
---
 .../mali-userspace/mali-userspace_git.bb   | 83 ++
 1 file changed, 83 insertions(+)
 create mode 100644 recipes-graphics/mali-userspace/mali-userspace_git.bb

diff --git a/recipes-graphics/mali-userspace/mali-userspace_git.bb 
b/recipes-graphics/mali-userspace/mali-userspace_git.bb
new file mode 100644
index 000..787f79d
--- /dev/null
+++ b/recipes-graphics/mali-userspace/mali-userspace_git.bb
@@ -0,0 +1,83 @@
+SUMMARY = "Userspace mali driver"
+DESCRIPTION = "Userspace mali driver"
+LICENSE = "CLOSED"
+SECTION = "libs"
+
+COMPATIBLE_MACHINE = "(rk3036|rk3288|rk3399)"
+
+# There's only hardfp version available
+python __anonymous() {
+tunes = d.getVar("TUNE_FEATURES", True)
+if not tunes:
+return
+if "callconvention-hard" not in tunes:
+pkgn = d.getVar("PN", True)
+pkgv = d.getVar("PV", True)
+raise bb.parse.SkipPackage("%s-%s ONLY supports hardfp mode for now" % 
(pkgn, pkgv))
+}
+
+DEPENDS = "libdrm mesa"
+
+PROVIDES += "virtual/egl virtual/libgles1 virtual/libgles2 virtual/libopencl 
libgbm"
+PROVIDES += "${@bb.utils.contains("DISTRO_FEATURES", "wayland", " 
virtual/libwayland-egl", " ", d)}"
+
+S = "${WORKDIR}/git"
+
+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)}"
+
+MALI_X11_rk3288 = "arm-linux-gnueabihf/libmali-midgard-r13p0-r0p0.so"
+MALI_WAYLAND_rk3288 = 
"arm-linux-gnueabihf/libmali-midgard-r13p0-r0p0-wayland.so "
+MALI_GBM_rk3288 = "arm-linux-gnueabihf/libmali-midgard-r13p0-r0p0-gbm.so "
+
+MALI_X11_rk3036 = "arm-linux-gnueabihf/libmali-utgard-r6p0.so"
+
+MALI_X11_rk3399 = "aarch64-linux-gnu/libmali-midgard-4th-r9p0.so"
+
+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}/lib/${MALI_X11} ${D}/${libdir}/libmali.so
+   elif [ "${USE_WL}" = "yes" ]; then
+   install ${S}/lib/${MALI_WAYLAND} ${D}/${libdir}/libmali.so
+   else
+   install ${S}/lib/${MALI_GBM} ${D}/${libdir}/libmali.so
+   fi
+
+   ln -sf libmali.so ${D}/${libdir}/libEGL.so
+   ln -sf libmali.so ${D}/${libdir}/libEGL.so.1
+   ln -sf libmali.so ${D}/${libdir}/libGLESv1_CM.so
+   ln -sf libmali.so ${D}/${libdir}/libGLESv1_CM.so.1
+   ln -sf libmali.so ${D}/${libdir}/libGLESv2.so
+   ln -sf libmali.so ${D}/${libdir}/libGLESv2.so.2
+   ln -sf libmali.so ${D}/${libdir}/libOpenCL.so
+   ln -sf libmali.so ${D}/${libdir}/libOpenCL.so.1
+   ln -sf libmali.so ${D}/${libdir}/libgbm.so
+   ln -sf libmali.so ${D}/${libdir}/libgbm.so.1
+
+   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"
+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"
-- 
2.7.4

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-rockchip][PATCH 2/2] recipes-graphics: Add recipe for libdrm-rk

2017-03-01 Thread Jacob Chen

It's rockchip modified libdrm, we can call rga by this libdrm.

Our development work in libdrm has not yet completed, so it have not pushed to 
the upstream.
We temporarily maintain it by ourself.
---
 recipes-graphics/libdrm/libdrm_rk.bb | 47 
 1 file changed, 47 insertions(+)
 create mode 100644 recipes-graphics/libdrm/libdrm_rk.bb

diff --git a/recipes-graphics/libdrm/libdrm_rk.bb 
b/recipes-graphics/libdrm/libdrm_rk.bb
new file mode 100644
index 000..6af5b6f
--- /dev/null
+++ b/recipes-graphics/libdrm/libdrm_rk.bb
@@ -0,0 +1,47 @@
+# Copyright (C) 2017 Fuzhou Rockchip Electronics Co., Ltd
+# Released under the MIT license (see COPYING.MIT for the terms)
+
+SECTION = "x11/base"
+LICENSE = "MIT"
+LIC_FILES_CHKSUM = 
"file://${COREBASE}/meta/COPYING.MIT;md5=3da9cfbcb788c80a0384361b4de20420"
+PROVIDES = "drm"
+DEPENDS = "libpthread-stubs udev libpciaccess"
+
+SRCREV = "${AUTOREV}"
+SRCBRANCH ?= "rockchip-2.4.74"
+SRC_URI = 
"git://github.com/rockchip-linux/libdrm-rockchip.git;branch=${SRCBRANCH}"
+
+S = "${WORKDIR}/git"
+
+inherit autotools pkgconfig
+
+EXTRA_OECONF += "--disable-cairo-tests \
+ --enable-omap-experimental-api \
+ --enable-install-test-programs \
+ --disable-manpages \
+ --disable-valgrind \
+--enable-rockchip-experimental-api \
+"
+
+ALLOW_EMPTY_${PN}-drivers = "1"
+PACKAGES =+ "${PN}-tests ${PN}-drivers ${PN}-radeon ${PN}-nouveau ${PN}-omap \
+ ${PN}-intel ${PN}-exynos ${PN}-kms ${PN}-freedreno ${PN}-amdgpu \
+${PN}-rockchip "
+
+RRECOMMENDS_${PN}-drivers = "${PN}-radeon ${PN}-nouveau ${PN}-omap ${PN}-intel 
\
+ ${PN}-exynos ${PN}-freedreno ${PN}-amdgpu 
${PN}-rockchip"
+
+FILES_${PN}-tests = "${bindir}/*"
+FILES_${PN}-radeon = "${libdir}/libdrm_radeon.so.*"
+FILES_${PN}-nouveau = "${libdir}/libdrm_nouveau.so.*"
+FILES_${PN}-omap = "${libdir}/libdrm_omap.so.*"
+FILES_${PN}-intel = "${libdir}/libdrm_intel.so.*"
+FILES_${PN}-exynos = "${libdir}/libdrm_exynos.so.*"
+FILES_${PN}-kms = "${libdir}/libkms*.so.*"
+FILES_${PN}-freedreno = "${libdir}/libdrm_freedreno.so.*"
+FILES_${PN}-amdgpu = "${libdir}/libdrm_amdgpu.so.*"
+FILES_${PN}-rockchip = "${libdir}/libdrm_rockchip.so.*"
+
+do_configure_prepend() {
+   ${S}/autogen.sh ${CONFIGUREOPTS} ${EXTRA_OECONF}
+}
-- 
2.7.4

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-rockchip][PATCH 1/2] udev-extraconf: add rockchip specific rules

2017-03-01 Thread Jacob Chen

This rules file help to set suitable mode for device node.

vpu-service, vpu_service, rkvdec, hevc-service are different ip.
mali0 is mali-midgard and mali is mali-utgard.

Signed-off-by: Jacob Chen <jacob-c...@iotwrt.com>
---
 recipes-core/udev/udev-extraconf/10-rk.rules |  6 ++
 recipes-core/udev/udev-extraconf_%.bbappend  | 13 +
 2 files changed, 19 insertions(+)
 create mode 100644 recipes-core/udev/udev-extraconf/10-rk.rules
 create mode 100644 recipes-core/udev/udev-extraconf_%.bbappend

diff --git a/recipes-core/udev/udev-extraconf/10-rk.rules 
b/recipes-core/udev/udev-extraconf/10-rk.rules
new file mode 100644
index 000..2308c9a
--- /dev/null
+++ b/recipes-core/udev/udev-extraconf/10-rk.rules
@@ -0,0 +1,6 @@
+KERNEL=="hevc-service", MODE="0666", GROUP="video"
+KERNEL=="rkvdec", MODE="0666", GROUP="video"
+KERNEL=="mali0", MODE="0666", GROUP="video"
+KERNEL=="mali", MODE="0666", GROUP="video"
+KERNEL=="vpu-service", MODE="0666", GROUP="video"
+KERNEL=="vpu_service", MODE="0666", GROUP="video"
diff --git a/recipes-core/udev/udev-extraconf_%.bbappend 
b/recipes-core/udev/udev-extraconf_%.bbappend
new file mode 100644
index 000..4691a31
--- /dev/null
+++ b/recipes-core/udev/udev-extraconf_%.bbappend
@@ -0,0 +1,13 @@
+# extra configuration udev rules
+FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
+
+SRC_URI_append = " \
+file://10-rk.rules \
+"
+
+do_install_prepend () {
+   install -d ${D}${sysconfdir}/udev/rules.d
+   install -m 0644 ${WORKDIR}/*.rules ${D}${sysconfdir}/udev/rules.d
+}
+
+PACKAGE_ARCH = "${MACHINE_ARCH}"
-- 
2.7.4

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [PATCH] recipes-graphics: Add recipe for libdrm-rk

2017-03-01 Thread Jacob Chen

oh， i forget to add meta-rockchip too.

2017-03-01 18:30 GMT+08:00 Jacob Chen <jacob-c...@iotwrt.com>:
> It's rockchip modified libdrm, we can call rga by this libdrm.
>
> Our development work in libdrm has not yet completed, so it have not pushed 
> to the upstream.
> We temporarily maintain it by ourself.
> ---
>  recipes-graphics/libdrm/libdrm_rk.bb | 47 
> 
>  1 file changed, 47 insertions(+)
>  create mode 100644 recipes-graphics/libdrm/libdrm_rk.bb
>
> diff --git a/recipes-graphics/libdrm/libdrm_rk.bb 
> b/recipes-graphics/libdrm/libdrm_rk.bb
> new file mode 100644
> index 000..6af5b6f
> --- /dev/null
> +++ b/recipes-graphics/libdrm/libdrm_rk.bb
> @@ -0,0 +1,47 @@
> +# Copyright (C) 2017 Fuzhou Rockchip Electronics Co., Ltd
> +# Released under the MIT license (see COPYING.MIT for the terms)
> +
> +SECTION = "x11/base"
> +LICENSE = "MIT"
> +LIC_FILES_CHKSUM = 
> "file://${COREBASE}/meta/COPYING.MIT;md5=3da9cfbcb788c80a0384361b4de20420"
> +PROVIDES = "drm"
> +DEPENDS = "libpthread-stubs udev libpciaccess"
> +
> +SRCREV = "${AUTOREV}"
> +SRCBRANCH ?= "rockchip-2.4.74"
> +SRC_URI = 
> "git://github.com/rockchip-linux/libdrm-rockchip.git;branch=${SRCBRANCH}"
> +
> +S = "${WORKDIR}/git"
> +
> +inherit autotools pkgconfig
> +
> +EXTRA_OECONF += "--disable-cairo-tests \
> + --enable-omap-experimental-api \
> + --enable-install-test-programs \
> + --disable-manpages \
> + --disable-valgrind \
> +--enable-rockchip-experimental-api \
> +"
> +
> +ALLOW_EMPTY_${PN}-drivers = "1"
> +PACKAGES =+ "${PN}-tests ${PN}-drivers ${PN}-radeon ${PN}-nouveau ${PN}-omap 
> \
> + ${PN}-intel ${PN}-exynos ${PN}-kms ${PN}-freedreno ${PN}-amdgpu 
> \
> +${PN}-rockchip "
> +
> +RRECOMMENDS_${PN}-drivers = "${PN}-radeon ${PN}-nouveau ${PN}-omap 
> ${PN}-intel \
> + ${PN}-exynos ${PN}-freedreno ${PN}-amdgpu 
> ${PN}-rockchip"
> +
> +FILES_${PN}-tests = "${bindir}/*"
> +FILES_${PN}-radeon = "${libdir}/libdrm_radeon.so.*"
> +FILES_${PN}-nouveau = "${libdir}/libdrm_nouveau.so.*"
> +FILES_${PN}-omap = "${libdir}/libdrm_omap.so.*"
> +FILES_${PN}-intel = "${libdir}/libdrm_intel.so.*"
> +FILES_${PN}-exynos = "${libdir}/libdrm_exynos.so.*"
> +FILES_${PN}-kms = "${libdir}/libkms*.so.*"
> +FILES_${PN}-freedreno = "${libdir}/libdrm_freedreno.so.*"
> +FILES_${PN}-amdgpu = "${libdir}/libdrm_amdgpu.so.*"
> +FILES_${PN}-rockchip = "${libdir}/libdrm_rockchip.so.*"
> +
> +do_configure_prepend() {
> +   ${S}/autogen.sh ${CONFIGUREOPTS} ${EXTRA_OECONF}
> +}
> --
> 2.7.4
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [PATCH] udev-extraconf: add rockchip specific rules

2017-03-01 Thread Jacob Chen

oh， i forget to add meta-rockchip too.

2017-03-01 18:23 GMT+08:00 Jacob Chen <jacob-c...@iotwrt.com>:
> This rules file help to set suitable mode for device node.
>
> vpu-service, vpu_service, rkvdec, hevc-service are different ip.
> mali0 is mali-midgard and mali is mali-utgard.
>
> Signed-off-by: Jacob Chen <jacob-c...@iotwrt.com>
> ---
>  recipes-core/udev/udev-extraconf/10-rk.rules |  6 ++
>  recipes-core/udev/udev-extraconf_%.bbappend  | 13 +
>  2 files changed, 19 insertions(+)
>  create mode 100644 recipes-core/udev/udev-extraconf/10-rk.rules
>  create mode 100644 recipes-core/udev/udev-extraconf_%.bbappend
>
> diff --git a/recipes-core/udev/udev-extraconf/10-rk.rules 
> b/recipes-core/udev/udev-extraconf/10-rk.rules
> new file mode 100644
> index 000..2308c9a
> --- /dev/null
> +++ b/recipes-core/udev/udev-extraconf/10-rk.rules
> @@ -0,0 +1,6 @@
> +KERNEL=="hevc-service", MODE="0666", GROUP="video"
> +KERNEL=="rkvdec", MODE="0666", GROUP="video"
> +KERNEL=="mali0", MODE="0666", GROUP="video"
> +KERNEL=="mali", MODE="0666", GROUP="video"
> +KERNEL=="vpu-service", MODE="0666", GROUP="video"
> +KERNEL=="vpu_service", MODE="0666", GROUP="video"
> diff --git a/recipes-core/udev/udev-extraconf_%.bbappend 
> b/recipes-core/udev/udev-extraconf_%.bbappend
> new file mode 100644
> index 000..4691a31
> --- /dev/null
> +++ b/recipes-core/udev/udev-extraconf_%.bbappend
> @@ -0,0 +1,13 @@
> +# extra configuration udev rules
> +FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
> +
> +SRC_URI_append = " \
> +file://10-rk.rules \
> +"
> +
> +do_install_prepend () {
> +   install -d ${D}${sysconfdir}/udev/rules.d
> +   install -m 0644 ${WORKDIR}/*.rules ${D}${sysconfdir}/udev/rules.d
> +}
> +
> +PACKAGE_ARCH = "${MACHINE_ARCH}"
> --
> 2.7.4
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [PATCH] recipes-graphics: Add recipe for libdrm-rk

2017-03-01 Thread Jacob Chen

It's rockchip modified libdrm, we can call rga by this libdrm.

Our development work in libdrm has not yet completed, so it have not pushed to 
the upstream.
We temporarily maintain it by ourself.
---
 recipes-graphics/libdrm/libdrm_rk.bb | 47 
 1 file changed, 47 insertions(+)
 create mode 100644 recipes-graphics/libdrm/libdrm_rk.bb

diff --git a/recipes-graphics/libdrm/libdrm_rk.bb 
b/recipes-graphics/libdrm/libdrm_rk.bb
new file mode 100644
index 000..6af5b6f
--- /dev/null
+++ b/recipes-graphics/libdrm/libdrm_rk.bb
@@ -0,0 +1,47 @@
+# Copyright (C) 2017 Fuzhou Rockchip Electronics Co., Ltd
+# Released under the MIT license (see COPYING.MIT for the terms)
+
+SECTION = "x11/base"
+LICENSE = "MIT"
+LIC_FILES_CHKSUM = 
"file://${COREBASE}/meta/COPYING.MIT;md5=3da9cfbcb788c80a0384361b4de20420"
+PROVIDES = "drm"
+DEPENDS = "libpthread-stubs udev libpciaccess"
+
+SRCREV = "${AUTOREV}"
+SRCBRANCH ?= "rockchip-2.4.74"
+SRC_URI = 
"git://github.com/rockchip-linux/libdrm-rockchip.git;branch=${SRCBRANCH}"
+
+S = "${WORKDIR}/git"
+
+inherit autotools pkgconfig
+
+EXTRA_OECONF += "--disable-cairo-tests \
+ --enable-omap-experimental-api \
+ --enable-install-test-programs \
+ --disable-manpages \
+ --disable-valgrind \
+--enable-rockchip-experimental-api \
+"
+
+ALLOW_EMPTY_${PN}-drivers = "1"
+PACKAGES =+ "${PN}-tests ${PN}-drivers ${PN}-radeon ${PN}-nouveau ${PN}-omap \
+ ${PN}-intel ${PN}-exynos ${PN}-kms ${PN}-freedreno ${PN}-amdgpu \
+${PN}-rockchip "
+
+RRECOMMENDS_${PN}-drivers = "${PN}-radeon ${PN}-nouveau ${PN}-omap ${PN}-intel 
\
+ ${PN}-exynos ${PN}-freedreno ${PN}-amdgpu 
${PN}-rockchip"
+
+FILES_${PN}-tests = "${bindir}/*"
+FILES_${PN}-radeon = "${libdir}/libdrm_radeon.so.*"
+FILES_${PN}-nouveau = "${libdir}/libdrm_nouveau.so.*"
+FILES_${PN}-omap = "${libdir}/libdrm_omap.so.*"
+FILES_${PN}-intel = "${libdir}/libdrm_intel.so.*"
+FILES_${PN}-exynos = "${libdir}/libdrm_exynos.so.*"
+FILES_${PN}-kms = "${libdir}/libkms*.so.*"
+FILES_${PN}-freedreno = "${libdir}/libdrm_freedreno.so.*"
+FILES_${PN}-amdgpu = "${libdir}/libdrm_amdgpu.so.*"
+FILES_${PN}-rockchip = "${libdir}/libdrm_rockchip.so.*"
+
+do_configure_prepend() {
+   ${S}/autogen.sh ${CONFIGUREOPTS} ${EXTRA_OECONF}
+}
-- 
2.7.4

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [PATCH] udev-extraconf: add rockchip specific rules

2017-03-01 Thread Jacob Chen

This rules file help to set suitable mode for device node.

vpu-service, vpu_service, rkvdec, hevc-service are different ip.
mali0 is mali-midgard and mali is mali-utgard.

Signed-off-by: Jacob Chen <jacob-c...@iotwrt.com>
---
 recipes-core/udev/udev-extraconf/10-rk.rules |  6 ++
 recipes-core/udev/udev-extraconf_%.bbappend  | 13 +
 2 files changed, 19 insertions(+)
 create mode 100644 recipes-core/udev/udev-extraconf/10-rk.rules
 create mode 100644 recipes-core/udev/udev-extraconf_%.bbappend

diff --git a/recipes-core/udev/udev-extraconf/10-rk.rules 
b/recipes-core/udev/udev-extraconf/10-rk.rules
new file mode 100644
index 000..2308c9a
--- /dev/null
+++ b/recipes-core/udev/udev-extraconf/10-rk.rules
@@ -0,0 +1,6 @@
+KERNEL=="hevc-service", MODE="0666", GROUP="video"
+KERNEL=="rkvdec", MODE="0666", GROUP="video"
+KERNEL=="mali0", MODE="0666", GROUP="video"
+KERNEL=="mali", MODE="0666", GROUP="video"
+KERNEL=="vpu-service", MODE="0666", GROUP="video"
+KERNEL=="vpu_service", MODE="0666", GROUP="video"
diff --git a/recipes-core/udev/udev-extraconf_%.bbappend 
b/recipes-core/udev/udev-extraconf_%.bbappend
new file mode 100644
index 000..4691a31
--- /dev/null
+++ b/recipes-core/udev/udev-extraconf_%.bbappend
@@ -0,0 +1,13 @@
+# extra configuration udev rules
+FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
+
+SRC_URI_append = " \
+file://10-rk.rules \
+"
+
+do_install_prepend () {
+   install -d ${D}${sysconfdir}/udev/rules.d
+   install -m 0644 ${WORKDIR}/*.rules ${D}${sysconfdir}/udev/rules.d
+}
+
+PACKAGE_ARCH = "${MACHINE_ARCH}"
-- 
2.7.4

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-rockchip][PATCH v2 2/5] u-boot-rockchip: add

2017-02-19 Thread Jacob Chen

Hi,

2017-02-19 10:43 GMT+08:00 Trevor Woerner <twoer...@gmail.com>:
> This recipe was taken from the Rockchip team's recipe at
> https://github.com/rockchip-linux/meta-rockchip/commit/6a139d5b7510c7ba36aace82c239b894d5741cac
>
> It was mostly written by Jacob Chen <jacob-c...@iotwrt.com> and I've made a
> couple small modifications.
>
> Signed-off-by: Trevor Woerner <twoer...@gmail.com>
> ---
>  recipes-bsp/u-boot/u-boot-rockchip_git.bb | 19 +++
>  1 file changed, 19 insertions(+)
>  create mode 100644 recipes-bsp/u-boot/u-boot-rockchip_git.bb
>
> diff --git a/recipes-bsp/u-boot/u-boot-rockchip_git.bb 
> b/recipes-bsp/u-boot/u-boot-rockchip_git.bb
> new file mode 100644
> index 000..3b4f109
> --- /dev/null
> +++ b/recipes-bsp/u-boot/u-boot-rockchip_git.bb
> @@ -0,0 +1,19 @@
> +# Copyright (C) 2017 Fuzhou Rockchip Electronics Co., Ltd
> +# Copyright (C) 2017 Trevor Woerner <twoer...@gmail.com>
> +# 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 = "(firefly-rk3288)"
> +
> +SRC_URI = "git://github.com/rockchip-linux/u-boot.git;branch=release;"
> +SRCREV = "${AUTOREV}"
> +S = "${WORKDIR}/git"
> +
> +do_deploy_prepend () {
> +   # copy to default search path
> +   cp ${B}/spl/${SPL_BINARY} ${B}/
> +}

I can't pass build if use do_deploy_prepend instead of do_install_prepend.

> --
> 2.12.0.rc1.48.g076c053
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-rockchip][PATCH v2 4/5] classes: rockchip-gpt-img: add

2017-02-19 Thread Jacob Chen


Hi all,


Eddie Cai wrote on 2017年02月19日 14:32:

Hi Trevor

2017-02-19 10:43 GMT+08:00 Trevor Woerner <twoer...@gmail.com 
<mailto:twoer...@gmail.com>>:

> This bbclass was taken from the Rockchip team's work at
> 
https://github.com/rockchip-linux/meta-rockchip/commit/53d2e2e474a3014e3013d0059fd1da773fb0e2b7
> It was mostly written by Jacob Chen <jacob-c...@iotwrt.com 
<mailto:jacob-c...@iotwrt.com>>. I've made some

> small modifications and added it.
>
> Older images used (what Rockchip calls) the "rk-boot" format. Newer 
images use

We call it legacy parameter format
> u-boot and a GPT partitioning scheme. This class allows the build to 
generate
> a gpt-img file that can either be flashed to eMMC or written to an 
SDcard (the

> same image is used for both).
gpt-img is much better than previous one. I like this name.
>
> This is the new image format used for rk3288 SoCs (e.g. the Firefly 
board).

>
> Signed-off-by: Trevor Woerner <twoer...@gmail.com 
<mailto:twoer...@gmail.com>>

> ---
>  classes/rockchip-gpt-img.bbclass | 132 
+++

>  1 file changed, 132 insertions(+)
>  create mode 100644 classes/rockchip-gpt-img.bbclass
>
> diff --git a/classes/rockchip-gpt-img.bbclass 
b/classes/rockchip-gpt-img.bbclass

> new file mode 100644
> index 000..fd80625
> --- /dev/null
> +++ b/classes/rockchip-gpt-img.bbclass
> @@ -0,0 +1,132 @@
> +# Copyright (C) 2017 Fuzhou Rockchip Electronics Co., Ltd
> +# Copyright (C) 2017 Trevor Woerner <twoer...@gmail.com 
<mailto:twoer...@gmail.com>>

> +# 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-gpt-img = "${IMG_ROOTFS_TYPE}"
> +
> +GPTIMG_SUFFIX  = "gpt-img"
> +GPTIMG = "${IMAGE_NAME}.${GPTIMG_SUFFIX}"
> +GPTIMG_SIZE   ?= "4096"
This should be GPT size in sectors which is 64 sectors. The name 
GPTIMG_SIZE is not clear enough. People may think it is whole gpt 
image. What about call it GPT_SIZE?


It's whole gpt image.


> +BOOT_IMG   = "boot.img"
> +MINILOADER = "loader.bin"
> +UBOOT  = "u-boot.out"
> +TRUST  = "trust.out"
> +GPTIMG_APPEND ?= "console=tty1 console=ttyS2,115200n8 rw 
root=/dev/mmcblk2p7 rootfstype=ext4 init=/sbin/init"

> +
> +# 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-gpt-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"
This is not just for rk3288. in fact, it can be used for all the 
Rockchip SoC.


There're many differences between Chips.
Some chips didn't implement SPL support and have to use rk-miniloader to 
create u-boot blob. (e.g. previous rk3399, rk3229)
Some chips didn't use "spl_back_to_brom" so their tpl have a different 
offset.(e.g. previous rk3288)


The name "generate_load1" can't express it clearly.


> +
> +IMAGE_CMD_rockchip-gpt-img () {
> +   # Change to image directory
> +   cd ${DEPLOY_DIR_IMAGE}
> +
> +   # Remove the exist image
> +   rm -rf *${GPTIMG_SUFFIX}
${IMAGE_NAME}  is derived using the IMAGE_BASENAME, MACHINE, and 
DATETIME variables. So we don't need to delete previous one to avoid 
mistake.

> +
> +   create_rk_image
> +
> +   ${PER_CHIP_IMG_GENERATION_COMMAND}
> +
> +   cd ${DEPLOY_DIR_IMAGE}
> +   ln -s ${GPTIMG} "${IMAGE_BASENAME}-${MACHINE}.${GPTIMG_SUFFIX}"
> +}
> +
> +create_rk_image () {
> +
> +   # Initialize sdcard image file
> +   dd if=/dev/zero of=${GPTIMG} bs=1M count=0 seek=${GPTIMG_SIZE}
> +
> +   # Create partition table
> +   parted -s ${GPTIMG} 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}  + ${RES

Re: [yocto] [meta-rockchip][PATCH v2 3/5] machine: firefly-rk3288: specify bootloader

2017-02-19 Thread Jacob Chen

Hi Trevor,

2017-02-19 13:03 GMT+08:00 Eddie Cai <eddie.cai.li...@gmail.com>:
> Hi Trevor
>
> 2017-02-19 10:43 GMT+08:00 Trevor Woerner <twoer...@gmail.com>:
>> Set the default preferred bootloader for firefly-rk3288 to be u-boot-rockchip
>> and set the default name of the SPL binary.
>>
>> Signed-off-by: Trevor Woerner <twoer...@gmail.com>
>> ---
>>  conf/machine/firefly-rk3288.conf | 1 +
>>  conf/machine/include/rk3288.inc  | 3 +++
>>  2 files changed, 4 insertions(+)
> Reviewed-by Eddie Cai <eddie.cai.li...@gmail.com>
>>
>> diff --git a/conf/machine/firefly-rk3288.conf 
>> b/conf/machine/firefly-rk3288.conf
>> index 8fa005d..58d752b 100644
>> --- a/conf/machine/firefly-rk3288.conf
>> +++ b/conf/machine/firefly-rk3288.conf
>> @@ -8,3 +8,4 @@
>>
>>  include conf/machine/include/rk3288.inc
>>  KERNEL_DEVICETREE = "rk3288-firefly.dtb"
>> +UBOOT_MACHINE = "firefly-rk3288_defconfig"
>> diff --git a/conf/machine/include/rk3288.inc 
>> b/conf/machine/include/rk3288.inc
>> index 769e5c1..4a4201f 100644
>> --- a/conf/machine/include/rk3288.inc
>> +++ b/conf/machine/include/rk3288.inc
>> @@ -10,3 +10,6 @@ PREFERRED_PROVIDER_virtual/kernel = "linux"
>>  SERIAL_CONSOLES = "115200;ttyS2"
>>  KERNEL_IMAGETYPE = "zImage"
>>  KBUILD_DEFCONFIG = "multi_v7_defconfig"
>> +
>> +PREFERRED_PROVIDER_virtual/bootloader ?= "u-boot-rockchip"
>> +SPL_BINARY ?= "u-boot-spl-dtb.bin"
>> --
>> 2.12.0.rc1.48.g076c053
>>
>> --
>> ___
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto


It looks good, Reviewed-by: Jacob Chen <jacob-c...@iotwrt.com>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-rockchip][PATCH 2/7] machine: Add machine file for the rk3288 linux Boards

2017-02-18 Thread Jacob Chen

Hi all,

Sorry, I found that rk-linux.inc could be moved to distro conf .

I know why you guys are opposed to it now.

I will remove it from machine conf, but i'm still confused about
whether TUNES is machines specific or distro

specific.

Eddie Cai wrote on 2017年02月09日 16:20:

2017-02-09 14:49 GMT+08:00 Jacob Chen <jacob2.c...@rock-chips.com>:

Trevor Woerner wrote on 2017年01月28日 03:41:

On Fri, Jan 27, 2017 at 9:37 AM, Romain Perier <romain.per...@gmail.com>
wrote:

Could you:
- Make one patch per new machine file and not one patch for all new added
machine

Agreed.

Are all of these machines actual devices? The evb one doesn't sound real.

Are all of these machines released and available for purchase? I've
heard of the tinkerboard (although I can't seem to find one I can
actually buy) but I haven't heard of the fennec.

I think i should only leave tinker board here.
We have a lot of boards which are not open to the public, it's not suitable
to push them to the community.

- Add a clear @DESCRIPTION for each board, see an example here:
https://git.yoctoproject.org/cgit/cgit.cgi/meta-rockchip/tree/conf/machine/firefly-rk3288.conf
- Write a clear and an understandable commit message for your new patches

@Trevor: What do you think about this rk-linux.inc ? I don't like this,
either its name and what it contains.

First off, I think it's really great to see people contributing to
meta-rockchip! :-)

This entire set of patches seems to be adding "official" support for
the rockchip devices; in other words, these recipes will help you to
create builds that use the official rockchip sources. That is great.
But I think a good BSP gives a user all the possibilities but then
leaves the final decision up to them.

: ) That's the reason why we try to push patches to here, we want that
"meta-rockchip" can
build between vendor old kernel/new kernel/old u-boot/new u-boot and
mainline kernel/u-boot
well. Community people might help develop mainline things.

So I agree with Romain, I think the name could use more work. It would
be nice if this set of patches included something in the name that let
the user know these build from official sources. Then the user could
decide whether they want to use the official rockchip sources, or
whether they want to build from upstream. So I'm not opposed to the
idea of adding recipes for official sources, I'd like like to see them
added in a way that leaves the decision with the user.

I added rk-linux.inc because i need a place to set up verndor-BSP default
settings.
I want that the user can choose various combinations by change the include
file in machine file.
e.g:
rk-linux.inc for linux-rockchip 4.4 + u-boot-rockchip-nex-dev
rk-linux.inc + rk-uboot.inc for linux-rockchip + u-boot-rockchip

rk-linux.inc for linux-mainline + u-boot-mainline

BTW, which name you think is better?

What about follow raspberrypi?
├── include
│ ├── rpi-base.inc
│ ├── rpi-default-providers.inc
│ ├── rpi-default-settings.inc
│ ├── rpi-default-versions.inc
│ └── tune-arm1176jzf-s.inc
├── raspberrypi0.conf
├── raspberrypi2.conf
├── raspberrypi3.conf
└── raspberrypi.conf

That's it for now.
Thanks for your patches

+1 :-)

--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

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

2017-02-09 Thread Jacob Chen


Hi,


Romain Perier wrote on 2017年01月27日 22:48:

Hi all,


2017-01-19 11:09 GMT+01:00 Jacob Chen <jacob-c...@iotwrt.com 
<mailto:jacob-c...@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-c...@iotwrt.com
<mailto:jacob-c...@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 000..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



-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

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

2017-02-09 Thread Jacob Chen


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.li...@gmail.com 
<mailto:eddie.cai.li...@gmail.com>>:


Hi

2017-01-19 18:09 GMT+08:00 Jacob Chen <jacob-c...@iotwrt.com
<mailto:jacob-c...@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-c...@iotwrt.com
<mailto:jacob-c...@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>




-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-rockchip][PATCH 2/7] machine: Add machine file for the rk3288 linux Boards

2017-02-09 Thread Jacob Chen

Hi,

Eddie Cai wrote on 2017年02月09日 16:20:

2017-02-09 14:49 GMT+08:00 Jacob Chen <jacob2.c...@rock-chips.com>:

Trevor Woerner wrote on 2017年01月28日 03:41:

On Fri, Jan 27, 2017 at 9:37 AM, Romain Perier <romain.per...@gmail.com>
wrote:

Could you:
- Make one patch per new machine file and not one patch for all new added
machine

Agreed.

Are all of these machines actual devices? The evb one doesn't sound real.

Are all of these machines released and available for purchase? I've
heard of the tinkerboard (although I can't seem to find one I can
actually buy) but I haven't heard of the fennec.

I think i should only leave tinker board here.
We have a lot of boards which are not open to the public, it's not suitable
to push them to the community.

@Trevor: What do you think about this rk-linux.inc ? I don't like this,
either its name and what it contains.

First off, I think it's really great to see people contributing to
meta-rockchip! :-)

rk-linux.inc for linux-mainline + u-boot-mainline

I send the wrong draft due to the poor network... Please ignore the e.g...

What i think it's that the users should always get image with all
features enabled with default settings.
I will be killed if i let them to set each settings one by one in
local.conf to enable features
ok to change name and split file, but i think the things it contianed is
needed.

BTW, which name you think is better?

split rk-linux.inc into
rk-base.inc
rk-vendor-providers.inc
rk-vendor-settings.inc
rk-vendor-versions.inc
rk-community-providers.inc
rk-community-settings.inc
rk-community-versions.inc

Hmmm, it look more clearly than rk-linux.inc.

That's it for now.
Thanks for your patches

+1 :-)

--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-rockchip][PATCH 4/7] recipes-graphics: Add support for mali-userspace

2017-02-08 Thread Jacob Chen


Hi,


Trevor Woerner wrote on 2017年01月28日 09:44:

On Fri, Jan 27, 2017 at 9:41 AM, Romain Perier  wrote:

Hi all,

Correct me if I am wrong, but these are generic mali userpace binaries ?
meta-rockchip is a bsp meta layer, it should only contains files and recipes
to make rockchip board working or things specific to the rockchip board. For
me these recipes are completly generic and might be re-used for another
platform with another SoC.

I don't want this in meta-rockchip. There is no a layer called meta-mali or
something ?

@Trevor: Feel free to comment, the point of view of the second maintainer is
always welcome

:-)


I was just about to point out that there is no meta-mali, and that
most BSP layers do include their own recipes for mali (meta-sunxi,
meta-96boards, meta-xilinx) but, googling around, there is in fact a
meta-mali provided my ARM itself:
https://github.com/ARM-software/meta-mali . So I guess we could go
either way. Although I haven't looked at what's specifically provided
in meta-mali to know if it would be useful or not.



I think GPU is a part of SOC. Other bsp meta layer also contain gpu 
userpace binaries.
And, mali userpace binaries are not very generic, there are different in 
hardware versions, software versions and backends.

e.g:
rk3288's GPU is T76x-r0p0 but rk3288w's GPU is T76x-r1p0, so they 
have to use different binaries.




--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-rockchip][PATCH 2/7] machine: Add machine file for the rk3288 linux Boards

2017-02-08 Thread Jacob Chen

Trevor Woerner wrote on 2017年01月28日 03:41:

On Fri, Jan 27, 2017 at 9:37 AM, Romain Perier wrote:

Could you:
- Make one patch per new machine file and not one patch for all new added
machine

Agreed.

Are all of these machines actual devices? The evb one doesn't sound real.

Are all of these machines released and available for purchase? I've
heard of the tinkerboard (although I can't seem to find one I can
actually buy) but I haven't heard of the fennec.

I think i should only leave tinker board here.
We have a lot of boards which are not open to the public, it's not
suitable to push them to the community.

@Trevor: What do you think about this rk-linux.inc ? I don't like this,
either its name and what it contains.

First off, I think it's really great to see people contributing to
meta-rockchip! :-)

: ) That's the reason why we try to push patches to here, we want that
"meta-rockchip" can
build between vendor old kernel/new kernel/old u-boot/new u-boot and
mainline kernel/u-boot

well. Community people might help develop mainline things.

I added rk-linux.inc because i need a place to set up verndor-BSP
default settings.
I want that the user can choose various combinations by change the
include file in machine file.

e.g:
rk-linux.inc for linux-rockchip 4.4 + u-boot-rockchip-nex-dev
rk-linux.inc + rk-uboot.inc for linux-rockchip + u-boot-rockchip

rk-linux.inc for linux-mainline + u-boot-mainline

BTW, which name you think is better?

That's it for now.
Thanks for your patches

+1 :-)

--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-rockchip][PATCH 2/7] machine: Add machine file for the rk3288 linux Boards

2017-02-06 Thread Jacob Chen


Hi all,

Thanks for reviewing, I will looking at comments and suggestions after 
the other work finished.


: )



在 2017年01月27日 22:37, Romain Perier 写道:

Hey,

Could you:
- Make one patch per new machine file and not one patch for all new 
added machine
- Add a clear @DESCRIPTION for each board, see an example here: 
https://git.yoctoproject.org/cgit/cgit.cgi/meta-rockchip/tree/conf/machine/firefly-rk3288.conf

- Write a clear and an understandable commit message for your new patches

@Trevor: What do you think about this rk-linux.inc ? I don't like 
this, either its name and what it contains.


That's it for now.
Thanks for your patches


2017-01-19 15:04 GMT+01:00 Jacob Chen <jacob-c...@iotwrt.com 
<mailto:jacob-c...@iotwrt.com>>:


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/

<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-c...@rock-chips.com
<mailto:jacob-c...@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 000..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 000..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 000..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 000..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




-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-rockchip][PATCH 2/7] machine: Add machine file for the rk3288 linux Boards

2017-02-03 Thread jacob-chen


Hi all,

Thanks for reviewing, I will looking at comments and suggestions after 
the other work finished.


: )



在 2017年01月27日 22:37, Romain Perier 写道:

Hey,

Could you:
- Make one patch per new machine file and not one patch for all new 
added machine
- Add a clear @DESCRIPTION for each board, see an example here: 
https://git.yoctoproject.org/cgit/cgit.cgi/meta-rockchip/tree/conf/machine/firefly-rk3288.conf

- Write a clear and an understandable commit message for your new patches

@Trevor: What do you think about this rk-linux.inc ? I don't like 
this, either its name and what it contains.


That's it for now.
Thanks for your patches


2017-01-19 15:04 GMT+01:00 Jacob Chen <jacob-c...@iotwrt.com 
<mailto:jacob-c...@iotwrt.com>>:


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/

<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-c...@rock-chips.com
<mailto:jacob-c...@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 000..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 000..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 000..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 000..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




-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

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

2017-01-19 Thread 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'm new to here,  and I just fllow readme in meta-rockchip  to send patches.

-- Original --
From: "Bruce Ashfield";<bruce.ashfi...@gmail.com>;
Date: Thu, Jan 19, 2017 09:40 PM
To: "Jacob Chen"<jacob-c...@iotwrt.com>; 
Cc: "Yocto Project Discussion"<yocto@yoctoproject.org>; 
"eddie.cai"<eddie@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-c...@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"-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

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

2017-01-19 Thread Jacob Chen

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





-- Original --
From:  "Burton, Ross";<ross.bur...@intel.com>;
Date:  Thu, Jan 19, 2017 07:30 PM
To:  "Jacob Chen"<jacob-c...@iotwrt.com>; 
Cc:  "yocto@yoctoproject.org"<yocto@yoctoproject.org>; 
"eddie.cai"<eddie@rock-chips.com>; 
"romain.perier"<romain.per...@gmail.com>; "Trevor Woerner"<twoer...@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-c...@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-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

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

2017-01-19 Thread Jacob Chen

Sorry for bothring : ).

2017-01-19 21:55 GMT+08:00 Jacob Chen <jacobchen...@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 <g...@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-c...@iotwrt.com
>>> <mailto:jacob-c...@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
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

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

2017-01-19 Thread 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-c...@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 000..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 <>  ${WORKDIR}/${UBOOT}
+   dd if=${WORKDIR}/${UBOOT} of=${NEXT_IMG} conv=notrunc,fsync seek=64
+
+}
-- 
2.7.4

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

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

2017-01-19 Thread 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-c...@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 000..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

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-rockchip][PATCH 6/7] rk3288.inc: add some variables

2017-01-19 Thread 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-c...@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

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

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

2017-01-19 Thread Jacob Chen

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

Signed-off-by: Jacob Chen <jacob-c...@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 000..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 000..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 000..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

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

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

2017-01-19 Thread 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-c...@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] [meta-rockchip][PATCH 2/7] machine: Add machine file for the rk3288 linux Boards

2017-01-19 Thread 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-c...@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 000..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 000..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 000..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 000..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

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

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

2017-01-19 Thread 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-c...@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 000..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

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

2017-01-19 Thread 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

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

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

2017-01-19 Thread 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 <g...@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-c...@iotwrt.com
>> <mailto:jacob-c...@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
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

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

2017-01-19 Thread Jacob Chen

2017-01-19 18:09 GMT+08:00 Jacob Chen <jacob-c...@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)
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

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

2017-01-19 Thread 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-c...@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

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

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

2017-01-19 Thread 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-c...@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 000..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

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

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

2017-01-19 Thread Jacob Chen

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

Signed-off-by: Jacob Chen <jacob-c...@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 000..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 000..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 000..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

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

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

2017-01-19 Thread 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-c...@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] [PATCH 2/7] machine: Add machine file for the rk3288 linux Boards

2017-01-19 Thread 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-c...@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 000..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 000..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 000..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 000..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

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

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

2017-01-19 Thread 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-c...@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 000..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

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

2017-01-19 Thread 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

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

42 matches

Mail list logo