mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Moritz Augsburger <ml+barebox@moritz.augsburger.name>
Cc: Barebox List <barebox@lists.infradead.org>
Subject: Re: Raspberry Pi: Access Firmware-FDT
Date: Wed, 30 Jan 2019 10:25:14 +0100	[thread overview]
Message-ID: <20190130092514.hqmsvvnpvxpnmr3n@pengutronix.de> (raw)
In-Reply-To: <c0358da915d386604bf576935cb49530@moritz.augsburger.name>

Hi Moritz,

On Tue, Jan 29, 2019 at 11:42:13AM +0100, Moritz Augsburger wrote:
> Hi,
> 
> on the RPi, the firmware binary blob assembles and enriches the dtb/dtbo
> files, puts the created fdt into memory, storing the location in r2.
> 
> I found a discussion proposing a patch
> (http://lists.infradead.org/pipermail/barebox/2018-June/033460.html) that
> was never included.

BTW with "See other mail I just sent you" in this thread I meant:
http://lists.infradead.org/pipermail/barebox/2018-June/033469.html

> 
> Is there currently any way to boot the kernel with the firmware created fdt?

No, there's currently no way to do said. We would need a fresh version
of the patch you referenced.

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:[~2019-01-30  9:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-29 10:42 Moritz Augsburger
2019-01-30  9:25 ` Sascha Hauer [this message]

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=20190130092514.hqmsvvnpvxpnmr3n@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=ml+barebox@moritz.augsburger.name \
    /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