[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [Qemu-arm] [PATCH] target-arm: Declare virtio-mmio as d

From: Heyi Guo
Subject: Re: [Qemu-devel] [Qemu-arm] [PATCH] target-arm: Declare virtio-mmio as dma-coherent in dt
Date: Thu, 9 Feb 2017 20:04:45 +0800
User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.5.0

Hi all,

Just to confirm that FWTS is supporting aarch64.

Alex is the maintainer of FWTS and may provide more information.


Gary (Heyi Guo)

在 2/9/2017 2:47 AM, Laszlo Ersek 写道:
On 02/08/17 19:23, Peter Maydell wrote:
On 8 February 2017 at 16:27, Ard Biesheuvel <address@hidden> wrote:
The _CCA property is mandatory on arm64, and there is no default.
Is there a tool that can check this kind of requirement
and complain about issues in the ACPI tables (and
ditto, device tree)? It's really easy to produce a
dt or ACPI table that works with current kernels and
then turns out to have a problem six or twelve
months down the line :-(
I think the "bios bits" project or the FWTS (firmware test suite)
project might do some ACPI sanity checks. They could be run in guests.


However, I'm unsure if they support aarch64. Also... it's not like those
projects are stationary. Even the ACPI spec is a moving target (and
spec-level regressions exist).

I believe Heyi Guo @ Linaro used to work with FWTS on aarch64. CC'd.

No clue about DT conformance testing. Is there an industry standard or a
working group behind DT?


reply via email to

[Prev in Thread] Current Thread [Next in Thread]