public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: afaerber@suse.de (Andreas Färber)
To: linux-arm-kernel@lists.infradead.org
Subject: No output on console despite ignore_loglevel earlyprintk
Date: Fri, 3 Mar 2017 18:17:47 +0100	[thread overview]
Message-ID: <3fc43a98-71b1-03df-6809-726230dc27d1@suse.de> (raw)
In-Reply-To: <0e7d14d5-d087-cba3-1792-fb0abf1142ef@sigmadesigns.com>

Am 03.03.2017 um 18:07 schrieb Marc Gonzalez:
> On 03/03/2017 17:59, Andreas F?rber wrote:
>> Am 03.03.2017 um 17:42 schrieb Marc Gonzalez:
>>> 	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 = &eth0;
> 	};
> 
> Should I be using serial0 everywhere?
> (I thought I could call it "foo", if I wanted.)

Most serial drivers call of_alias_get_id() to retrieve the index - feel
free to add some debug output to see whether "serial" and "serial0"
behave the same, I haven't tested - literal "foo" will definitely behave
differently since the drivers check for "serial".

Regards,
Andreas

-- 
SUSE Linux GmbH, Maxfeldstr. 5, 90409 N?rnberg, Germany
GF: Felix Imend?rffer, Jane Smithard, Graham Norton
HRB 21284 (AG N?rnberg)

  reply	other threads:[~2017-03-03 17:17 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 [this message]
2017-03-03 17:18     ` Russell King - ARM Linux

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=3fc43a98-71b1-03df-6809-726230dc27d1@suse.de \
    --to=afaerber@suse.de \
    --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