mail archive of the barebox mailing list
 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: [PATCH 2/2] Switched SAMA5D4EK development board to the newer environment method.
Date: Wed, 11 Feb 2015 09:35:24 +0100	[thread overview]
Message-ID: <20150211083524.GH12209@pengutronix.de> (raw)
In-Reply-To: <54DB0436.3010004@atmel.com>

On Wed, Feb 11, 2015 at 03:26:46PM +0800, Bo Shen wrote:
> Hi J,
> 
> On 02/11/2015 01:06 PM, Jean-Christophe PLAGNIOL-VILLARD wrote:
> >Hi,
> >
> >	as state before I use the atmel board for bootp everyday as the defaultenv-2 does not support
> >	this Nack until it’s fixed
> 
> Do you mean the defaultenv-2 doesn't support the bootp feature or do
> you mean let Doug to keep the default boot from net?
> 
> >	I did send patch for this in the past but they did not hit the mainline
> 
> Can you point us this? Thanks.

He meant this patch:

http://lists.infradead.org/pipermail/barebox/2012-September/thread.html#9304

Reading this discussion again I still have mostly the same opinion:
an /env/boot/* script should be simple, it should be adjustable.

We should resolve this now.

So Jean-Christophe, What you want is to boot your board with
informations provided by the dhcp server. Looking again at your patch
back then the following should do it:

/env/boot/bootp:

| #!/bin/sh
| 
| path="/mnt/tftp"
| 
| ifup eth0
| 
| # Set variables based on information provided by the dhcp request
| nfsroot="${global.dhcp.rootpath}"
| global.bootm.image="${path}/${global.dhcp.bootfile}"
| global.bootm.oftree="${path}/${global.dhcp.oftree_file}"
| 
| bootargs-ip
| global.linux.bootargs.dyn.root="root=/dev/nfs nfsroot=$nfsroot,v3,tcp"

Since you reject changes to the default boot source for this board your
other issue seems to be that you want your board to execute this bootscript
without further adjusting the environment. This is something we cannot do.
The default bootsource can only ever fit your personal or someone elses
use. We cannot make everyone happy with the default boot source, so I
suggest you either control your board via some expect script (which
sucks, I know) or you just save your adjusted environment on your test
board.

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:[~2015-02-11  8:35 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-10 14:28 [PATCH 1/2] SAMA5D4EK - Now mostly supports booting Android from NAND Doug Brainard
2015-02-10 14:28 ` [PATCH 2/2] Switched SAMA5D4EK development board to the newer environment method Doug Brainard
2015-02-11  2:34   ` Bo Shen
2015-02-11  4:00     ` Doug Brainard
2015-02-11  5:06       ` Jean-Christophe PLAGNIOL-VILLARD
2015-02-11  7:26         ` Bo Shen
2015-02-11  8:35           ` Sascha Hauer [this message]
2015-02-11  8:54             ` Jean-Christophe PLAGNIOL-VILLARD
2015-02-11  9:12               ` Eric Bénard
2015-02-11  9:19               ` Sascha Hauer
2015-02-11 12:03                 ` Jean-Christophe PLAGNIOL-VILLARD
2015-02-11 14:33                   ` Sascha Hauer
2015-02-11  8:43     ` Sascha Hauer
2015-02-11 16:53       ` Doug Brainard
2015-02-11 16:38     ` Doug Brainard
2015-02-11 17:39       ` Doug Brainard
2015-02-12  9:13         ` Sascha Hauer
2015-02-13  2:57           ` Doug Brainard
2015-02-13  5:32           ` Doug Brainard
2015-02-11  1:30 ` [PATCH 1/2] SAMA5D4EK - Now mostly supports booting Android from NAND Bo Shen
2015-02-11  4:02   ` Doug Brainard
2015-02-11  7:23     ` Bo Shen
2015-02-11  5:04 ` Jean-Christophe PLAGNIOL-VILLARD
2015-02-11  7:42   ` 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=20150211083524.GH12209@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox