Date: Wed, 27 Sep 2017 17:13:01 +0200 From: Emmanuel Vadot <manu@bidouilliste.com> To: Ian Lepore <ian@freebsd.org> Cc: freebsd-arm <freebsd-arm@freebsd.org> Subject: Re: CUBOX snapshots working? Message-ID: <20170927171301.8cbf838f481c980d1c5f309a@bidouilliste.com> In-Reply-To: <1506524426.73082.182.camel@freebsd.org> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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: > >=20 > > >=20 > > > [...] > > > haven't worked much with the new imx6 uboot packages because for me > > > they're completely unusable because they lack support for netbooting. > > > =A0(If you feel tempted to say something about efi and netbooting, pl= ease > > > provide links to how-to documentation at the very least, and an examp= le > > > that works for armv6 would be even better.) > > >=20 > > > -- Ian > > =A0Just set 'filename' to loader.efi in dhcpd.conf (if you use isc-dhcp= d) > > and have it served by tftpd. > > =A0In U-boot : > >=20 > > =A0$ env set boot_targets=3Ddhcp (default is different for each board b= ut > > will look like "mmc0 dhcp usb") > > =A0$ env save (if you want it by default) > > =A0$ boot > >=20 > > =A0This will make u-boot do dhcp request, tftp load the DTB (so > > have it in your tftpd directory), loader.efi and run it. > >=20 >=20 > 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 If you can just set the variable in loader.efi and it should work. > Where does loader.efi load the kernel and modules from? =A0How 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. =A0I don't want uboot doing anything on the network itself. =A0How 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. --=20 Emmanuel Vadot <manu@bidouilliste.com> <manu@freebsd.org>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20170927171301.8cbf838f481c980d1c5f309a>