mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 2/2] Switched SAMA5D4EK development board to the newer environment method.
Date: Wed, 11 Feb 2015 20:03:08 +0800	[thread overview]
Message-ID: <78248D27-8489-46A4-A2BB-D3F345E5C6D1@jcrosoft.com> (raw)
In-Reply-To: <20150211091948.GK12209@pengutronix.de>


> On Feb 11, 2015, at 5:19 PM, Sascha Hauer <s.hauer@pengutronix.de> wrote:
> 
> On Wed, Feb 11, 2015 at 04:54:09PM +0800, Jean-Christophe PLAGNIOL-VILLARD wrote:
>> 
>>> On Feb 11, 2015, at 4:35 PM, Sascha Hauer <s.hauer@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;
> 
> Let me recap: On the host you have some directory exported as NFS. It
> contains a link to some other position:
> 
> /export/somelink -> /some/other/file
> 
> Now if I mount /export on barebox 'somelink' points to /some/other/file,
> a path that doesn't exist in barebox, some the file cannot be read. The
> NFS command implementation now mounts '/some/other' from the NFS server
> and reads 'file' from that location.
> 
> This is really a misfeature is something that we shouldn't support at
> all.
> 
> Can't you just make your link a relative one inside the exported
> directory? That works just fine and as expected.

unfortunately no can’t do so why not just add my old patch that work in all case

Best Regards,
J.
> 
> 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 12:03 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
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 [this message]
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=78248D27-8489-46A4-A2BB-D3F345E5C6D1@jcrosoft.com \
    --to=plagnioj@jcrosoft.com \
    --cc=barebox@lists.infradead.org \
    --cc=s.hauer@pengutronix.de \
    /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