From: martin.blumenstingl@googlemail.com (Martin Blumenstingl)
To: linus-amlogic@lists.infradead.org
Subject: [PATCH 0/3] 32-bit Meson: add missing /chosen/stdout-path
Date: Sun, 28 Oct 2018 15:03:40 +0100 [thread overview]
Message-ID: <20181028140343.1071-1-martin.blumenstingl@googlemail.com> (raw)
Some boards don't have the /chosen/stdout-path property yet. Support
for these boards is far from being complete and I don't have any of
those for testing. Whenever someone reports an issue with one of these
boards I would like an output with the "earlycon" kernel argument.
However, this only works when the board sets the /chosen/stdout-path
property.
None of these were tested manually, but since it's the same for all
existing (32-bit and 64-bit) boards it's safe to assume that this will
work.
Martin Blumenstingl (3):
ARM: dts: meson6: atv1200: add the /chosen/stdout-path property
ARM: dts: meson8: minix-neo-x8: add the /chosen/stdout-path property
ARM: dts: meson8b: mxq: add the /chosen/stdout-path property
arch/arm/boot/dts/meson6-atv1200.dts | 4 ++++
arch/arm/boot/dts/meson8-minix-neo-x8.dts | 4 ++++
arch/arm/boot/dts/meson8b-mxq.dts | 4 ++++
3 files changed, 12 insertions(+)
--
2.19.1
next reply other threads:[~2018-10-28 14:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-28 14:03 Martin Blumenstingl [this message]
2018-10-28 14:03 ` [PATCH 1/3] ARM: dts: meson6: atv1200: add the /chosen/stdout-path property Martin Blumenstingl
2018-11-08 13:30 ` Neil Armstrong
2018-10-28 14:03 ` [PATCH 2/3] ARM: dts: meson8: minix-neo-x8: " Martin Blumenstingl
2018-11-08 13:30 ` Neil Armstrong
2018-10-28 14:03 ` [PATCH 3/3] ARM: dts: meson8b: mxq: " Martin Blumenstingl
2018-11-08 13:30 ` Neil Armstrong
2018-11-15 19:43 ` [PATCH 0/3] 32-bit Meson: add missing /chosen/stdout-path Kevin Hilman
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=20181028140343.1071-1-martin.blumenstingl@googlemail.com \
--to=martin.blumenstingl@googlemail.com \
--cc=linus-amlogic@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
all inboxes | Powered by JetHome®