Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 30 Apr 2017 17:40:57 +0100
From:      Andrew Turner <andrew@fubar.geek.nz>
To:        Mark Millard <markmi@dsl-only.net>
Cc:        freebsd-arm <freebsd-arm@freebsd.org>, FreeBSD Current <freebsd-current@freebsd.org>
Subject:   Re: FYI: FreeBSD-12.0-CURRENT-arm64-aarch64-20170420-r317181.raw under qemu-system-aarch64 on odroid-c2 under UbuntuMate : No valid device tree blob found!
Message-ID:  <61C08AFE-0BE8-4BDE-B50C-09268850AE21@fubar.geek.nz>
In-Reply-To: <47F6A67D-2D97-4992-96CE-45751190CA86@dsl-only.net>
References:  <FF5D8468-CE04-411A-9F3C-10EF5F21D9E5@dsl-only.net> <D2E876BD-A23F-4C33-A0B6-8F1A862C11D6@fubar.geek.nz> <47F6A67D-2D97-4992-96CE-45751190CA86@dsl-only.net>

next in thread | previous in thread | raw e-mail | index | archive | help

> On 30 Apr 2017, at 12:02, Mark Millard <markmi@dsl-only.net> wrote:
>=20
> On 2017-Apr-30, at 1:57 AM, Andrew Turner <andrew at fubar.geek.nz> =
wrote:
>=20
>>> On 30 Apr 2017, at 04:29, Mark Millard <markmi at dsl-only.net> =
wrote:
>>> ...
>>> acpi0: <BOCHS BXPCFACP>
>>> acpi0: Power Button (fixed)
>>> acpi0: Sleep Button (fixed)
>>=20
>> ACPI is not fully supported on arm64.
>=20
> Good to know. Thanks.
>=20
> But the messages:
>=20
> No valid device tree blob found!
> WARNING! Trying to fire up the kernel, but no device tree blob found!
>=20
> were well before the acpi0 messages so I'd expect
> that the lack of a "device tree blob" is a separate,
> earlier issue, likely to do with the content of:
>=20
> FreeBSD-12.0-CURRENT-arm64-aarch64-20170420-r317181.raw

No, the device tree blob comes from UEFI. It seems the current UEFI only =
provides the ACPI tables, and not a DTB.

Andrew




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?61C08AFE-0BE8-4BDE-B50C-09268850AE21>