From: robert.jarzmik@free.fr
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: Envfs embedded in barebox.bin
Date: Thu, 17 Nov 2011 17:02:22 +0100 (CET) [thread overview]
Message-ID: <18d7a66c-b6d8-4f44-b702-cc292da78f05@zimbra1-e1.priv.proxad.net> (raw)
In-Reply-To: <20111117154923.GJ27267@pengutronix.de>
----- Mail original -----
De: "Sascha Hauer" <s.hauer@pengutronix.de>
> My issue is that while I'm developping my board code, I have no feedback (because no console available).
So you are doing LED debugging? That's brave ;)
That's crazy. It is the method I used to bring this board into the linux kernel, and I still have my good morse over a LED code, with which I debugged early initcalls in the kernel. But that's very very tedious :)
> Most boards have this in the config:
> CONFIG_DEFAULT_ENVIRONMENT=y
> CONFIG_DEFAULT_ENVIRONMENT_GENERIC=y
> CONFIG_DEFAULT_ENVIRONMENT_PATH="defaultenv arch/arm/boards/guf-vincell/env"
> This means that the content of defaultenv/ and arch/arm/boards/guf-vincell/env
> is embedded into the binary (common/Makefile) and gets mounted during
> startup (common/startup.c line 113)
Ah, this is the wheel I was speaking of :)
I had missed the "CONFIG_DEFAULT_ENVIRONMENT_GENERIC" part, and I didn't see anything in the linker (as it actually is in a generated .h file ...).
Great, thanks for the info, I just recompiled, and a hexdump shows my environment within barbox.bin.
Cheers.
--
Robert
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2011-11-17 16:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <15dd21bf-86c1-4ca8-a830-caef28d617ee@zimbra1-e1.priv.proxad.net>
2011-11-17 15:05 ` robert.jarzmik
2011-11-17 15:49 ` Sascha Hauer
2011-11-17 16:02 ` robert.jarzmik [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=18d7a66c-b6d8-4f44-b702-cc292da78f05@zimbra1-e1.priv.proxad.net \
--to=robert.jarzmik@free.fr \
--cc=barebox@lists.infradead.org \
--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