[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5abefbed-fd4d-0564-e99c-e17f6a1445b5@synopsys.com>
Date: Tue, 27 Jun 2017 07:25:39 +0300
From: Vineet Gupta <Vineet.Gupta1@...opsys.com>
To: Alexey Brodkin <Alexey.Brodkin@...opsys.com>,
"robh+dt@...nel.org" <robh+dt@...nel.org>
CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"Alexey.Brodkin@...opsys.com" <Alexey.Brodkin@...opsys.com>,
"Eugeniy.Paltsev@...opsys.com" <Eugeniy.Paltsev@...opsys.com>,
"linux-snps-arc@...ts.infradead.org"
<linux-snps-arc@...ts.infradead.org>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
Arnd Bergmann <arnd@...db.de>
Subject: stdout-path (was Re: [PATCH 3/3 v6] ARC: hsdk: initial port for HSDK
board)
On 06/26/2017 07:25 PM, Alexey Brodkin wrote:
>>> +
>>> + chosen {
>>> + bootargs = "earlycon=uart8250,mmio32,0xf0005000,115200n8 console=ttyS0,115200n8 debug print-fatal-signals=1";
>> Use stdout-path for the console. Really, the bootargs should be blank
>> and populated by the bootloader especially debug options.
> Agree but in case of devboards we quite often disable bootloader and
> load Linux image in memory via JTAG. So in that case bootargs make perfect sense IMH
FWIW, I tried this 2 years ago (v4.1 ish) per pestering by Arnd but at the time I
had to add some hacks in early 8250 driver to get this working for ARC.
See,
http://www.spinics.net/lists/linux-serial/msg17742.html
http://www.spinics.net/lists/linux-serial/msg17747.html
We can certainly revisit this now.
-Vineet
Powered by blists - more mailing lists