mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Andrey Smirnov <andrew.smirnov@gmail.com>
To: Pascal Vizeli <pvizeli@syshack.ch>
Cc: Barebox List <barebox@lists.infradead.org>
Subject: Re: [PATCH 1/1] command: oftree: support load device tree from memory
Date: Wed, 6 Jun 2018 12:57:28 -0700	[thread overview]
Message-ID: <CAHQ1cqFr4ASW-hD96HOM7WyeRjPCFf5CnXcbBMX1fkQJQTEcUg@mail.gmail.com> (raw)
In-Reply-To: <20180606151602.11094-1-pvizeli@syshack.ch>

On Wed, Jun 6, 2018 at 8:16 AM, Pascal Vizeli <pvizeli@syshack.ch> 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.
>
> For implementation:
>
> Not sure what is the best. Maybe we can create a of_unflatten_file_dtb() and
> of_unflatten_memory_dtb() they return fdt. There are a lot place they load
> a fdt from a file and repeat the same code.
>

IMHO, an ideal solution to this problem would be to either extend
RAMFS or create a separate FS that would allow mounting an arbitrary
blob in RAM as a file with size determined using
file_name_detect_type() + custom code or specified explicitly.

That's quite a bit more work that this patch, though.

Thanks,
Andrey Smirnov

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

  reply	other threads:[~2018-06-06 19:57 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 [this message]
2018-06-07  7:20 ` Sascha Hauer
2018-06-07  8:29   ` Pascal Vizeli
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=CAHQ1cqFr4ASW-hD96HOM7WyeRjPCFf5CnXcbBMX1fkQJQTEcUg@mail.gmail.com \
    --to=andrew.smirnov@gmail.com \
    --cc=barebox@lists.infradead.org \
    --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