All of lore.kernel.org
 help / color / mirror / Atom feed
From: Trevor Woerner <twoerner@gmail.com>
To: Randy 'ayaka' Li <ayaka@soulik.info>
Cc: yocto@yoctoproject.org
Subject: Re: [PATCH v2 01/10] conf/machine: add support for rk3399
Date: Tue, 23 Apr 2019 13:47:16 -0400	[thread overview]
Message-ID: <20190423174716.GA7171@linux-uys3> (raw)
In-Reply-To: <20190423132514.21996-2-ayaka@soulik.info>

On Tue 2019-04-23 @ 09:25:05 PM, Randy 'ayaka' Li wrote:
> RK3399 is a new generation powerful SoC from Rockchip, which has
> Dual Cortex-A72 + Quad Cortex-A53, 64-bit CPU.
> 
> Signed-off-by: Randy 'ayaka' Li <ayaka@soulik.info>
> ---
>  conf/machine/excavator-rk3399.conf | 12 ++++++++++++
>  conf/machine/firefly-rk3399.conf   | 14 ++++++++++++++
>  conf/machine/include/rk3399.inc    | 17 +++++++++++++++++
>  3 files changed, 43 insertions(+)
>  create mode 100644 conf/machine/excavator-rk3399.conf
>  create mode 100644 conf/machine/firefly-rk3399.conf
>  create mode 100644 conf/machine/include/rk3399.inc
> 
> diff --git a/conf/machine/excavator-rk3399.conf b/conf/machine/excavator-rk3399.conf
> new file mode 100644
> index 0000000..8506a50
> --- /dev/null
> +++ b/conf/machine/excavator-rk3399.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: EXCAVATOR 3399
> +
> +include conf/machine/include/rk3399.inc
> +
> +KERNEL_DEVICETREE = "rockchip/rk3399-sapphire-excavator.dtb"
> +UBOOT_MACHINE = "evb-rk3399_defconfig"
> +
> +GPTIMG_APPEND = "console=ttyS2,1500000n8 rw root=PARTUUID=B921B045-1DF0 rootfstype=ext4 init=/sbin/init"
> diff --git a/conf/machine/firefly-rk3399.conf b/conf/machine/firefly-rk3399.conf
> new file mode 100644
> index 0000000..4e35c3d
> --- /dev/null
> +++ b/conf/machine/firefly-rk3399.conf
> @@ -0,0 +1,14 @@
> +# Copyright (C) 2017 Fuzhou Rockchip Electronics Co., Ltd
> +# Released under the MIT license (see COPYING.MIT for the terms)
> +
> +#@TYPE: Machine
> +#@NAME: Firefly RK3399
> +#@DESCRIPTION: Firefly-RK3399 is a Six-Core 64-bit High-Performance Platform.
> +#http://www.t-firefly.com/en/
> +
> +include conf/machine/include/rk3399.inc
> +
> +KERNEL_DEVICETREE = "rockchip/rk3399-firefly.dtb"
> +UBOOT_MACHINE = "evb-rk3399_defconfig"
> +
> +GPTIMG_APPEND = "console=ttyS2,1500000n8 rw root=PARTUUID=B921B045-1DF0 rootfstype=ext4 init=/sbin/init"
> diff --git a/conf/machine/include/rk3399.inc b/conf/machine/include/rk3399.inc
> new file mode 100644
> index 0000000..9237616
> --- /dev/null
> +++ b/conf/machine/include/rk3399.inc
> @@ -0,0 +1,17 @@
> +# Copyright (C) 2019 SUMOMO Computer Association
> +# Released under the MIT license (see COPYING.MIT for the terms)
> +
> +SOC_FAMILY = "rk3399"
> +
> +require conf/machine/include/tune-cortexa72.inc
> +require conf/machine/include/soc-family.inc
> +require conf/machine/include/rockchip-defaults.inc
> +
> +SERIAL_CONSOLES = "1500000;ttyS2"
> +KERNEL_IMAGETYPE = "Image"
> +KBUILD_DEFCONFIG = "defconfig"
> +
> +PREFERRED_PROVIDER_virtual/bootloader ?= "u-boot-rockchip"

Using u-boot-rockchip causes build failures. In both cases (excavator-rk3399
and firefly-rk3399) I get:

	| #
	| # configuration written to .config
	| #
	| make[1]: Leaving directory '/z/build-master/meta-rockchip/build/tmp-glibc/work/firefly_rk3399-oe-linux/u-boot-rockchip/20171218-r0/build'
	| make: Leaving directory '/z/build-master/meta-rockchip/build/tmp-glibc/work/firefly_rk3399-oe-linux/u-boot-rockchip/20171218-r0/git'
	| /z/build-master/meta-rockchip/build/tmp-glibc/work/firefly_rk3399-oe-linux/u-boot-rockchip/20171218-r0/temp/run.do_configure.27647: line 113: merge_config.sh: command not found
	| WARNING: /z/build-master/meta-rockchip/build/tmp-glibc/work/firefly_rk3399-oe-linux/u-boot-rockchip/20171218-r0/temp/run.do_configure.27647:1 exit 127 from 'merge_config.sh -m .config'
	| ERROR: Function failed: do_configure (log file is located at /z/build-master/meta-rockchip/build/tmp-glibc/work/firefly_rk3399-oe-linux/u-boot-rockchip/20171218-r0/temp/log.do_configure.27647)

Do you have an updated recipe for u-boot-rockchip?

> +
> +IMAGE_FSTYPES = "rockchip-gpt-img"
> +IMAGE_CLASSES = "rockchip-gpt-img"
> -- 
> 2.20.1
> 
> -- 
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto


  reply	other threads:[~2019-04-23 17:47 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-23 13:25 [meta-rockchip] [PATCH v2 00/10] add new SoCs supports Randy 'ayaka' Li
2019-04-23 13:25 ` [PATCH v2 01/10] conf/machine: add support for rk3399 Randy 'ayaka' Li
2019-04-23 17:47   ` Trevor Woerner [this message]
2019-04-24 15:01     ` ayaka
2019-04-23 13:25 ` [PATCH v2 02/10] conf/machine: add support for rk3328 Randy 'ayaka' Li
2019-04-23 13:25 ` [PATCH v2 03/10] conf/machine: add support for rv1108 Randy 'ayaka' Li
2019-04-23 13:25 ` [PATCH v2 04/10] conf/machine: add support for rk3036 Randy 'ayaka' Li
2019-04-23 13:25 ` [PATCH v2 05/10] conf/machine: add support for rk312x Randy 'ayaka' Li
2019-04-23 13:25 ` [PATCH v2 06/10] conf/machine: add support for rk3326 Randy 'ayaka' Li
2019-04-23 13:25 ` [PATCH v2 07/10] conf/machine: add support for rk3368 Randy 'ayaka' Li
2019-04-23 13:25 ` [PATCH v2 08/10] conf/machine: add support for rk3308 Randy 'ayaka' Li
2019-04-23 13:25 ` [PATCH v2 09/10] conf/machine: rk3288: adding some machine files Randy 'ayaka' Li
2019-04-23 13:25 ` [PATCH v2 10/10] conf: use rockchip kernel 4.4 for firefly release Randy 'ayaka' Li

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190423174716.GA7171@linux-uys3 \
    --to=twoerner@gmail.com \
    --cc=ayaka@soulik.info \
    --cc=yocto@yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.