mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Pascal Vizeli <pascal.vizeli@syshack.ch>
To: Sascha Hauer <s.hauer@pengutronix.de>
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:29:53 +0200	[thread overview]
Message-ID: <CACvFaDd0CUgO8+ExRriuXd4cSNLhvv5pvE=Ar07LX0ytLJiHTQ@mail.gmail.com> (raw)
In-Reply-To: <20180607072037.3jw4exty4huobpm6@pengutronix.de>

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.

greets
Pascal

2018-06-07 9:20 GMT+02:00 Sascha Hauer <s.hauer@pengutronix.de>:
> On Wed, Jun 06, 2018 at 03:16:02PM +0000, Pascal Vizeli wrote:
>> DON'T MERGE: this is only a concept patch.
>>
>> On some device, barebox is the second bootloader. The first bootloader provide
>> some times allready a better device tree as the linux kernel own.
>> Mostly barebox can't boot from this device tree but the linux kernel can.
>>
>> This patch allow to load a device tree from memory from first bootloader.
>
> Note while it may be handy to have a command for that, you can already
> do this without writing code:
>
> memcpy -d /mydtb <dtbaddress> 0 0x10000
> oftree -l /mydtb
>
> The only drawback is that you have to guess the size of the dtb.
>
> 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:30 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 [this message]
2018-06-07  8:53     ` Sascha Hauer
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='CACvFaDd0CUgO8+ExRriuXd4cSNLhvv5pvE=Ar07LX0ytLJiHTQ@mail.gmail.com' \
    --to=pascal.vizeli@syshack.ch \
    --cc=barebox@lists.infradead.org \
    --cc=pvizeli@syshack.ch \
    --cc=s.hauer@pengutronix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox