From: Ard Biesheuvel <ard.biesheuvel@linaro.org>
To: linux-efi@vger.kernel.org
Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>,
graeme.gregory@linaro.org, linux-doc@vger.kernel.org,
pjones@redhat.com, corbet@lwn.net, agraf@suse.de,
leif.lindholm@linaro.org, mingo@redhat.com, tglx@linutronix.de,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] efi: arm: add support for earlycon on EFI framebuffer
Date: Fri, 25 Jan 2019 17:18:04 +0100 [thread overview]
Message-ID: <20190125161806.13472-1-ard.biesheuvel@linaro.org> (raw)
Repurpose the existing EFI earlyprintk code to implement support for
'earlycon=efi' for arm64 systems, allowing the graphical console
to be used instead of the serial port for early debug output.
Ard Biesheuvel (2):
efi: x86: move EFI earlyprintk code to shared location
efi: arm64: Enable earlycon for the GOP framebuffer
Documentation/admin-guide/kernel-parameters.txt | 9 ++-
arch/arm64/include/asm/efi.h | 6 ++
arch/x86/Kconfig.debug | 2 +-
arch/x86/include/asm/efi.h | 6 ++
arch/x86/platform/efi/Makefile | 1 -
drivers/firmware/efi/Kconfig | 5 ++
drivers/firmware/efi/Makefile | 1 +
arch/x86/platform/efi/early_printk.c => drivers/firmware/efi/earlycon.c | 62 ++++++++++++++------
8 files changed, 70 insertions(+), 22 deletions(-)
rename arch/x86/platform/efi/early_printk.c => drivers/firmware/efi/earlycon.c (76%)
--
2.20.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2019-01-25 16:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-25 16:18 Ard Biesheuvel [this message]
2019-01-25 16:18 ` [PATCH 1/2] efi: x86: move EFI earlyprintk code to shared location Ard Biesheuvel
2019-01-25 16:18 ` [PATCH 2/2] efi: arm64: Enable earlycon for the GOP framebuffer Ard Biesheuvel
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=20190125161806.13472-1-ard.biesheuvel@linaro.org \
--to=ard.biesheuvel@linaro.org \
--cc=agraf@suse.de \
--cc=corbet@lwn.net \
--cc=graeme.gregory@linaro.org \
--cc=leif.lindholm@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-efi@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pjones@redhat.com \
--cc=tglx@linutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).