From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753073AbbK1VCf (ORCPT ); Sat, 28 Nov 2015 16:02:35 -0500 Received: from mail-pa0-f68.google.com ([209.85.220.68]:33513 "EHLO mail-pa0-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752787AbbK1VCb (ORCPT ); Sat, 28 Nov 2015 16:02:31 -0500 Message-ID: <565A1665.2060504@gmail.com> Date: Sat, 28 Nov 2015 13:02:29 -0800 From: Frank Rowand Reply-To: frowand.list@gmail.com User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 To: Nicolas Pitre CC: Russell King - ARM Linux , Arnd Bergmann , linux-arm-kernel@lists.infradead.org, =?ISO-8859-1?Q?Pali_Roh=E1r?= , "devicetree@vger.kernel.org" , Ivaylo Dimitrov , Laura Abbott , Tony Lindgren , Sebastian Reichel , Will Deacon , linux-kernel@vger.kernel.org, Rob Herring , Pavel Machek , Grant Likely , linux-omap@vger.kernel.org, =?ISO-8859-1?Q?Andreas_F=E4rber?= , frowand.list@gmail.com Subject: Re: [PATCH 5/5] arm: boot: store ATAGs structure into DT "/chosen/linux,atags" entry References: <20150713131902.GH26485@atomide.com> <20151127132722.GA30871@n2100.arm.linux.org.uk> <20151127195148.GB30871@n2100.arm.linux.org.uk> <11537945.4HX4Y84tjV@wuerfel> <20151128123328.GC30871@n2100.arm.linux.org.uk> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 11/28/2015 9:34 AM, Nicolas Pitre wrote: > On Sat, 28 Nov 2015, Russell King - ARM Linux wrote: > >> On Fri, Nov 27, 2015 at 06:28:50PM -0500, Nicolas Pitre wrote: >>> On Fri, 27 Nov 2015, Arnd Bergmann wrote: >>> >>>> I don't mind creating the /proc/atags compatibility hack from the kernel >>>> for a DT based N700 kernel, as long as we limit it as much as we can >>>> to the machines that need it. Leaving a board file for the N700 in place >>>> that contains the procfs code (and not much more) seems reasonable >>>> here, as we are talking about a board specific hack and the whole point >>>> appears to be running unmodified user space. >>>> >>>> Regarding how to get the data into the kernel in the first place, my >>>> preferred choice would still be to have an intermediate bootloader >>>> such as pxa-impedance-matcher, but I won't complain if others are >>>> happy enough about putting it into the ATAGS compat code we already >>>> have, as long as it's limited to the boards we know need it. >>> >>> Assuming you have a N700 board file for special procfs code, then why >>> not getting at the atags in memory where the bootloader has put them >>> directly from that same board file? This way it'll really be limited to >>> the board we know needs it and the special exception will be contained >>> to that one file. Amongst the machine specific hooks, there is one that >>> gets invoked early during boot before those atags are overwritten. >> >> I've already suggested that. > > Good. And Arnd likes the idea too. So we might be converging at last > which is a good thing. It makes me happy too. -Frank