From: Vineet.Gupta1@synopsys.com (Vineet Gupta)
To: linux-snps-arc@lists.infradead.org
Subject: stdout-path (was Re: [PATCH 3/3 v6] ARC: hsdk: initial port for HSDK board)
Date: Tue, 27 Jun 2017 07:25:39 +0300 [thread overview]
Message-ID: <5abefbed-fd4d-0564-e99c-e17f6a1445b5@synopsys.com> (raw)
In-Reply-To: <1498494334.28955.58.camel@synopsys.com>
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
WARNING: multiple messages have this Message-ID (diff)
From: Vineet Gupta <Vineet.Gupta1@synopsys.com>
To: "robh+dt@kernel.org" <robh+dt@kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Alexey.Brodkin@synopsys.com" <Alexey.Brodkin@synopsys.com>,
"Eugeniy.Paltsev@synopsys.com" <Eugeniy.Paltsev@synopsys.com>,
"linux-snps-arc@lists.infradead.org"
<linux-snps-arc@lists.infradead.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Arnd Bergmann <arnd@arndb.de>
Subject: stdout-path (was Re: [PATCH 3/3 v6] ARC: hsdk: initial port for HSDK board)
Date: Tue, 27 Jun 2017 07:25:39 +0300 [thread overview]
Message-ID: <5abefbed-fd4d-0564-e99c-e17f6a1445b5@synopsys.com> (raw)
In-Reply-To: <1498494334.28955.58.camel@synopsys.com>
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
WARNING: multiple messages have this Message-ID (diff)
From: Vineet Gupta <Vineet.Gupta1@synopsys.com>
To: Alexey Brodkin <Alexey.Brodkin@synopsys.com>,
"robh+dt@kernel.org" <robh+dt@kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Alexey.Brodkin@synopsys.com" <Alexey.Brodkin@synopsys.com>,
"Eugeniy.Paltsev@synopsys.com" <Eugeniy.Paltsev@synopsys.com>,
"linux-snps-arc@lists.infradead.org"
<linux-snps-arc@lists.infradead.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Arnd Bergmann <arnd@arndb.de>
Subject: stdout-path (was Re: [PATCH 3/3 v6] ARC: hsdk: initial port for HSDK board)
Date: Tue, 27 Jun 2017 07:25:39 +0300 [thread overview]
Message-ID: <5abefbed-fd4d-0564-e99c-e17f6a1445b5@synopsys.com> (raw)
In-Reply-To: <1498494334.28955.58.camel@synopsys.com>
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
next prev parent reply other threads:[~2017-06-27 4:25 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-26 15:11 [PATCH 0/3 v6] hsdk: initial port for HSDK board Eugeniy Paltsev
2017-06-26 15:11 ` Eugeniy Paltsev
2017-06-26 15:11 ` Eugeniy Paltsev
2017-06-26 15:11 ` [PATCH 1/3 v6] ARC: Set IO-coherency aperture base to LINUX_LINK_BASE Eugeniy Paltsev
2017-06-26 15:11 ` Eugeniy Paltsev
2017-06-26 15:11 ` Eugeniy Paltsev
2017-06-26 15:11 ` [PATCH 2/3 v6] ARC: Decouple linux kernel memory address and link address Eugeniy Paltsev
2017-06-26 15:11 ` Eugeniy Paltsev
2017-06-26 15:11 ` Eugeniy Paltsev
2017-06-26 15:11 ` [PATCH 3/3 v6] ARC: hsdk: initial port for HSDK board Eugeniy Paltsev
2017-06-26 15:11 ` Eugeniy Paltsev
2017-06-26 15:11 ` Eugeniy Paltsev
2017-06-26 15:51 ` Rob Herring
2017-06-26 15:51 ` Rob Herring
2017-06-26 15:51 ` Rob Herring
2017-06-26 16:25 ` Alexey Brodkin
2017-06-26 16:25 ` Alexey Brodkin
2017-06-27 4:25 ` Vineet Gupta [this message]
2017-06-27 4:25 ` stdout-path (was Re: [PATCH 3/3 v6] ARC: hsdk: initial port for HSDK board) Vineet Gupta
2017-06-27 4:25 ` Vineet Gupta
2017-06-28 22:50 ` [PATCH 3/3 v6] ARC: hsdk: initial port for HSDK board Rob Herring
2017-06-28 22:50 ` Rob Herring
2017-06-28 22:50 ` Rob Herring
2017-06-29 16:39 ` Eugeniy Paltsev
2017-06-29 16:39 ` Eugeniy Paltsev
2017-06-29 16:39 ` Eugeniy Paltsev
2017-06-29 7:27 ` Vineet Gupta
2017-06-29 7:27 ` Vineet Gupta
2017-06-29 7:27 ` Vineet Gupta
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5abefbed-fd4d-0564-e99c-e17f6a1445b5@synopsys.com \
--to=vineet.gupta1@synopsys.com \
--cc=linux-snps-arc@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.