From: linux@armlinux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: No output on console despite ignore_loglevel earlyprintk
Date: Fri, 3 Mar 2017 17:18:39 +0000 [thread overview]
Message-ID: <20170303171839.GP21222@n2100.armlinux.org.uk> (raw)
In-Reply-To: <0e7d14d5-d087-cba3-1792-fb0abf1142ef@sigmadesigns.com>
On Fri, Mar 03, 2017 at 06:07:39PM +0100, Marc Gonzalez wrote:
> On 03/03/2017 17:59, Andreas F?rber wrote:
> >> I suppose this is related to my DT description?
> >>
> >> chosen {
> >> stdout-path = "serial:115200n8";
> >> };
> >>
> >> Isn't stdout-path = "serial:115200n8" supposed to be equivalent to
> >> console=ttyS0,115200 ?
> >
> > First of all, that should probably be serial0, and it needs to be
> > defined as an alias. In my case that's a given.
>
> My DT root node contains
>
> aliases {
> serial = &uart;
> eth0 = ð0;
> };
>
> Should I be using serial0 everywhere?
> (I thought I could call it "foo", if I wanted.)
Correct, stdout-path contains the node name - please see
Documentation/devicetree/bindings/chosen.txt for the definitive
information.
Setting the early console has no effect on the eventual system
console that the kernel chooses. See these files:
drivers/of/fdt.c
drivers/tty/serial/earlycon.c
--
RMK's Patch system: http://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.
prev parent reply other threads:[~2017-03-03 17:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-03 16:42 No output on console despite ignore_loglevel earlyprintk Marc Gonzalez
2017-03-03 16:55 ` Russell King - ARM Linux
2017-03-03 17:26 ` Andreas Färber
2017-03-03 17:46 ` Russell King - ARM Linux
2017-04-05 14:02 ` Marc Gonzalez
2017-04-05 16:37 ` Marc Gonzalez
2017-03-03 16:59 ` Andreas Färber
2017-03-03 17:07 ` Marc Gonzalez
2017-03-03 17:17 ` Andreas Färber
2017-03-03 17:18 ` Russell King - ARM Linux [this message]
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=20170303171839.GP21222@n2100.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=linux-arm-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox