All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Hurley <peter@hurleysoftware.com>
To: Michal Simek <michal.simek@xilinx.com>,
	linux-arm-kernel@lists.infradead.org,
	Arnd Bergmann <arnd@arndb.de>,
	Nicolas Pitre <nicolas.pitre@linaro.org>
Cc: "Sören Brinkmann" <soren.brinkmann@xilinx.com>,
	monstr@monstr.eu, "Jiri Slaby" <jslaby@suse.com>,
	linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>
Subject: Re: [PATCH 2/3] serial: xuartps: Enable OF earlycon support
Date: Thu, 18 Feb 2016 09:20:32 -0800	[thread overview]
Message-ID: <56C5FD60.4090906@hurleysoftware.com> (raw)
In-Reply-To: <56C57A60.4070600@xilinx.com>

On 02/18/2016 12:01 AM, Michal Simek wrote:
> BTW: Is it normal that when earlycon support is enabled that the bootlog
> is copied again? All what was printed before bootconsole [xxx] disabled
> is printed twice.

I think it has to do with the dummy console bug w/ OF.

Masahiro Yamada reported this back with 4.4-rc1 [1] but problem occurs before
then as well.

[1] http://www.gossamer-threads.com/lists/linux/kernel/2313050

> Or is this just bug in our driver?

No.

Regards,
Peter Hurley

WARNING: multiple messages have this Message-ID (diff)
From: peter@hurleysoftware.com (Peter Hurley)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/3] serial: xuartps: Enable OF earlycon support
Date: Thu, 18 Feb 2016 09:20:32 -0800	[thread overview]
Message-ID: <56C5FD60.4090906@hurleysoftware.com> (raw)
In-Reply-To: <56C57A60.4070600@xilinx.com>

On 02/18/2016 12:01 AM, Michal Simek wrote:
> BTW: Is it normal that when earlycon support is enabled that the bootlog
> is copied again? All what was printed before bootconsole [xxx] disabled
> is printed twice.

I think it has to do with the dummy console bug w/ OF.

Masahiro Yamada reported this back with 4.4-rc1 [1] but problem occurs before
then as well.

[1] http://www.gossamer-threads.com/lists/linux/kernel/2313050

> Or is this just bug in our driver?

No.

Regards,
Peter Hurley

  reply	other threads:[~2016-02-18 17:20 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-15 16:05 [PATCH 1/3] ARM: zynq: Move early printk virtual address to vmalloc area Michal Simek
2016-02-15 16:05 ` Michal Simek
2016-02-15 16:05 ` [PATCH 2/3] serial: xuartps: Enable OF earlycon support Michal Simek
2016-02-15 16:05   ` Michal Simek
2016-02-16 11:54   ` Arnd Bergmann
2016-02-16 11:54     ` Arnd Bergmann
2016-02-16 16:33   ` Peter Hurley
2016-02-16 16:33     ` Peter Hurley
2016-02-18  8:01     ` Michal Simek
2016-02-18  8:01       ` Michal Simek
2016-02-18  8:01       ` Michal Simek
2016-02-18 17:20       ` Peter Hurley [this message]
2016-02-18 17:20         ` Peter Hurley
2016-02-15 16:05 ` [PATCH 3/3] ARM: zynq: Use earlycon instead of earlyprintk Michal Simek
2016-02-15 16:05   ` Michal Simek
2016-02-15 16:05   ` Michal Simek
2016-02-16 11:57 ` [PATCH 1/3] ARM: zynq: Move early printk virtual address to vmalloc area Arnd Bergmann
2016-02-16 11:57   ` Arnd Bergmann

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=56C5FD60.4090906@hurleysoftware.com \
    --to=peter@hurleysoftware.com \
    --cc=arnd@arndb.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=jslaby@suse.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=michal.simek@xilinx.com \
    --cc=monstr@monstr.eu \
    --cc=nicolas.pitre@linaro.org \
    --cc=soren.brinkmann@xilinx.com \
    /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.