mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Pascal Vizeli <pvizeli@syshack.ch>
Cc: barebox@lists.infradead.org
Subject: Re: Oftree from memory and access to start arguments
Date: Mon, 11 Jun 2018 08:31:52 +0200	[thread overview]
Message-ID: <20180611063152.kior6txkjqi2n5j5@pengutronix.de> (raw)
In-Reply-To: <CACvFaDdHP13W4=GWoSmejJTN5qgwmbWzqhpOiK2S2ss+wVeq7A@mail.gmail.com>

On Fri, Jun 08, 2018 at 01:03:11AM +0200, Pascal Vizeli wrote:
> Hi Sascha,
> 
> I wrote a patch they do that what you have suggest. It write the dtb
> from memory into a file.
> 
> My problem is, I don't know how I can share data between PBL and the
> main process?
> That are not the same binary, so I can't use extern keyword and on
> this early boot step I don't know how I can access to memory.
> I think with a simple pointer, I can't access to a memory area they
> are not my own?

I have a patch in the queue that shall solve this problem, but I never
came to it to make it ready. So far I would recommend some internal SRAM
to store a pointer. Another possibility would be to pass some less
memory to barebox_arm_entry() and pick up the data there. (I would
recommend at least 4k of memory to steal)

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-11  6:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-05 23:07 Pascal Vizeli
2018-06-07  7:31 ` Sascha Hauer
2018-06-07 23:03   ` Pascal Vizeli
2018-06-11  6:31     ` 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=20180611063152.kior6txkjqi2n5j5@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --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