Date: Wed, 27 Sep 2017 09:26:00 -0600 From: Ian Lepore <ian@freebsd.org> To: Emmanuel Vadot <manu@bidouilliste.com> Cc: freebsd-arm <freebsd-arm@freebsd.org> Subject: Re: CUBOX snapshots working? Message-ID: <1506525960.31939.3.camel@freebsd.org> In-Reply-To: <20170927171301.8cbf838f481c980d1c5f309a@bidouilliste.com> References: <201709260339.VAA16701@mail.lariat.net> <1506435673.73082.129.camel@freebsd.org> <201709261732.LAA21422@mail.lariat.net> <20170926200446.c188fda613df2ffb894b1ff3@bidouilliste.com> <1506450112.73082.143.camel@freebsd.org> <20170926204622.67ae9edbca62e2dcdbd1ea31@bidouilliste.com> <CABx9NuRSCe54e%2B3LjOJphGP=5EAWYbBtub-%2BEvsE9JHXYdcmbw@mail.gmail.com> <1506460653.73082.156.camel@freebsd.org> <CANCZdfqAM-kXuBq2YcngR9PKajxJSTa_UNpm-v7zbMH2bvpo6g@mail.gmail.com> <1506466528.73082.172.camel@freebsd.org> <20170927112413.4fc048082df75f51a4b71eea@bidouilliste.com> <1506524426.73082.182.camel@freebsd.org> <20170927171301.8cbf838f481c980d1c5f309a@bidouilliste.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 2017-09-27 at 17:13 +0200, Emmanuel Vadot wrote: > > > On Wed, 27 Sep 2017 09:00:26 -0600 > Ian Lepore <ian@freebsd.org> wrote: > > > > > On Wed, 2017-09-27 at 11:24 +0200, Emmanuel Vadot wrote: > > > > > > On Tue, 26 Sep 2017 16:55:28 -0600 > > > Ian Lepore <ian@freebsd.org> wrote: > > > > > > > > > > > > > > > [...] > > > > haven't worked much with the new imx6 uboot packages because > > > > for me > > > > they're completely unusable because they lack support for > > > > netbooting. > > > > (If you feel tempted to say something about efi and > > > > netbooting, please > > > > provide links to how-to documentation at the very least, and an > > > > example > > > > that works for armv6 would be even better.) > > > > > > > > -- Ian > > > Just set 'filename' to loader.efi in dhcpd.conf (if you use isc- > > > dhcpd) > > > and have it served by tftpd. > > > In U-boot : > > > > > > $ env set boot_targets=dhcp (default is different for each board > > > but > > > will look like "mmc0 dhcp usb") > > > $ env save (if you want it by default) > > > $ boot > > > > > > This will make u-boot do dhcp request, tftp load the DTB (so > > > have it in your tftpd directory), loader.efi and run it. > > > > > What if I don't have control over the dhcp server config, how can I > > locally configure what file to load? > From U-Boot: > $ dhcp > $ tftp $kernel_addr_r <ip> <filename> > > Or something like that, run 'tftp help' or 'help tftp' I never > recall. > > > > > What if I'm running nfs, but not a tftp server? > I don't know if in loader.efi you can use the ip stack from the EFI > firmware without doing tftp/bootp tftp and bootp have nothing to do with each other. A common situation for people is that an IP address is available via dhcp or bootp, but they have no control over other boot parms delivered along with the basic IP info. In some cases that other info (rootpath, filename, etc) is present but wildly wrong and must be ignored. There needs to be a way to locally override such info and specify the tftp or nfs server and path locally. -- Ian > If you can just set the variable in loader.efi and it should work. > > > Where does loader.efi load the kernel and modules from? How do I > > control / change that? > from the loaddev variable iirc > > > > > The configuration I prefer is that loader(8) comes from local > > storage > > (sdcard, whatever), and it loads the kernel, the dtb, and modules, > > via > > nfs. I don't want uboot doing anything on the network itself. How > > do > > I configure that? > You can try setting the loaddev to net under loader.efi > > The main reason to use efi is that we have (in theory) the same > support as on amd64. > Maybe some of your scenario can't work ATM I don't know, best way is > to try. >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1506525960.31939.3.camel>