From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?UTF-8?B?QW5kcsOpIFNjaGFsbGVy?= Date: Wed, 04 Feb 2015 20:10:50 +0100 Subject: [U-Boot] Loop Variable through to user space In-Reply-To: <20150203232719.1ac240a0@lilith> References: <54D0C5B8.60800@googlemail.com> <20150203232719.1ac240a0@lilith> Message-ID: <54D26EBA.2010406@googlemail.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Hello Albert, thanks for the information. Do you mean to pass the value using an environment variable to the boot parameter? How would I approach to set up an environment variable in the SPL? Wouldn't it increase the memory footprint such that the SPL wouldn't fit into SRAM anymore? Best, Andr? Am 03.02.15 um 23:27 schrieb Albert ARIBAUD: > Hello Andr?, > > On Tue, 03 Feb 2015 13:57:28 +0100, Andr? Schaller > wrote: >> Hi all, >> >> during the execution of th MLO I create a variable, whose value I want >> to make accessible to user space applications in Android. How can this >> be achieved? >> >> One way would be to write the contents of the variable to external >> memory and let it read by the user space process. However, I would need >> to make sure that during boot no other process is overwriting the address. >> >> Do you know of any other ways? > > Kind of a hack, but maybe you could pass the value somehow through the > kernel boot parameters? I assume that a meaningless parameter does not > affect the kernel but can still be parsed from /proc/cmdline. > >> Best, >> Andr? > > Amicalement, >