All of lore.kernel.org
 help / color / mirror / Atom feed
From: klaus.goger at theobroma-systems.com <klaus.goger@theobroma-systems.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] rockchip: rk3399: set fdtfile
Date: Mon, 19 Mar 2018 08:17:49 +0100	[thread overview]
Message-ID: <B557583F-A4D2-4534-A05E-40485122A5EC@theobroma-systems.com> (raw)
In-Reply-To: <20180317084825.96189-1-kettenis@openbsd.org>


> On 17.03.2018, at 09:48, Mark Kettenis <kettenis@openbsd.org> wrote:
> 
> Signed-off-by: Mark Kettenis <kettenis@openbsd.org>
> Acked-by: Philipp Tomsich <philipp.tomsich@theobroma-systems.com>
> ---
> include/configs/rk3399_common.h | 1 +
> 1 file changed, 1 insertion(+)
> 
> diff --git a/include/configs/rk3399_common.h b/include/configs/rk3399_common.h
> index d700bf2549..9a5de3a7e3 100644
> --- a/include/configs/rk3399_common.h
> +++ b/include/configs/rk3399_common.h
> @@ -59,6 +59,7 @@
> #include <config_distro_bootcmd.h>
> #define CONFIG_EXTRA_ENV_SETTINGS \
> 	ENV_MEM_LAYOUT_SETTINGS \
> +	"fdtfile=rockchip/" CONFIG_DEFAULT_DEVICE_TREE ".dtb\0" \
> 	"partitions=" PARTS_DEFAULT \
> 	BOOTENV
> 

This assumes that the devicetree files in U-Boot and the OS are the same.
As it’s our goal to keep Linux devicetrees in sync with U-Boot this patch should
be fine in the long-term. But at the moment this only applies for rk3399-firefly (on
Linux).

Mark, where would one find the devicetrees included in OpenBSD?
I looked in sys/arch/amd64 but couldn’t find any.

Anyhow, I’m fine with that change.

Tested-by: Klaus Goger <klaus.goger@theobroma-systems.com>

— 
Klaus

  parent reply	other threads:[~2018-03-19  7:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-17  8:48 [U-Boot] [PATCH] rockchip: rk3399: set fdtfile Mark Kettenis
2018-03-18 16:12 ` [U-Boot] " Philipp Tomsich
2018-03-19  7:17 ` klaus.goger at theobroma-systems.com [this message]
2018-03-19  8:25   ` Jonathan Gray
2018-03-19 11:10   ` Mark Kettenis
2018-03-19  8:36 ` Philipp Tomsich
2018-03-28 21:35 ` Philipp Tomsich

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=B557583F-A4D2-4534-A05E-40485122A5EC@theobroma-systems.com \
    --to=klaus.goger@theobroma-systems.com \
    --cc=u-boot@lists.denx.de \
    /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.