Date: Fri, 15 Jul 2016 15:17:52 -0600 From: Ian Lepore <ian@freebsd.org> To: Karl Denninger <karl@denninger.net>, freebsd-arm@freebsd.org Subject: Re: Bizarre clone attempt failures on Raspberry Pi2... Message-ID: <1468617472.72182.340.camel@freebsd.org> In-Reply-To: <e4cf45b4-8df4-05e5-9eb7-00cccc8d224b@denninger.net> References: <201607151729.u6FHT9PT068989@pdx.rh.CN85.ChatUSA.com> <151CAE3A-CAA6-49FB-A150-7AAA8981E013@gromit.dlib.vt.edu> <CABx9NuRF6_ODwZATnneEW1GekZLSCkzvdEhPbdFZ2rrbAi9-PA@mail.gmail.com> <e4cf45b4-8df4-05e5-9eb7-00cccc8d224b@denninger.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 2016-07-15 at 16:03 -0500, Karl Denninger wrote: > As an aside the new u-boot *does* speak to a USB keyboard out-of-box. > > I am going to attempt to build the environment in boot.scr, which > should > work (since it reads THAT as well off the boot media) -- if that > works > it obviates the need for a specific compilation for FreeBSD in the > port. > > Needless to say that's a fairly-material win if it works. > FreeBSD needs a build of u-boot that adds the CONFIG_API option so that loader(8) works. From what I've heard, recent versions of u-boot have broken the CONFIG_API option as part of the "device model" work. So a u-boot new enough that usb keyboards work on rpi is probably too new to work with our need for CONFIG_API. Our path forward probably involves abandoning CONFIG_API (since they seem disinclined to support it) and using the new EFI support u-boot provides. But we don't have an EFI loader for armv6 yet either (and I don't know that anybody has worked on that yet). -- Ian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1468617472.72182.340.camel>