[PATCH 2/2] Switched SAMA5D4EK development board to the newer environment method.

[Jean-Christophe PLAGNIOL-VILLARD]

> On Feb 11, 2015, at 4:35 PM, Sascha Hauer <s.hauer at pengutronix.de> wrote:
> 
> 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}”

this is not possible unfortunately

As if you use symlink the nfs will not work
it was work on defaultenv as it’s use the nfs commande and not FS
The nfs command handle symlink;w

that why in my patch I had to mount the fs first then remount it if it’s a symlink

so today the defaultenv-2 break the bootp support


> | 
> | 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.

When the defaultenv-2 will support bootp I’ll be the first to get rid of the old defaultenv
but today I have automatic test system that depends on it to test linux on at91 and others

Best Regards,
J.