Date: Tue, 18 Sep 2018 23:31:14 -0600 From: Rebecca Cran <rebecca@bluestop.org> To: Greg V <greg@unrelenting.technology>, Konstantin Belousov <kostikbel@gmail.com> Cc: Warner Losh <imp@bsdimp.com>, FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: FreeBSD EFI projects Message-ID: <76404aad-40f3-e3ad-35b1-949fb5afb086@bluestop.org> In-Reply-To: <1537265515.2378.0@hraggstad.unrelenting.technology> 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> <1537265515.2378.0@hraggstad.unrelenting.technology>
next in thread | previous in thread | raw e-mail | index | archive | help
On 9/18/18 4:11 AM, Greg V wrote: > > 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 :) Was that a 64-bit version of FreeBSD? My understanding is the 32-bit FreeBSD boots fine, but 64-bit needs work. -- Rebecca
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?76404aad-40f3-e3ad-35b1-949fb5afb086>