All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vagrant Cascadian <vagrant@debian.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v1] rockchip: utilize CONFIG_DEFAULT_FDT_FILE
Date: Fri, 22 Jun 2018 07:23:12 -0700	[thread overview]
Message-ID: <87zhzmoq7j.fsf@aikidev.net> (raw)
In-Reply-To: <8736ycsydo.fsf@aikidev.net>

On 2018-05-27, Vagrant Cascadian wrote:
> On 2018-05-25, Klaus Goger wrote:
>> Currently the fdtfile environment variable is set to
>> CONFIG_DEFAULT_DEVICE_TREE which is Ñ–nternally used as U-Boot devicetree
>> source. The OS can use a different filename and Kconfig gives us the
>> ability to select a default devicetree via CONFIG_DEFAULT_FDT_FILE.
>> This also gives user configuring U-Boot via menuconfig the behaviour
>> someone would expect.
...
> Tested on puma-rk3399.
>
> Tested-By: Vagrant Cascadian <vagrant@debian.org>
>
> Was hoping to also test on firefly-rk3399, but having difficulty getting
> u-boot installed unreleated to this patch.

Finally was able to test on Firefly-RK3399 applied against u-boot
2018.07-rc2, and it also works correctly.

Are there any outstanding concerns with this patch?


live well,
  vagrant
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 832 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20180622/ccf5fc95/attachment.sig>

  parent reply	other threads:[~2018-06-22 14:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-25 21:45 [U-Boot] [PATCH v1] rockchip: utilize CONFIG_DEFAULT_FDT_FILE Klaus Goger
2018-05-27 19:16 ` Vagrant Cascadian
2018-05-27 19:36   ` klaus.goger at theobroma-systems.com
2018-06-22 14:23   ` Vagrant Cascadian [this message]
2018-06-22 14:32     ` klaus.goger at theobroma-systems.com
2018-07-13 10:47 ` [U-Boot] [U-Boot,v1] " 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=87zhzmoq7j.fsf@aikidev.net \
    --to=vagrant@debian.org \
    --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.