From owner-freebsd-arm@freebsd.org Sat Nov 26 12:57:40 2016 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 72A9CC56124 for ; Sat, 26 Nov 2016 12:57:40 +0000 (UTC) (envelope-from jrc@skylon.demon.co.uk) Received: from smtp.demon.co.uk (mdfmta010.mxout.tch.inty.net [91.221.169.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 11BF5BD4 for ; Sat, 26 Nov 2016 12:57:38 +0000 (UTC) (envelope-from jrc@skylon.demon.co.uk) Received: from mdfmta010.tch.inty.net (unknown [127.0.0.1]) by mdfmta010.tch.inty.net (Postfix) with ESMTP id 59D45401987 for ; Sat, 26 Nov 2016 12:51:58 +0000 (GMT) Received: from mdfmta010.tch.inty.net (unknown [127.0.0.1]) by mdfmta010.tch.inty.net (Postfix) with ESMTP id 3072840195A for ; Sat, 26 Nov 2016 12:51:58 +0000 (GMT) Received: from skylon.dyndns.org (unknown [81.104.142.175]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mdfmta010.tch.inty.net (Postfix) with ESMTP for ; Sat, 26 Nov 2016 12:51:58 +0000 (GMT) Received: from router.home.verminmedia.com ([192.168.199.1] helo=[192.168.199.2]) by skylon.dyndns.org with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.86_2) (envelope-from ) id 1cAcRx-0005hU-IM for freebsd-arm@freebsd.org; Sat, 26 Nov 2016 12:51:25 +0000 To: freebsd-arm@freebsd.org From: John Connett Subject: Booting FreeBSD from Windows 10 IoT Core EFI? Message-ID: Date: Sat, 26 Nov 2016 12:51:02 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.5.0 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="1CPDHEKLWXfu4ownoB2PljnKU9iERh3vJ" X-MDF-HostID: 19 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Nov 2016 12:57:40 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --1CPDHEKLWXfu4ownoB2PljnKU9iERh3vJ Content-Type: multipart/mixed; boundary="X2Ownw6LaGMhimNsKfwEjN2oiJ9uH0o0E"; protected-headers="v1" From: John Connett To: freebsd-arm@freebsd.org Message-ID: Subject: Booting FreeBSD from Windows 10 IoT Core EFI? --X2Ownw6LaGMhimNsKfwEjN2oiJ9uH0o0E Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Windows 10 IoT Core on Raspberry Pi 3 (and Dragonboard 410c) appears to boot using EFI. The following link demonstrates that a faulty boot can result in an EFI start prompt: https://social.msdn.microsoft.com/Forums/en-US/426f4537-59c3-4fe1-9f09-26= 47a9c8b71d/raspberry-pi-3-booting-to-efi-screen Has anyone tried booting FreeBSD using this version of EFI? I suspect it originates from Broadcom and is probably licensed for use on their devices. Might be an alternative to the "u-boot efi option" mentioned on a thread in this list last month. I have both a Raspberry Pi 3 and Dragonboard 410c on which I could experiment if someone could give me pointer on where to start. --X2Ownw6LaGMhimNsKfwEjN2oiJ9uH0o0E-- --1CPDHEKLWXfu4ownoB2PljnKU9iERh3vJ Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iLMEAQECAB0WIQSkgaq2sCio4xbyyp3JMiZNt4huWQUCWDmFQAAKCRDJMiZNt4hu WWm+A/wMJwAM7rI3bUTox0fcq+guvEw9pajQLKdtQj2mYk4/GyfF6OQ8JuM5R0hu LOucRHFRf70EptnbIcubInIng6m5u3gWdwltBuNlFd6URPqW5W+pmkK+Jfru2OsM KpwANe7P0pAXLhxhz6Baiz7UQCHk0Cs4gURnja0qORH+5y9/vg== =6lgZ -----END PGP SIGNATURE----- --1CPDHEKLWXfu4ownoB2PljnKU9iERh3vJ--