From: Sascha Hauer <s.hauer@pengutronix.de>
To: Martin Hofmann <martin.hofmann@mni.thm.de>
Cc: barebox@lists.infradead.org
Subject: Re: No default env without Barebox wanting to load from persistant storage
Date: Mon, 29 Oct 2018 14:53:32 +0100 [thread overview]
Message-ID: <20181029135332.zdljgjg2lkti3nfv@pengutronix.de> (raw)
In-Reply-To: <8b1454dd-7a19-f6c8-d3cd-863372947e4c@mni.thm.de>
Hi Martin,
On Sun, Oct 28, 2018 at 04:24:13PM +0100, Martin Hofmann wrote:
> Hello everyone,
>
> I am currently working on a Barebox port for our own home made architecture
> used for educational purpose.
>
> The port can be found under github.com/mh0fmann/eco32-barebox and starts
> being used.
>
> Our architecture does not have any kind of nand or nor flash that can be
> added used for /dev/env0 to store a environment in it but we still want to
> use a default compile in enivornment.
>
> In oderder to use that one is in the in the need to activate
> CONFIG_ENV_HANDLING which alaways wants to load a environment from
> /dev/env0.
>
> So the question is - is it not possible to just use a compile in default env
> without the need that barebox wants to load another env from somewhere else
> or did i miss something on the way?
Indeed this a usecase I never thought of and is not officially
supported. However, a
default_environment_path_set(NULL);
Should have the desired effect.
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
next prev parent reply other threads:[~2018-10-29 13:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-28 15:24 Martin Hofmann
2018-10-29 13:53 ` Sascha Hauer [this message]
2018-10-30 6:57 ` Martin Hofmann
2018-10-30 7:33 ` Sascha Hauer
2018-10-30 8:50 ` Martin Hofmann
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=20181029135332.zdljgjg2lkti3nfv@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=martin.hofmann@mni.thm.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