mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Pascal Vizeli <pascal.vizeli@syshack.ch>
Cc: barebox@lists.infradead.org, Pascal Vizeli <pvizeli@syshack.ch>
Subject: Re: [PATCH 1/1] command: oftree: support load device tree from memory
Date: Thu, 7 Jun 2018 10:53:12 +0200	[thread overview]
Message-ID: <20180607085312.xtrjlsmuxfvfv4jj@pengutronix.de> (raw)
In-Reply-To: <CACvFaDd0CUgO8+ExRriuXd4cSNLhvv5pvE=Ar07LX0ytLJiHTQ@mail.gmail.com>

On Thu, Jun 07, 2018 at 10:29:53AM +0200, Pascal Vizeli wrote:
> Thanks for this workaround. I will use this.
> 
> I will later send a patch they store the device tree address on
> raspberry into a variable.
> So that user can load this, if he need it.
> 
> The question is now, would you allow to load a device tree with a
> memory address on oftree utility?
> And if yes, where is the best place to add this function.

Instead of a command I would prefer if you could just store r2 from
the original bootloader you have been started with, and in a board
specific initcall you copy the devicetree you found in memory to a
file. Then the user has access to the devicetree with regular file
commands and there is no need to guess the memory address where the
original bootloader stored the device tree.

Sascha

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2018-06-07  8:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-06 15:16 Pascal Vizeli
2018-06-06 19:57 ` Andrey Smirnov
2018-06-07  7:20 ` Sascha Hauer
2018-06-07  8:29   ` Pascal Vizeli
2018-06-07  8:53     ` Sascha Hauer [this message]
2018-06-07 10:42       ` Pascal Vizeli
2018-06-07 12:45         ` Pascal Vizeli

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=20180607085312.xtrjlsmuxfvfv4jj@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=pascal.vizeli@syshack.ch \
    --cc=pvizeli@syshack.ch \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox