Date: Thu, 12 Jul 2018 08:07:40 -0600 From: Ian Lepore <ian@freebsd.org> To: Emmanuel Vadot <manu@bidouilliste.com>, Greg V <greg@unrelenting.technology> Cc: freebsd-arm@freebsd.org Subject: Re: Netbooting ROCK64 Message-ID: <1531404460.66719.26.camel@freebsd.org> In-Reply-To: <20180712160051.ab6447bad4d97395552c3a5d@bidouilliste.com> References: <1531333209.1596.0@hraggstad.unrelenting.technology> <20180712120405.a16a2733473400e899f34d2f@bidouilliste.com> <1531392570.1456.0@hraggstad.unrelenting.technology> <20180712160051.ab6447bad4d97395552c3a5d@bidouilliste.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 2018-07-12 at 16:00 +0200, Emmanuel Vadot wrote:
> > env set bootargs boot.nfsroot.server=${serverip}
> > boot.nfsroot.path=<PATH> comconsole_speed=${baudrate}
> > tftpboot ${kernel_addr_r} loader.efi
> > bootefi ${kernel_addr_r} ${fdtcontroladdr}
>
> I've never used nfs with loader like this, do you control the dhcp ?
> If so just set the correct rootpath in it and in uboot just do :
> setenv boot_targets dhcp
> saveenv
This is really not a good enough answer. Many people have dhcp, not
nearly as many have easy access to control the config of that dhcp
server.
It MUST be possible to set tftp and/or nfs boot parms from some
persisent config on the system being booted, or we just don't have a
viable netboot solution.
Pre-efi, all you had to do for netbooting was
setenv loaderdev net
setenv rootpath serverip:/path/to/rootfs
boot
It sure would be nice if we could maintain that level of simplicity
with efi uboot.
-- Ian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1531404460.66719.26.camel>