From: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
To: Paul Burton <paul.burton@imgtec.com>
Cc: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
Larry Finger <Larry.Finger@lwfinger.net>,
Michael Ellerman <mpe@ellerman.id.au>,
Andreas Schwab <schwab@linux-m68k.org>,
Andrew Morton <akpm@linux-foundation.org>,
Borislav Petkov <bp@suse.de>, Petr Mladek <pmladek@suse.com>,
Tejun Heo <tj@kernel.org>,
linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v3] console: use first console if stdout-path device doesn't appear
Date: Sat, 5 Nov 2016 00:44:51 +0900 [thread overview]
Message-ID: <20161104153852.GA422@swordfish> (raw)
In-Reply-To: <2317993.vxfTP7Yo3N@np-p-burton>
Hi Paul,
On (11/03/16 21:17), Paul Burton wrote:
> > [..]
> > > + * The device tree stdout-path chosen node property was
> > > + * specified so we don't want to enable the first
> > > + * registered console just now in order to give the
> > > + * device indicated by stdout-path a chance to be
> > > + * registered first. Do however keep track of the
> > > + * first console we see so that we can fall back to
> > > + * using it if we don't see the desired device, either
> > > + * because stdout-path isn't valid, or because we have
> > > + * no driver for the device or our driver doesn't call
> > > + * of_console_check(). See printk_late_init() for this
> > > + * fallback.
> >
> > if the path is not valid then correct the path. no?
>
> ...but what if the path is valid and we simply don't have a driver for the
> device it references? As I said in that comment we may not have a driver at
> all.
well, I suppose, in this case normally one would go and enable the
missing .config option. no?
-ss
next prev parent reply other threads:[~2016-11-04 15:46 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-09 12:50 [PATCH] console: Don't prefer first registered if DT specifies stdout-path Paul Burton
2016-08-09 12:50 ` Paul Burton
2016-08-09 12:50 ` Paul Burton
2016-08-09 14:12 ` kbuild test robot
2016-08-09 14:12 ` kbuild test robot
2016-08-09 14:12 ` kbuild test robot
2016-08-09 15:10 ` kbuild test robot
2016-08-09 15:10 ` kbuild test robot
2016-08-09 15:19 ` [PATCH v2] " Paul Burton
2016-08-09 15:19 ` Paul Burton
2016-08-09 21:57 ` Andrew Morton
2016-08-09 21:57 ` Andrew Morton
2016-08-09 21:57 ` Andrew Morton
2016-10-16 18:07 ` Andreas Schwab
2016-10-16 18:07 ` Andreas Schwab
2016-10-16 18:07 ` Andreas Schwab
2016-10-17 10:33 ` Paul Burton
2016-10-17 10:33 ` Paul Burton
2016-10-17 17:39 ` Andreas Schwab
2016-10-17 17:39 ` Andreas Schwab
2016-10-17 17:39 ` Andreas Schwab
2016-10-18 9:18 ` [PATCH] console: use first console if stdout-path device doesn't appear Paul Burton
2016-10-18 18:58 ` Andreas Schwab
2016-10-30 9:46 ` Andreas Schwab
2016-10-31 5:28 ` Michael Ellerman
2016-10-31 12:14 ` [PATCH v2] " Paul Burton
2016-10-31 15:50 ` Paul Burton
2016-10-31 19:21 ` Larry Finger
2016-10-31 23:09 ` Sergey Senozhatsky
2016-10-31 23:31 ` Larry Finger
2016-11-03 12:57 ` [PATCH v3] " Paul Burton
2016-11-03 17:40 ` Sergey Senozhatsky
2016-11-03 21:17 ` Paul Burton
2016-11-04 15:44 ` Sergey Senozhatsky [this message]
2016-11-04 8:05 ` Andreas Schwab
2016-11-07 8:27 ` Michael Ellerman
2016-11-07 9:18 ` Paul Burton
2016-11-07 15:26 ` Larry Finger
2016-11-07 17:21 ` Paul Burton
2016-11-07 18:27 ` Larry Finger
2016-11-08 13:21 ` revert 05fd007e46296afb (was: [PATCH v3] console: use first console if stdout-path device doesn't appear) Sergey Senozhatsky
2016-11-03 13:04 ` [PATCH v2] console: use first console if stdout-path device doesn't appear Paul Burton
2016-11-01 4:39 ` Michael Ellerman
2016-10-31 15:58 ` Larry Finger
2016-10-31 12:23 ` [PATCH] " Paul Burton
2016-10-18 9:21 ` [PATCH v2] console: Don't prefer first registered if DT specifies stdout-path Paul Burton
2016-10-18 9:21 ` Paul Burton
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=20161104153852.GA422@swordfish \
--to=sergey.senozhatsky@gmail.com \
--cc=Larry.Finger@lwfinger.net \
--cc=akpm@linux-foundation.org \
--cc=bp@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=paul.burton@imgtec.com \
--cc=pmladek@suse.com \
--cc=schwab@linux-m68k.org \
--cc=tj@kernel.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.