From: Guillaume Gardet <guillaume.gardet@free.fr>
To: u-boot@lists.denx.de
Subject: [U-Boot] NFSv2 => NFSv3
Date: Fri, 10 Jun 2016 09:36:53 +0200 [thread overview]
Message-ID: <575A6E15.5010003@free.fr> (raw)
In-Reply-To: <CANr=Z=ZK815Ro5C28jXTrE2u3qdhZWag8Ovcm3ccDPYuMpz9Hw@mail.gmail.com>
Hi,
Le 09/06/2016 18:20, Joe Hershberger a ?crit :
> Hi Guillaume,
>
> On Thu, Jun 2, 2016 at 9:26 AM, Joe Hershberger
> <joe.hershberger@gmail.com> wrote:
>> On Thu, Jun 2, 2016 at 8:39 AM, Guillaume Gardet
>> <guillaume.gardet@free.fr> wrote:
>>> Hi,
>>>
>>> I am facing a problem with U-Boot.
>>> Our NFS server supports NFS v3 and v4 but it seems that U-Boot is NFS v2
>>> only.
>>>
>>> Is there any plan to update to v3? Otherwise, I could help, but I would need
>>> some pointers to NFS protocol handling.
>> I'm not aware of anyone working on that. Maybe someone more familiar
>> with NFS could help, or look at the differences in the Linux
>> implementations.
> I received a note from bodhi bodhi <mibodhi@gmail.com> that he is
> successfully using NFS v3 with modern U-Boot (since 2014).
>
> Here are the details of the environment that he included...
I think he uses NFSv3 for the root filesystem but the NFS server is also NFSv2 compatible for u-boot nfs loads (uImage and DTB).
Guillaume
>
> bootcmd_nfs=setenv nfs_server "192.168.0.224"; setenv nfs_path
> "/srv/nfs/hosts/tldDebian2"; setenv nfs_bootcmd "run nfs_set_bootargs;
> run nfs_boot"; setenv nfs_ipconfig
> "192.168.0.229:192.168.0.224:192.168.0.1:255.255.0.0:tldDebian2::off";
> setenv nfs_set_bootargs "setenv bootargs console=ttyS0,115200
> root=/dev/nfs nfsroot=$nfs_server:$nfs_path,v3 rootfstype=nfs rootwait
> ip=$nfs_ipconfig $mtdparts"; setenv nfs_load_uimage "nfs 0x800000
> $nfs_server:$nfs_path/boot/uImage"; setenv nfs_load_uinitrd "nfs
> 0x1100000 $nfs_server:$nfs_path/boot/uInitrd"; setenv nfs_load_dtb
> "nfs 0x1c00000 $nfs_server:$nfs_path/boot/dts/kirkwood-pogo_e02.dtb";
> setenv nfs_bootm "bootm 0x800000 0x1100000 0x1c00000"; setenv nfs_boot
> "run nfs_load_uimage; run nfs_load_uinitrd; run nfs_load_dtb; run
> nfs_bootm"; echo "Booting NFS root?"; run nfs_bootcmd
>
> Thanks, Bodhi.
>
> Cheers,
> -Joe
>
prev parent reply other threads:[~2016-06-10 7:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-02 13:39 [U-Boot] NFSv2 => NFSv3 Guillaume Gardet
2016-06-02 14:26 ` Joe Hershberger
2016-06-09 16:20 ` Joe Hershberger
2016-06-10 7:36 ` Guillaume Gardet [this message]
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=575A6E15.5010003@free.fr \
--to=guillaume.gardet@free.fr \
--cc=u-boot@lists.denx.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