Date: Thu, 17 Oct 2019 21:03:00 +0000 From: greg@unrelenting.technology To: "Colin Percival" <cperciva@tarsnap.com>, freebsd-arm@freebsd.org Subject: Re: EC2 ARM64 "bare metal" instances Message-ID: <120f10da37ee104ea0fb82adeac59c63@unrelenting.technology> In-Reply-To: <0100016dd57b89f3-034edaf3-4ae3-46f6-96ad-a3f0cf202c05-000000@email.amazonses.com> References: <0100016dd57b89f3-034edaf3-4ae3-46f6-96ad-a3f0cf202c05-000000@email.amazonses.com>
next in thread | previous in thread | raw e-mail | index | archive | help
October 16, 2019 7:51 PM, "Colin Percival" <cperciva@tarsnap.com> wrote:= =0A=0A> Hi ARM experts,=0A> =0A> FreeBSD does not currently boot on Amazo= n's recently released "bare metal"=0A> ARM64 instances. It might be usefu= l to get these working, since they're=0A> reasonably powered hardware (16= cores, 32 GB RAM) and should be able to run=0A> bhyve (that's the "bare = metal" part).=0A=0AI know bhyvearm64 only supports GICv3 right now, so I = wonder how bhyvearm64=0Ais going to interact with the GICv2m-on-GICv3 thi= ng they've done=0A(WTF are they smoking?!).. =0A=0A> I'm aware of a few p= atches these systems needed in order to work on Linux=0A=0ANetBSD got sup= port recently too (yes yes I'm checking dmesgd.nycbug quite often :D)=0A= =0Ahttps://github.com/NetBSD/src/commits?author=3Djaredmcneill=0A=0AAppar= ently "downstream ports" in general only have a single device, so this=0A= filtering thing doesn't have to be a Graviton quirk:=0Ahttps://github.com= /NetBSD/src/commit/5969d36d314e797f3ce439a3fd445e5ba9d268f1=0A=0ABut we d= o need the AMZN0001 thing and the GIC thing.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?120f10da37ee104ea0fb82adeac59c63>