From: Andre Heider Date: Thu, 27 Aug 2020 16:34:08 +0200 Subject: [PATCH 4/5] arm: mvebu: Espressobin: Define console env In-Reply-To: <20200827102916.d64m43tw4jiqatas@pali> References: <20200824142502.7281-1-pali@kernel.org> <20200824142502.7281-4-pali@kernel.org> <902e3699-095c-032f-f67a-28c070293e91@gmail.com> <20200826133140.ih77mzeozyi2ua7o@pali> <20200826141020.4pat5oulm7t3pdpm@pali> <20200826151048.7synjjiouuok2bqt@pali> <0bea3303-858c-7a4d-bd9e-6f7334f5db59@gmail.com> <20200827102916.d64m43tw4jiqatas@pali> Message-ID: <0d895fe5-c481-c5df-50c7-637fc2bd866b@gmail.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On 27/08/2020 12:29, Pali Roh?r wrote: > On Thursday 27 August 2020 06:51:57 Andre Heider wrote: >> On the other hand, check "git grep 'console='". So why not just add the >> earlycon to bootargs directly so it works everywhere? > > The only useful thing about CONFIG_DEFAULT_CONSOLE and ${console} env is > to propagate earlycon argument to kernel. As console kernel argument is > already set via chosen/stdout in DTS. > > Setting earlycon directly to ${bootargs} env does not work as basically > all distribution scripts set/overwrite ${bootargs} on their own. > > So we need to store earlycon argument into some other uboot env and then > teach these distribution scripts to append that new uboot env into their > bootargs... > > Or is there any other way? I don't know the answer to that, but as we've seen with $console, it's hard to get everyone on the same page. But maybe it's not worth the hassle, since console works, and earlycon may only be interesting to ppl who know how to enable it anyway. Regards, Andre