Date: Tue, 18 Sep 2018 13:11:55 +0300 From: Greg V <greg@unrelenting.technology> To: Konstantin Belousov <kostikbel@gmail.com> Cc: Warner Losh <imp@bsdimp.com>, rebecca@bluestop.org, FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: FreeBSD EFI projects Message-ID: <1537265515.2378.0@hraggstad.unrelenting.technology> In-Reply-To: <20180917200935.GD3161@kib.kiev.ua> References: <1dbeee10-857e-7fb2-dac2-1047353739ba@bluestop.org> <CANCZdfpWQyR3KRKYjNRoxzJ1uEEXgT4LPQzgguLMjY=dMMcE%2Bg@mail.gmail.com> <3ce6e6cb-a608-2969-09d4-201df07df586@bluestop.org> <CANCZdfqP3qh-V916d8wyLiKL-Yj_5OBJ05n_85dURsTQbBMHQA@mail.gmail.com> <20180917200935.GD3161@kib.kiev.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Sep 17, 2018 at 11:09 PM, Konstantin Belousov <kostikbel@gmail.com> wrote: > That said, making only the loader->kernel transition from EFI 32bit to > 64bit kernel should be not too hard, and even significantly simpler > than > to make 32bit EFI load 32bit kernel. amd64 kernels already aware that > there might be no BIOS and they do not try to make vm86 calls into > real > code, and only read memory map from the loader metadata etc. > > Besides old Macs, this should also benefit newer Intel embedded-like > boards. Hi, I can confirm that the kernel already worked fine when booted from 32-bit EFI. I booted an old Mac into HardenedBSD using a 32-bit-EFI build of GRUB2 :)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1537265515.2378.0>