Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933368AbbKRUzj (ORCPT ); Wed, 18 Nov 2015 15:55:39 -0500 Received: from SMTP.ANDREW.CMU.EDU ([128.2.157.37]:44655 "EHLO smtp.andrew.cmu.edu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756900AbbKRUzg (ORCPT ); Wed, 18 Nov 2015 15:55:36 -0500 Date: Wed, 18 Nov 2015 15:54:49 -0500 From: "Gabriel L. Somlo" To: =?iso-8859-1?Q?Fran=E7ois?= Revol Cc: Rob Herring , Paolo Bonzini , Mark Rutland , Peter Maydell , mst@redhat.com, stefanha@gmail.com, QEMU Developers , Eric Anholt , kraxel@redhat.com, "linux-api@vger.kernel.org" , Andy Gross , Pawel Moll , kernelnewbies@kernelnewbies.org, =?utf-8?B?UmFmYcWCIE1pxYJlY2tp?= , Russell King , Laszlo Ersek , "devicetree@vger.kernel.org" , Arnd Bergmann , Ian Campbell , jordan.l.justen@intel.com, Kumar Gala , Leif Lindholm , "matt.fleming@intel.com" , Ard Biesheuvel , Greg Kroah-Hartman , "linux-kernel@vger.kernel.org" , Andy Lutomirski , Hanjun Guo , Sudeep Holla Subject: Re: Re: [Qemu-devel] [PATCH v4 4/4] devicetree: update documentation for fw_cfg ARM bindings Message-ID: <20151118205448.GD2109@HEDWIG.INI.CMU.EDU> References: <1447470235-13643-1-git-send-email-somlo@cmu.edu> <1447470235-13643-5-git-send-email-somlo@cmu.edu> <20151115020754.GA21323@rob-hp-laptop> <564995FA.40308@redhat.com> <564C7758.6010103@free.fr> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <564C7758.6010103@free.fr> X-Clacks-Overhead: GNU Terry Pratchett User-Agent: Mutt/1.5.24 (2015-08-30) X-PMX-Version: 6.0.3.2322014, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2015.11.18.204216 X-SMTP-Spam-Clean: 8% ( MULTIPLE_RCPTS 0.1, HTML_00_01 0.05, HTML_00_10 0.05, BODYTEXTP_SIZE_3000_LESS 0, BODY_SIZE_2000_2999 0, BODY_SIZE_5000_LESS 0, BODY_SIZE_7000_LESS 0, DATE_TZ_NA 0, FROM_EDU_TLD 0, NO_URI_HTTPS 0, REFERENCES 0, __ANY_URI 0, __BOUNCE_CHALLENGE_SUBJ 0, __BOUNCE_NDR_SUBJ_EXEMPT 0, __CD 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __FORWARDED_MSG 0, __HAS_FROM 0, __HAS_MSGID 0, __IN_REP_TO 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __MULTIPLE_RCPTS_CC_X2 0, __PHISH_SPEAR_STRUCTURE_1 0, __REFERENCES 0, __SANE_MSGID 0, __SUBJ_ALPHA_END 0, __SUBJ_ALPHA_NEGATE 0, __TO_MALFORMED_2 0, __URI_NO_PATH 0, __URI_NO_WWW 0, __URI_NS , __USER_AGENT 0) X-SMTP-Spam-Score: 8% Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2505 Lines: 56 On Wed, Nov 18, 2015 at 02:04:24PM +0100, Fran?ois Revol wrote: > On 17/11/2015 23:14, Rob Herring wrote: > > On Mon, Nov 16, 2015 at 2:38 AM, Paolo Bonzini wrote: > >> > >> > >> On 15/11/2015 03:07, Rob Herring wrote: > >>> We generally don't want DT docs to depend on other kernel documentation. > >> > >> DT docs do not contain a copy of the data sheets, either. There is no > >> reason to say how to use the device (and even then, only doing so > >> partially) in the DT docs. > > > > The difference is datasheets apply to all OS's, kernel documentation > > does not. In theory at least this could be used for other OS's, right? > > Would be nice indeed, as it's part of their intended purpose. > > For now we have to shoehorn things into linux-only stuff (like initrd) > because well, nobody cares enough about NetBSD to compile U-Boot with > its internal API, so let alone adding custom Haiku code. > > And of course, for things linux doesn't care about (like framebuffer > description) then we're stuck trying to guess where it's at and writing > drivers for our bootloader. > > So if at least people were considering they aren't the only users of > this, that'd make life better for everyone. > > > Perhaps QEMU is the right place to thoroughly describe this and DT and > > sysfs docs can refer to it. > > The brilliant idea of FDT was that we could have a canonical source and > blob for it where people could send patches, but of course Linux and BSD > freaks disagreed, so you now find Linux-flavoured DTs for rPi and other > things, as well as BSD versions. > > Please, at least get the binding documentation for this unique and > usable for everyone! That would be 'docs/specs/fw_cfg.txt' in the QEMU source tree. I will avoid cut'n'pasting anything from there into either the proposed Documentation/ABI/testing/sysfs-firmware-qemu_fw_cfg (leaving only the sysfs specific bits in there), and also remove any redundant bits from Documentation/devicetree/bindings/arm/fw-cfg.txt. I'm inclined to add (in v5) a mention of 'qemu:docs/specs/fw_cfg.txt' to both the proposed fw_cfg sysfs doc file, and to the existing fw_cfg arm/dt node doc file, unless I get strong objections against doing so... :) Thanks, --Gabriel -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/