From mboxrd@z Thu Jan 1 00:00:00 1970 From: revol@free.fr (=?UTF-8?Q?Fran=c3=a7ois_Revol?=) Date: Wed, 18 Nov 2015 14:04:24 +0100 Subject: [Qemu-devel] [PATCH v4 4/4] devicetree: update documentation for fw_cfg ARM bindings In-Reply-To: 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> Message-ID: <564C7758.6010103@free.fr> To: kernelnewbies@lists.kernelnewbies.org List-Id: kernelnewbies.lists.kernelnewbies.org 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! Fran?ois. From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?UTF-8?Q?Fran=c3=a7ois_Revol?= Subject: Re: [PATCH v4 4/4] devicetree: update documentation for fw_cfg ARM bindings Date: Wed, 18 Nov 2015 14:04:24 +0100 Message-ID: <564C7758.6010103@free.fr> 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> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org Sender: qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org To: Rob Herring , Paolo Bonzini Cc: Mark Rutland , Peter Maydell , mst@redhat.com, stefanha@gmail.com, QEMU Developers , "linux-kernel@vger.kernel.org" , Eric Anholt , kraxel@redhat.com, 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, "Gabriel L. Somlo" , Kumar Gala , Leif Lindholm , Sudeep Holla , "matt.fleming@intel.com" , Ard Biesheuvel lin List-Id: linux-api@vger.kernel.org On 17/11/2015 23:14, Rob Herring wrote: > On Mon, Nov 16, 2015 at 2:38 AM, Paolo Bonzini wr= ote: >> >> >> On 15/11/2015 03:07, Rob Herring wrote: >>> We generally don't want DT docs to depend on other kernel documentati= on. >> >> 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. >=20 > 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! Fran=E7ois. From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933553AbbKRR4G (ORCPT ); Wed, 18 Nov 2015 12:56:06 -0500 Received: from smtpfb2-g21.free.fr ([212.27.42.10]:41819 "EHLO smtpfb2-g21.free.fr" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933511AbbKRR4A (ORCPT ); Wed, 18 Nov 2015 12:56:00 -0500 Subject: Re: Re: [Qemu-devel] [PATCH v4 4/4] devicetree: update documentation for fw_cfg ARM bindings To: Rob Herring , Paolo Bonzini 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> Cc: 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, "Gabriel L. Somlo" , Kumar Gala , Leif Lindholm , "matt.fleming@intel.com" , Ard Biesheuvel , Greg Kroah-Hartman , "linux-kernel@vger.kernel.org" , Andy Lutomirski , Hanjun Guo , Sudeep Holla From: =?UTF-8?Q?Fran=c3=a7ois_Revol?= X-Enigmail-Draft-Status: N1110 Message-ID: <564C7758.6010103@free.fr> Date: Wed, 18 Nov 2015 14:04:24 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Icedove/38.3.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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! François. From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:44405) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Zz2Q8-0000Yg-DG for qemu-devel@nongnu.org; Wed, 18 Nov 2015 08:05:14 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Zz2Q2-0002rV-Ry for qemu-devel@nongnu.org; Wed, 18 Nov 2015 08:05:08 -0500 Received: from smtp5-g21.free.fr ([2a01:e0c:1:1599::14]:39220) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Zz2Q2-0002qy-MO for qemu-devel@nongnu.org; Wed, 18 Nov 2015 08:05:02 -0500 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> From: =?UTF-8?Q?Fran=c3=a7ois_Revol?= Message-ID: <564C7758.6010103@free.fr> Date: Wed, 18 Nov 2015 14:04:24 +0100 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] [PATCH v4 4/4] devicetree: update documentation for fw_cfg ARM bindings List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Rob Herring , Paolo Bonzini Cc: Mark Rutland , Peter Maydell , mst@redhat.com, stefanha@gmail.com, QEMU Developers , "linux-kernel@vger.kernel.org" , Eric Anholt , kraxel@redhat.com, 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, "Gabriel L. Somlo" , Kumar Gala , Leif Lindholm , Sudeep Holla , "matt.fleming@intel.com" , Ard Biesheuvel , "linux-api@vger.kernel.org" , Greg Kroah-Hartman , Andy Lutomirski , Hanjun Guo , Andy Gross On 17/11/2015 23:14, Rob Herring wrote: > On Mon, Nov 16, 2015 at 2:38 AM, Paolo Bonzini wr= ote: >> >> >> On 15/11/2015 03:07, Rob Herring wrote: >>> We generally don't want DT docs to depend on other kernel documentati= on. >> >> 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. >=20 > 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! Fran=E7ois.