From mboxrd@z Thu Jan 1 00:00:00 1970 From: Vladimir Pantelic Subject: Re: Request review of device tree documentation Date: Wed, 16 Jun 2010 11:45:00 +0200 Message-ID: <4C189D1C.6050304@nt.tu-darmstadt.de> References: <4C13430B.5000907@firmworks.com> <1276339529.1962.184.camel@pasglop> <1276339684.1962.186.camel@pasglop> <4C13B618.1030006@firmworks.com> <1276383132.1962.195.camel@pasglop> <4C146F18.9030008@firmworks.com> <20100614124438.GF9323@yookeroo> <20100614160201.GD9550@shareable.org> <4C165FD1.6080505@firmworks.com> <4C186AA8.4040709@compulab.co.il> <4C186B7B.1060308@firmworks.com> <4C186C72.2020506@compulab.co.il> <4C187013.5000400@firmworks.com> <4C18738C.4090809@compulab.co.il> <4C187FF0.5020806@firmworks.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4C187FF0.5020806@firmworks.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-arm-kernel-bounces@lists.infradead.org Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=m.gmane.org@lists.infradead.org To: Mitch Bradley Cc: Nicolas Pitre , microblaze-uclinux@itee.uq.edu.au, devicetree-discuss , Jamie Lokier , Grant Likely , linuxppc-dev , Mike Rapoport , Dan Malek , Jeremy Kerr , linux-arm-kernel@lists.infradead.org, David Gibson List-Id: devicetree@vger.kernel.org Mitch Bradley wrote: >> I'm also objecting the step (b) and, fortunately, it's not yet the >> status quo. >> Current U-Boot/kernel implementations I've encountered still do not >> have OS calls to resident HW access routines. But if such calls would >> be allowed, my impression is that SoC vendors would make extensive use >> of them. > > One could argue that a feature that vendors would use extensively is one > that is sorely needed from their point of view. yes, it would free them from writing these pesky linux drivers and getting them into mainline :)