From: Ian Campbell <Ian.Campbell@citrix.com>
To: xen-devel <xen-devel@lists.xen.org>
Cc: Julien Grall <julien.grall@linaro.org>, Tim Deegan <tim@xen.org>,
Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>
Subject: [PATCH v2 0/4] dt-uart: cleanups, bugfixes and /chosen/stdout-path support
Date: Thu, 8 Jan 2015 11:53:29 +0000 [thread overview]
Message-ID: <1420718009.19787.44.camel@citrix.com> (raw)
The two main changes here are:
* a bugfix to deal with DT paths which contain a common, which are
perfectly valid and quite common.
* support for the /chosen/stdout-path device tree property, which
allows Xen to find a boot console without manual configuration
if presented with a suitable device tree. Juno and Seattle both
contain the node in the dt supplied with the upstream Linux
kernel (not sure about their factory kernel), as do a bunch of
non-virt capable arm devices, but with stdout-path support being
added to Linux in v3.19-rc1 I expect that number will soon grow.
I think "dt-uart: use ':' as separator between path and options"
should be a candidate for stable backport.
Since last time: removed back compat support for ',', constify, warn if
stdout-path is truncated.
next reply other threads:[~2015-01-08 11:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-08 11:53 Ian Campbell [this message]
2015-01-08 11:53 ` [PATCH v2 1/4] dt-uart: add an emacs magic block Ian Campbell
2015-01-08 11:53 ` [PATCH v2 2/4] dt-uart: Clarify log messages at init time Ian Campbell
2015-01-08 11:53 ` [PATCH v2 3/4] dt-uart: use ':' as separator between path and options Ian Campbell
2015-01-08 12:26 ` Julien Grall
2015-01-08 12:29 ` Ian Campbell
2015-01-08 11:53 ` [PATCH v2 4/4] dt-uart: support /chosen/stdout-path property Ian Campbell
2015-01-08 13:15 ` Julien Grall
2015-01-08 13:22 ` Ian Campbell
2015-01-08 13:30 ` Julien Grall
2015-01-12 15:22 ` Ian Campbell
2015-01-12 15:24 ` Julien Grall
2015-01-12 16:31 ` Ian Campbell
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=1420718009.19787.44.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=Stefano.Stabellini@eu.citrix.com \
--cc=julien.grall@linaro.org \
--cc=tim@xen.org \
--cc=xen-devel@lists.xen.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.