Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752951AbbKYVvr (ORCPT ); Wed, 25 Nov 2015 16:51:47 -0500 Received: from mout.kundenserver.de ([212.227.126.131]:53210 "EHLO mout.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752907AbbKYVvm convert rfc822-to-8bit (ORCPT ); Wed, 25 Nov 2015 16:51:42 -0500 From: Arnd Bergmann To: Pali =?ISO-8859-1?Q?Roh=E1r?= 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 =?ISO-8859-1?Q?F=E4rber?= , linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org Subject: Re: [PATCH 5/5] arm: boot: store ATAGs structure into DT "/chosen/linux,atags" entry Date: Wed, 25 Nov 2015 22:51 +0100 Message-ID: <17689711.DsQsCiDFAN@wuerfel> User-Agent: KMail/4.11.5 (Linux/3.16.0-10-generic; KDE/4.11.5; x86_64; ; ) In-Reply-To: <201511252244.28797@pali> References: <20150713131902.GH26485@atomide.com> <3245119.krc4KB3uae@wuerfel> <201511252244.28797@pali> MIME-Version: 1.0 Content-Transfer-Encoding: 8BIT Content-Type: text/plain; charset="iso-8859-1" X-Provags-ID: V03:K0:iQdheDj8Ydp/GV8FAgoPiwrj273FvEsybk1N5wc2igl4KYrH6n4 uASdAVYdzwafJCbhSpIuJ6oGadySlwGgCJs2cuwR5PfAhVEg7ghAN/CUt4nqFTQBNOT1vlY lcYZSmImvKudmsklIH72GJ08kSCaY6mkA3QzyE8Hb2f4bZxNefImltMnkUi326TmpDnL7qG vK5kaaEGWzGVUkbuiG6AA== X-UI-Out-Filterresults: notjunk:1;V01:K0:Egh9OXWbNUM=:6Vrn7wEInTTPBdBdAUPTI1 vvJiBTokyp27m424p+gyKVtpWEj3rO7JGcPkJ0K6HSQ5jwSOnyjudbGGkLkIgrN3wSdpT0+I7 4xo+2GDfj1WiJogUy2Q5csJLfOFQh7uIRivmKWxnuI4XJx93GRZDDqIdQh6AXbsUwlp8QAqS9 +NDulB97xtmFh8YRpLFaNCmsgunQMyDlIWXqzOdBv1NjXOvQCU/w2OlGF2ajHFh/luIIu5mP+ QiWpopkaO0ELew7gA2Z8hrfm+QACjdZg+ndHxqXHeeYf7dQIWDZnL5LoKntV8GKZAbpuIfZwG JcIfcen/LJRqmsTiwZaAS6xGISi+lJF7emmDk0As5n9IxcJrIy5ykuTYtU+eCSNO/iBUhMOQq pK8ydlyRpAtBHjlbtQB28GJ/ziaQXbVIJcS6KYhOCE/RI4FVfnmSwMOMrA0GhSLJd4UNOkdaV +ipaRgt8ILQeyv0X/we5Rt2FVZZpDv+/MBJ0OHxqOCLlWKXJnCHPWQ3zJlP8z/FpjP1mKcpQt hcx8HsukApQQPXWviQnmInzG0u9qHbjWbZGzb+A10LD7lXM+gdH/B1HJkFMILKMCjFkBW7S4e i1UA9kpy2xLm49Lkhj0WWL27JG+PMS3kVi+DUQyPThFKKneWVSqjAoeQEjt/Qduu5aQkbtXWW tSFgaOx1D6XoAaGAvQJWcPHXLTBYEcYjHYQqrNU9NDJrUaGbrSqEqdYc9yLhzah4chMPCoA3g LYILah4NYPw7I4IM Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1085 Lines: 24 On Wednesday 25 November 2015 22:44:28 Pali Roh?r wrote: > > Arnd, my question about proper solution reminds... Proprietary > bootloader which cannot be replaced (e.g. it is signed or do unknown > magic) provides information to booted kernel via custom specific ATAGs > fields. How userspace could properly read those custom information from > bootloader? The typical solution for nonstandard bootloaders is to have a boot wrapper like the one from https://github.com/zonque/pxa-impedance-matcher that translates whatever information we have at the bootloader level into DT properties. As I understand, the reason we are not doing that here is that we also have proprietary user space that we can't fix to look in a different place, i.e. the interface is between the bootloader and some user binary, not bootloader to kernel. Arnd -- 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/