Date: Wed, 19 Sep 2018 16:37:22 -0700 From: Warner Losh <imp@bsdimp.com> To: rebecca@bluestop.org Cc: Ed Maste <emaste@freebsd.org>, "Rodney W. Grimes" <freebsd-rwg@pdx.rh.cn85.dnsmgr.net>, greg@unrelenting.technology, Konstantin Belousov <kostikbel@gmail.com>, FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: FreeBSD EFI projects Message-ID: <CANCZdfpnop6N00-4cD0DM6dWAz5nhQpNehiwc%2BV8c6ME%2BCZZww@mail.gmail.com> In-Reply-To: <4f40c03a-1e7a-0f09-5780-3ce6b0ec1a4e@bluestop.org> References: <76404aad-40f3-e3ad-35b1-949fb5afb086@bluestop.org> <201809191434.w8JEY41Z024163@pdx.rh.CN85.dnsmgr.net> <CAPyFy2DSSCiH-Q13_C_cM%2BoAN3nfy2YLQh-JDCQzL47pYgjTiA@mail.gmail.com> <4f40c03a-1e7a-0f09-5780-3ce6b0ec1a4e@bluestop.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Sep 19, 2018 at 4:33 PM Rebecca Cran <rebecca@bluestop.org> wrote: > Oh, that's a really good point - thanks! I happen to have a Minnowboard > Turbot currently sitting unused. > One other idea, unrelated to the 32-bit UEFI to boot 64-bit kernel, is to see about mining tsoome@'s port of FreeBSD boot loader to OpenIndiana. He's done a lot of cool things that would be useful to bring in, but need someone with a UEFI clue to do it. He's not had the time to get them reviewed and tested in our environment, if I understand correctly. You might want to reach out to him to see if there's things that would be useful. The biggest one I can think of is that his efi show variable code knows about standard UEFI variables and prints them out interpreted, not in unhelpful without the standard handy binary form like our loader does. Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfpnop6N00-4cD0DM6dWAz5nhQpNehiwc%2BV8c6ME%2BCZZww>