Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752623AbbKYVof (ORCPT ); Wed, 25 Nov 2015 16:44:35 -0500 Received: from mail-wm0-f48.google.com ([74.125.82.48]:33229 "EHLO mail-wm0-f48.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751139AbbKYVoc (ORCPT ); Wed, 25 Nov 2015 16:44:32 -0500 From: Pali =?utf-8?q?Roh=C3=A1r?= To: Arnd Bergmann Subject: Re: [PATCH 5/5] arm: boot: store ATAGs structure into DT "/chosen/linux,atags" entry Date: Wed, 25 Nov 2015 22:44:28 +0100 User-Agent: KMail/1.13.7 (Linux/3.13.0-68-generic; KDE/4.14.2; x86_64; ; ) Cc: Tony Lindgren , Pavel Machek , Frank Rowand , "devicetree@vger.kernel.org" , "Russell King - ARM Linux" , Laura Abbott , Grant Likely , Rob Herring , Will Deacon , Ivaylo Dimitrov , Sebastian Reichel , Andreas =?utf-8?q?F=C3=A4rber?= , linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org References: <20150713131902.GH26485@atomide.com> <20151125210310.GT2517@atomide.com> <3245119.krc4KB3uae@wuerfel> In-Reply-To: <3245119.krc4KB3uae@wuerfel> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1602315.3aKPk7AD5o"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <201511252244.28797@pali> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2140 Lines: 56 --nextPart1602315.3aKPk7AD5o Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On Wednesday 25 November 2015 22:29:53 Arnd Bergmann wrote: > On Wednesday 25 November 2015 13:03:10 Tony Lindgren wrote: > > * Arnd Bergmann [151125 11:50]: > > > On Wednesday 25 November 2015 10:16:44 Tony Lindgren wrote: > > > > At least I don't have better solutions in mind. > > >=20 > > > I would be happier if we could restrict this as much as possible > > > to the boards that need it, as an opt-in. That way it doesn't > > > become an ABI for people that don't already rely in this > > > information. How about adding a check the code adds the > > > linux,atags property to do it only for a whitelist of board > > > numbers? > >=20 > > Or populate /proc/atags only for the ones that need it from machine > > specific init_early? >=20 > That would also address my main concern about /proc/atags, but still > leave the atags in /proc/device-tree/chosen/linux,atags, and it would > be bad if someone who currently uses /proc/atags changes their code > to use the other file instead of finding a proper solution. >=20 > Arnd Arnd, my question about proper solution reminds... Proprietary=20 bootloader which cannot be replaced (e.g. it is signed or do unknown=20 magic) provides information to booted kernel via custom specific ATAGs=20 fields. How userspace could properly read those custom information from=20 bootloader? =2D-=20 Pali Roh=C3=A1r pali.rohar@gmail.com --nextPart1602315.3aKPk7AD5o Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iEYEABECAAYFAlZWK7wACgkQi/DJPQPkQ1KDGACfbEg3+2P69BSWI3ZMloVuHtl7 0tQAnRWutvOg9ockxWsG/32s3Wm7P1Xg =F6mX -----END PGP SIGNATURE----- --nextPart1602315.3aKPk7AD5o-- -- 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/