All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Bo Shen <voice.shen@atmel.com>
Cc: barebox@lists.infradead.org
Subject: Re: Passing kernel arguments - SAMA5D4EK
Date: Fri, 6 Feb 2015 08:33:18 +0100	[thread overview]
Message-ID: <20150206073318.GI12209@pengutronix.de> (raw)
In-Reply-To: <54D09205.4070704@atmel.com>

Hi,

On Tue, Feb 03, 2015 at 05:16:53PM +0800, Bo Shen wrote:
> Hi Sascha,
> 
> On 02/03/2015 04:59 PM, Sascha Hauer wrote:
> >Note that we started with trying to build a generic default environment
> >which at some point grew into a monster. We now have the 2nd version of
> >the generic default environment which is much better. Unfortunately
> >usage of this new default environment is board specific and your board
> >isn't converted yet. If you are interested I can show you the steps to
> >convert it.
> 
> I am interested in this, could you show me the steps to convert it?
> Thanks.

Here we go:

- Add "select HAVE_DEFAULT_ENVIRONMENT_NEW" to your board config
- Enable CONFIG_DEFAULT_ENVIRONMENT in the default config
- move everything that should be run during startup to one or multiple
  scripts in /env/init/. For example the at91sam9260ek has some stuff
  depending on $armlinux_architecture, that should be done in an init
  script.
- create /env/boot/* scripts several examples can be found in the tree
- Create /env/nv/* variables for the corresponding global variables that
  you wish to have. do a "find -name nv" to see what I mean.
- /env/config should normally be empty in the board code, then the
  generic one from defaultenv/defaultenv-2-base/config is used
- MTD partitions should for now be defined in /env/init/mtdparts-* or later
  in the device tree.

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

  parent reply	other threads:[~2015-02-06  7:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-02 16:58 Passing kernel arguments - SAMA5D4EK Doug Brainard
2015-02-03  8:59 ` Sascha Hauer
2015-02-03  9:16   ` Bo Shen
2015-02-03 17:21     ` Doug Brainard
2015-02-03 19:33       ` Sascha Hauer
2015-02-03 21:07         ` Doug Brainard
2015-02-05 22:19           ` Doug Brainard
2015-02-06  7:35             ` Sascha Hauer
2015-02-06  7:33     ` Sascha Hauer [this message]
2015-02-07 18:55       ` Doug Brainard
2015-02-09  7:36         ` Sascha Hauer
2015-02-10  5:05           ` Doug Brainard
2015-02-10  9:48             ` Sascha Hauer

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=20150206073318.GI12209@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=voice.shen@atmel.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.