From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from astoria.ccjclearline.com ([64.235.106.9]) by merlin.infradead.org with esmtps (Exim 4.76 #1 (Red Hat Linux)) id 1TenjZ-0000Sc-0Q for barebox@lists.infradead.org; Sat, 01 Dec 2012 14:07:57 +0000 Date: Sat, 1 Dec 2012 09:07:53 -0500 (EST) From: "Robert P. J. Day" In-Reply-To: Message-ID: References: MIME-Version: 1.0 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: barebox-bounces@lists.infradead.org Errors-To: barebox-bounces+u.kleine-koenig=pengutronix.de@lists.infradead.org Subject: Re: how does barebox deal with more than one environment? To: Antony Pavlov Cc: "U-Boot Version 2 (barebox)" On Sat, 1 Dec 2012, Antony Pavlov wrote: > On 1 December 2012 17:19, Robert P. J. Day wrote: > > On Sat, 1 Dec 2012, Robert P. J. Day wrote: > > > >> > >> writing up a simple barebox exercise for students and on this page: > >> > >> http://wiki.barebox.org/doku.php?id=user:first_steps > >> > >> it seems clear(?) that you can define multiple environments that will > >> appear at /dev/env0, /dev/env1, etc, but that page also claims that > >> *only* the configuration on /dev/env0 will be executed automatically > >> if barebox finds that it's a valid configuration sector. > >> > >> so what happens with the additional environments? that page doesn't > >> make it clear. i'm just about to read the source to see if i can > >> figure this out. > > > > oh, wait, i think i see ... the "loadenv" command will load a given > > environment into a directory so i'm *assuming* that additional > > environments are simply available to be loaded, but /dev/env0 is the > > only one treated special. or feel free to correct me if i'm > > hopelessly wrong. > > See common/startup.c:110 > > #ifdef CONFIG_ENV_HANDLING > if (envfs_load(default_environment_path, "/env")) { > #ifdef CONFIG_DEFAULT_ENVIRONMENT > printf("no valid environment found on %s. " > "Using default environment\n", > default_environment_path); > envfs_load("/dev/defaultenv", "/env"); > #endif > > By default default_environment_path="/dev/env0", but it can be > overwritten in a board code (e.g. see arch/arm/boards/panda/board.c). i realize that -- what i was asking about were the possible *additional* environments (/dev/env1, /dev/env2, ...) that are mentioned on that page. rday -- ======================================================================== Robert P. J. Day Ottawa, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday ======================================================================== _______________________________________________ barebox mailing list barebox@lists.infradead.org http://lists.infradead.org/mailman/listinfo/barebox