From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:56512) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1c3ppw-0007m3-H4 for qemu-devel@nongnu.org; Mon, 07 Nov 2016 14:44:09 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1c3pps-0001vX-LQ for qemu-devel@nongnu.org; Mon, 07 Nov 2016 14:44:08 -0500 Received: from mail-wm0-x22b.google.com ([2a00:1450:400c:c09::22b]:38615) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1c3pps-0001uM-EF for qemu-devel@nongnu.org; Mon, 07 Nov 2016 14:44:04 -0500 Received: by mail-wm0-x22b.google.com with SMTP id f82so139648206wmf.1 for ; Mon, 07 Nov 2016 11:44:03 -0800 (PST) Sender: Paolo Bonzini References: From: Paolo Bonzini Message-ID: <594ec495-cbb9-e60c-2a35-47d308ca9ed8@redhat.com> Date: Mon, 7 Nov 2016 20:43:59 +0100 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Subject: Re: [Qemu-devel] Sphinx for QEMU docs? (and a doc-comment format question) List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Maydell Cc: QEMU Developers , Stefan Hajnoczi On 07/11/2016 19:23, Peter Maydell wrote: > On 7 November 2016 at 17:50, Paolo Bonzini 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 > >