From: Paolo Bonzini <pbonzini@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] Sphinx for QEMU docs? (and a doc-comment format question)
Date: Mon, 7 Nov 2016 20:43:59 +0100 [thread overview]
Message-ID: <594ec495-cbb9-e60c-2a35-47d308ca9ed8@redhat.com> (raw)
In-Reply-To: <CAFEAcA_vbHsXC5oh4in7=9DNfX+RKFtgQ8xhPUPNd8Rne9GKgw@mail.gmail.com>
On 07/11/2016 19:23, Peter Maydell wrote:
> On 7 November 2016 at 17:50, Paolo Bonzini <pbonzini@redhat.com> 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
>
>
next prev parent reply other threads:[~2016-11-07 19:44 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-05 18:42 [Qemu-devel] Sphinx for QEMU docs? (and a doc-comment format question) Peter Maydell
2016-11-07 9:35 ` Daniel P. Berrange
2016-11-07 13:30 ` Stefan Hajnoczi
2016-11-07 13:41 ` Daniel P. Berrange
2016-11-07 13:49 ` Peter Maydell
2016-11-07 22:52 ` John Snow
2016-11-08 16:20 ` Stefan Hajnoczi
2016-11-08 16:24 ` John Snow
2016-11-09 11:32 ` Stefan Hajnoczi
2016-11-10 3:39 ` Fam Zheng
2016-11-10 9:55 ` Stefan Hajnoczi
2016-11-10 10:08 ` Paolo Bonzini
2016-11-10 10:55 ` Daniel P. Berrange
2016-11-08 23:56 ` Paolo Bonzini
2016-11-07 15:03 ` Peter Maydell
2016-11-07 17:04 ` Paolo Bonzini
2016-11-07 17:20 ` Peter Maydell
2016-11-07 17:50 ` Paolo Bonzini
2016-11-07 18:23 ` Peter Maydell
2016-11-07 19:43 ` Paolo Bonzini [this message]
2016-11-07 20:36 ` Peter Maydell
2016-11-08 5:02 ` Emilio G. Cota
2017-01-05 16:47 ` Paolo Bonzini
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=594ec495-cbb9-e60c-2a35-47d308ca9ed8@redhat.com \
--to=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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).