Re: No default env without Barebox wanting to load from persistant storage

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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@xxxxxxxxxxxxxxxxxxx
http://lists.infradead.org/mailman/listinfo/barebox



[Index of Archives]     [Linux Embedded]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [XFree86]

  Powered by Linux