[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] Sphinx for QEMU docs? (and a doc-comment format questio
From: |
Paolo Bonzini |
Subject: |
Re: [Qemu-devel] Sphinx for QEMU docs? (and a doc-comment format question) |
Date: |
Mon, 7 Nov 2016 20:43:59 +0100 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 |
On 07/11/2016 19:23, Peter Maydell wrote:
> On 7 November 2016 at 17:50, Paolo Bonzini <address@hidden> wrote:
>> On 07/11/2016 18:20, Peter Maydell wrote:
>>> User and developer, sure, but what's "hardware specifications" for?
>>
>> It's docs/specs.
>
> Those are almost entirely third-party external stuff,
No, they are defined by QEMU: fw_cfg, pvpanic, ivshmem, various
test devices. The ACPI stuff refers to QEMU's implementation of
hotplug, too, and there is the registry of PCI ids defined by
QEMU. It's not all hardware actually---there is stuff like
vhost-user, qcow2, etc.---but generally it's for interoperability.
It's not quite user documentation and definitely not developer
documentation.
Paolo
> unless
> I'm confused about what you have in mind. The best we can do
> is provide links to them, and even there those are likely to
> break from time to time, drift out of date, etc...
>
> thanks
> -- PMM
>
>
Re: [Qemu-devel] Sphinx for QEMU docs? (and a doc-comment format question), Paolo Bonzini, 2016/11/08
Re: [Qemu-devel] Sphinx for QEMU docs? (and a doc-comment format question), Peter Maydell, 2016/11/07
Re: [Qemu-devel] Sphinx for QEMU docs? (and a doc-comment format question), Emilio G. Cota, 2016/11/08