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

[Romain Perier]

Hi all,


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

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


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

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


Thanks,
Romain
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20170127/99e81aa1/attachment.html>