linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matt Fleming <matt@console-pimps.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Ingo Molnar <mingo@kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] EFI changes
Date: Sun, 27 Oct 2013 21:48:15 +0000	[thread overview]
Message-ID: <20131027214815.GH1982@console-pimps.org> (raw)

Guys, do you think we could get the EFI earlyprintk support into the
'x86/efi' branch for the upcoming merge window? I know it's quite late
in the game but since it's a new feature it shouldn't introduce any kind
of regression and is a much needed feature.

The following changes since commit c158c3bf59951bbb44bd7ccca9e6665dfd1617c5:

  boot, efi: Remove redundant memset() (2013-10-04 20:07:47 +0100)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/mfleming/efi.git tags/efi-next

for you to fetch changes up to 32c9e70fc3912c3b9c7d53ce016960ce99ff93d4:

  x86/efi: Add EFI framebuffer earlyprintk support (2013-10-27 21:18:48 +0000)

----------------------------------------------------------------
 * Add support for earlyprintk=efi which uses the EFI framebuffer. Very
   useful for debugging boot issues.

----------------------------------------------------------------
Matt Fleming (2):
      efi: Add asm-generic/efi.h for non-x86
      x86/efi: Add EFI framebuffer earlyprintk support

 Documentation/kernel-parameters.txt  |   8 +-
 arch/ia64/include/asm/efi.h          |   6 ++
 arch/x86/Kconfig.debug               |   9 ++
 arch/x86/boot/compressed/eboot.c     |   1 -
 arch/x86/include/asm/efi.h           |  12 +++
 arch/x86/kernel/early_printk.c       |   6 ++
 arch/x86/kernel/setup.c              |   1 -
 arch/x86/platform/efi/Makefile       |   1 +
 arch/x86/platform/efi/early_printk.c | 191 +++++++++++++++++++++++++++++++++++
 arch/x86/platform/efi/efi.c          |   1 -
 arch/x86/platform/efi/efi_32.c       |   1 -
 arch/x86/platform/efi/efi_64.c       |   1 -
 arch/x86/platform/uv/bios_uv.c       |   1 -
 include/asm-generic/efi.h            |  17 ++++
 include/linux/efi.h                  |  31 +-----
 15 files changed, 249 insertions(+), 38 deletions(-)
 create mode 100644 arch/ia64/include/asm/efi.h
 create mode 100644 arch/x86/platform/efi/early_printk.c
 create mode 100644 include/asm-generic/efi.h

-- 
Matt Fleming, Intel Open Source Technology Center

             reply	other threads:[~2013-10-27 21:48 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-27 21:48 Matt Fleming [this message]
2013-10-28 11:17 ` [GIT PULL] EFI changes Ingo Molnar
2013-10-28 11:49   ` Matt Fleming
2013-10-28 11:50     ` Ingo Molnar
  -- strict thread matches above, loose matches on Subject: below --
2013-10-29  8:18 Matt Fleming
2013-10-28 12:35 Matt Fleming
2013-10-28 13:44 ` Ingo Molnar
2013-10-28 15:52   ` Matt Fleming
2013-10-28 15:55     ` Ingo Molnar
2013-10-28 20:30       ` Matt Fleming
2013-10-29  8:11         ` Ingo Molnar
2013-10-04 19:55 Matt Fleming
2013-10-06  9:27 ` Ingo Molnar
2013-09-30 10:49 Matt Fleming
2013-09-30 14:26 ` H. Peter Anvin

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=20131027214815.GH1982@console-pimps.org \
    --to=matt@console-pimps.org \
    --cc=hpa@zytor.com \
    --cc=linux-efi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --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).