All of lore.kernel.org
 help / color / mirror / Atom feed
From: Heinrich Schuchardt <xypron.glpk@gmx.de>
To: Simon Glass <sjg@chromium.org>
Cc: Ilias Apalodimas <ilias.apalodimas@linaro.org>,
	U-Boot Mailing List <u-boot@lists.denx.de>
Subject: Usage of device-tree for blobs
Date: Wed, 25 Aug 2021 10:05:54 +0200	[thread overview]
Message-ID: <ccb85894-359a-d1a0-bb5b-f14dd7956886@gmx.de> (raw)

Hello Simon,

some boards like qemu-riscv64_defconfig do not use any device-tree at
build time. A device-tree is only supplied at runtime by the prior boot
stage (CONFIG_OF_PRIOR_STAGE=y).

In doc/develop/devicetree/intro.rst you suggest to put binary blobs into
the device-tree.

Could you, please, update the documentation to explain how adding blobs
to the device-tree works in the different scenarios depending on the
values of:

CONFIG_OF_EMBED
CONFIG_OF_SEPARATE
CONFIG_OF_BOARD
CONFIG_OF_HOSTFILE
CONFIG_OF_PRIOR_STAGE

It would be especially important to understand how one can develop a
board independent feature which works for all of these settings.

Please, describe CONFIG_OF_PRIOR_STAGE in
doc/develop/devicetree/control.rst.

Best regards

Heinrich

             reply	other threads:[~2021-08-25  8:06 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-25  8:05 Heinrich Schuchardt [this message]
2021-08-26  3:15 ` Usage of device-tree for blobs Simon Glass
2021-08-26  7:05   ` Heinrich Schuchardt
2021-08-26 19:54     ` Simon Glass
2021-08-26 20:18       ` Mark Kettenis
2021-08-27  3:57         ` Simon Glass
2021-08-27 19:52           ` Mark Kettenis
2021-08-28 18:07             ` Simon Glass
2021-08-26 21:05       ` Sean Anderson
2021-08-26 12:55   ` Mark Kettenis
2021-08-26 20:00     ` Simon Glass
2021-08-26 20:27       ` Mark Kettenis
2021-08-27  3:57         ` Simon Glass
2021-08-28  3:24 ` Simon Glass
2021-09-03  8:53 ` Simon Glass

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=ccb85894-359a-d1a0-bb5b-f14dd7956886@gmx.de \
    --to=xypron.glpk@gmx.de \
    --cc=ilias.apalodimas@linaro.org \
    --cc=sjg@chromium.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.