mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 1/2] add 2nd generation default env
Date: Sun, 15 Apr 2012 19:45:38 +0200	[thread overview]
Message-ID: <20120415174538.GO3852@pengutronix.de> (raw)
In-Reply-To: <20120415165709.GQ30672@game.jcrosoft.org>

On Sun, Apr 15, 2012 at 06:57:09PM +0200, Jean-Christophe PLAGNIOL-VILLARD wrote:
> On 18:22 Sun 15 Apr     , Sascha Hauer wrote:
> > The current default environment grows in complexity and still is
> > quite unflexible. The basic mistake we (or better I) made is that
> > we had a boot script and tried to control its behaviour with
> > variables passed to this script. This had the consequence that
> > with every new feature we had to pass another variable to this
> > script and add another if/else to the script. This environment
> > set inverts this behaviour. It introduces a set of helper functions
> > which /env/config can use to do its job.
> > 
> > The helpers are:
> > 
> > /env/bin/ifup
> > 
> > bring up networking. Uses /env/network/$interface to configure the
> > interface. If something has to be done to discover the interface (for
> > USB devices), the code can be put into /env/network/${interface}-discover
> > 
> > /env/bin/bootargs-root-*
> > 
> > Add fields to $bootargs relevant for the kernel to find its rootfs. We
> > currently have helpers for ubi, nfs, initrd and jffs2
> > 
> > /env/bin/bootargs-ip-*
> > 
> > Add fields to $bootargs relevant for the kernel to configure networking.
> > Currently we have helpers for dhcp, static or ip=none
> > 
> > /env/bin/mtdparts-init
> > /env/bin/mtdparts-add
> > 
> > Add barebox partitions to mtd like devices and construct the mtdparts
> > Kernel option.
> > 
> > Additionally the automount feature is used to transparently mount
> > filesystems. With this only the device/file which contains the kernel
> > has to be specified in /env/config.
> 
> can you give us few days to try before apply it

Sure, no problem. In fact I would be glad to get some feedback on this.
Changing the defaultenv can be quite painful later when the board files
are changed.
I am sure though that something like that is needed, the current
defaultenv doesn't bring us much further.

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

  reply	other threads:[~2012-04-15 17:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-15 16:22 [PATCH] generic default environment - 2nd try Sascha Hauer
2012-04-15 16:22 ` [PATCH 1/2] add 2nd generation default env Sascha Hauer
2012-04-15 16:57   ` Jean-Christophe PLAGNIOL-VILLARD
2012-04-15 17:45     ` Sascha Hauer [this message]
2012-04-15 16:22 ` [PATCH 2/2] ARM pcm038: switch to new default environment 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=20120415174538.GO3852@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=plagnioj@jcrosoft.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox