From: Al Stone <al.stone@linaro.org>
To: Andrew Jones <drjones@redhat.com>,
Shannon Zhao <zhaoshenglong@huawei.com>
Cc: peter.maydell@linaro.org, qemu-devel@nongnu.org,
Leif Lindholm <leif.lindholm@linaro.org>,
shannon.zhao@linaro.org
Subject: Re: [Qemu-devel] [PATCH 0/2] ACPI/arm-virt: add DBG2
Date: Wed, 9 Sep 2015 15:23:48 -0600 [thread overview]
Message-ID: <55F0A364.1050809@linaro.org> (raw)
In-Reply-To: <20150909055213.GA3037@hawk.localdomain>
On 09/08/2015 11:52 PM, Andrew Jones wrote:
> On Wed, Sep 09, 2015 at 12:25:45PM +0800, Shannon Zhao wrote:
>>
>>
>> On 2015/9/8 21:04, Leif Lindholm wrote:
>>> On Tue, Sep 08, 2015 at 11:18:27AM +0800, Shannon Zhao wrote:
>>>> On 2015/9/7 22:23, Leif Lindholm wrote:
>>>>> The Debug Port Table 2 (DBG2) is mandated by the ARM Server Base Boot
>>>>> Requirements specification. Add the DBG2 table definitions, and set up
>>>>> an entry in the ARM virt machine for the pl011 UART.
>>>>
>>>> Looking at Documentation/arm64/acpi_object_usage.txt in Linux kernel, it
>>>> says
>>>> "
>>>> DBG2 Signature Reserved (signature == "DBG2")
>>>> == DeBuG port table 2 ==
>>>> Microsoft only table, will not be supported.
>>>> "
>>>> It seems that Linux kernel doesn't support or need it, but Windows
>>>> requires it. So does it need to test this on Windows?
>>>
>>> No, it can be tested under Linux with the set I just sent out:
>>> http://lists.infradead.org/pipermail/linux-arm-kernel/2015-September/368614.html
>>
>> So you need to change Documentation/arm64/acpi_object_usage.txt as well.
>> But that is kernel side.
>
> I also wonder if Documentation/arm64/arm-acpi.txt should have its
> "Booting using ACPI tables" section updated to reference (describe even?)
> the use of SPCR. Maybe Leif's already doing that with the
> this-time-really-for-upstream kernel spcr patches.
>
> drew
>
It's on my TODO list to update this documentation properly, to
include updates on DBG2 and SPCR along with a bunch of other
ACPI 6.0 changes. My bad for the delays on this...
--
ciao,
al
-----------------------------------
Al Stone
Software Engineer
Linaro Enterprise Group
al.stone@linaro.org
-----------------------------------
prev parent reply other threads:[~2015-09-09 21:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-07 14:23 [Qemu-devel] [PATCH 0/2] ACPI/arm-virt: add DBG2 Leif Lindholm
2015-09-07 14:23 ` [Qemu-devel] [PATCH 1/2] ACPI: Add definitions for the DBG2 table Leif Lindholm
2015-09-07 15:51 ` Andrew Jones
2015-09-10 8:19 ` Michael S. Tsirkin
2015-09-10 10:08 ` Igor Mammedov
2015-09-08 3:27 ` Shannon Zhao
2015-09-08 13:10 ` Leif Lindholm
2015-09-07 14:23 ` [Qemu-devel] [PATCH 2/2] hw/arm/virt-acpi-build: Add " Leif Lindholm
2015-09-07 15:59 ` Andrew Jones
2015-09-08 3:18 ` [Qemu-devel] [PATCH 0/2] ACPI/arm-virt: add DBG2 Shannon Zhao
2015-09-08 13:04 ` Leif Lindholm
2015-09-09 4:25 ` Shannon Zhao
2015-09-09 5:52 ` Andrew Jones
2015-09-09 21:23 ` Al Stone [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=55F0A364.1050809@linaro.org \
--to=al.stone@linaro.org \
--cc=drjones@redhat.com \
--cc=leif.lindholm@linaro.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=shannon.zhao@linaro.org \
--cc=zhaoshenglong@huawei.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).