All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sudeep Holla <sudeep.holla-5wv7dgnIgG8@public.gmane.org>
To: Peter Hurley
	<peter-WaGBZJeGNqdsbIuE7sb01tBPR1lH4CV8@public.gmane.org>,
	Masahiro Yamada
	<yamada.masahiro-uWyLwvC0a2jby3iVrkZq2A@public.gmane.org>,
	devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-arm-kernel
	<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>,
	linux-serial-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: Sudeep Holla <sudeep.holla-5wv7dgnIgG8@public.gmane.org>
Subject: Re: Which is better to specify console, "console= " or "stdout-path" ?
Date: Wed, 21 Oct 2015 14:06:14 +0100	[thread overview]
Message-ID: <56278DC6.8090601@arm.com> (raw)
In-Reply-To: <56278CF3.9010400-WaGBZJeGNqdsbIuE7sb01tBPR1lH4CV8@public.gmane.org>



On 21/10/15 14:02, Peter Hurley wrote:
> On 10/21/2015 08:54 AM, Sudeep Holla wrote:
>> On 21/10/15 13:46, Peter Hurley wrote:

[..]

>>> Be aware that options specified via /chosen/stdout-path are
>>> currently ignored by earlycon. There were some hiccups getting the
>>> initial support upstream; when 4.4 hits mainline, I'll resubmit
>>> my series that implements the of_serial i/o properties and
>>> options passthrough to earlycon setup.
>>>
>>
>> Yes I am aware of that.
>
> The others to which my email was addressed might not know that.
>

True, good that you pointed it out.

>> IIUC it's in -next now and works fine for me.
>
> Well, the fix in -next doesn't actually do anything wrt earlycon baud
> rate; those changes were part of a larger series that depends on
> the fix in -next.
>

Ah ok.

-- 
Regards,
Sudeep
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

WARNING: multiple messages have this Message-ID (diff)
From: sudeep.holla@arm.com (Sudeep Holla)
To: linux-arm-kernel@lists.infradead.org
Subject: Which is better to specify console, "console= " or "stdout-path" ?
Date: Wed, 21 Oct 2015 14:06:14 +0100	[thread overview]
Message-ID: <56278DC6.8090601@arm.com> (raw)
In-Reply-To: <56278CF3.9010400@hurleysoftware.com>



On 21/10/15 14:02, Peter Hurley wrote:
> On 10/21/2015 08:54 AM, Sudeep Holla wrote:
>> On 21/10/15 13:46, Peter Hurley wrote:

[..]

>>> Be aware that options specified via /chosen/stdout-path are
>>> currently ignored by earlycon. There were some hiccups getting the
>>> initial support upstream; when 4.4 hits mainline, I'll resubmit
>>> my series that implements the of_serial i/o properties and
>>> options passthrough to earlycon setup.
>>>
>>
>> Yes I am aware of that.
>
> The others to which my email was addressed might not know that.
>

True, good that you pointed it out.

>> IIUC it's in -next now and works fine for me.
>
> Well, the fix in -next doesn't actually do anything wrt earlycon baud
> rate; those changes were part of a larger series that depends on
> the fix in -next.
>

Ah ok.

-- 
Regards,
Sudeep

  parent reply	other threads:[~2015-10-21 13:06 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-21  5:09 Which is better to specify console, "console= " or "stdout-path" ? Masahiro Yamada
2015-10-21  5:09 ` Masahiro Yamada
     [not found] ` <CAK7LNAS9uBJ1cVmGBKae3W0tk8Siu1yeXOaeN6Kz11cksMqtsg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-10-21  7:43   ` Arnd Bergmann
2015-10-21  7:43     ` Arnd Bergmann
2015-10-21  8:58   ` Sudeep Holla
2015-10-21  8:58     ` Sudeep Holla
     [not found]     ` <562753A6.3070107-5wv7dgnIgG8@public.gmane.org>
2015-10-21 12:46       ` Peter Hurley
2015-10-21 12:46         ` Peter Hurley
     [not found]         ` <56278911.9050704-WaGBZJeGNqdsbIuE7sb01tBPR1lH4CV8@public.gmane.org>
2015-10-21 12:54           ` Sudeep Holla
2015-10-21 12:54             ` Sudeep Holla
     [not found]             ` <56278AFD.8000505-5wv7dgnIgG8@public.gmane.org>
2015-10-21 13:02               ` Peter Hurley
2015-10-21 13:02                 ` Peter Hurley
     [not found]                 ` <56278CF3.9010400-WaGBZJeGNqdsbIuE7sb01tBPR1lH4CV8@public.gmane.org>
2015-10-21 13:06                   ` Sudeep Holla [this message]
2015-10-21 13:06                     ` Sudeep Holla
2015-10-21 15:38           ` Masahiro Yamada
2015-10-21 15:38             ` Masahiro Yamada
     [not found]             ` <CAK7LNAQ_+_9K-y7bmpdGwcH2u4uqJhJhON1Ew4OvzSSa-amyvw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-10-21 16:26               ` Peter Hurley
2015-10-21 16:26                 ` Peter Hurley
     [not found]                 ` <5627BCBC.5040701-WaGBZJeGNqdsbIuE7sb01tBPR1lH4CV8@public.gmane.org>
2015-10-22  4:20                   ` Masahiro Yamada
2015-10-22  4:20                     ` Masahiro Yamada
     [not found]                     ` <CAK7LNASqjd_Xf53WKa=Ogesf80HQzEoKEyVtw-BMh7JF=jq+xQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-10-28 16:00                       ` Peter Hurley
2015-10-28 16:00                         ` Peter Hurley

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=56278DC6.8090601@arm.com \
    --to=sudeep.holla-5wv7dgnigg8@public.gmane.org \
    --cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
    --cc=linux-serial-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=peter-WaGBZJeGNqdsbIuE7sb01tBPR1lH4CV8@public.gmane.org \
    --cc=yamada.masahiro-uWyLwvC0a2jby3iVrkZq2A@public.gmane.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.