From: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: linux-efi@vger.kernel.org, Ingo Molnar <mingo@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
"H . Peter Anvin" <hpa@zytor.com>,
leif.lindholm@linaro.org, lorenzo.pieralisi@arm.com,
linux-kernel@vger.kernel.org, Eugene Cohen <eugene@hp.com>,
Matt Fleming <matt@codeblueprint.co.uk>,
Peter Jones <pjones@redhat.com>
Subject: Re: [GIT PULL 0/2] EFI fixes for v4.11
Date: Wed, 05 Apr 2017 12:08:31 +0200 [thread overview]
Message-ID: <5013223.ea6UCckGV3@amdc3058> (raw)
In-Reply-To: <20170404152744.26687-1-ard.biesheuvel@linaro.org>
Hi,
On Tuesday, April 04, 2017 04:27:42 PM Ard Biesheuvel wrote:
> Hello all,
>
> Please pull these fixes for EFI framebuffer support on ARM/arm64 systems.
>
> The following changes since commit 822f5845f710e57d7e2df1fd1ee00d6e19d334fe:
>
> efi/esrt: Cleanup bad memory map log messages (2017-03-17 18:53:12 +0000)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/efi/efi.git tags/efi-urgent
>
> for you to fetch changes up to e73c2811538bd36ec1340d01bafdc080af31914e:
>
> efifb: Avoid reconfiguration of BAR that covers the framebuffer (2017-04-04 15:56:43 +0100)
>
> ----------------------------------------------------------------
> Two fixes related to the EFI framebuffer driver:
> - Ignore Graphics Output Protocol (GOP) implementations that are marked as
> BLT-only -- the framebuffer base address is invalid in this case, and the
> Blt() method is not accessible to the kernel.
> - If the GOP framebuffer base address coincides with a memory BAR of a PCI
> device that has memory decoding enabled, claim the memory resource so that
> the PCI core will not attempt to move it later on.
>
> ----------------------------------------------------------------
> Ard Biesheuvel (1):
> efifb: Avoid reconfiguration of BAR that covers the framebuffer
This patch breaks build if PCI support is not enabled:
drivers/video/fbdev/efifb.c: In function ‘claim_efifb_bar’:
drivers/video/fbdev/efifb.c:386:2: error: implicit declaration of function ‘pci_claim_resource’ [-Werror=implicit-function-declaration]
(x86 ifdefs are not enough, the patch should also check for PCI support)
Also please cc: linux-fbdev mailing list & me on fbdev related patches.
> Cohen, Eugene (1):
> efi/libstub: Skip GOP with PIXEL_BLT_ONLY format
>
> drivers/firmware/efi/libstub/gop.c | 6 ++--
> drivers/video/fbdev/efifb.c | 66 +++++++++++++++++++++++++++++++++++++-
> 2 files changed, 69 insertions(+), 3 deletions(-)
Best regards,
--
Bartlomiej Zolnierkiewicz
Samsung R&D Institute Poland
Samsung Electronics
next prev parent reply other threads:[~2017-04-05 10:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-04 15:27 [GIT PULL 0/2] EFI fixes for v4.11 Ard Biesheuvel
2017-04-04 15:27 ` [PATCH 1/2] efi/libstub: Skip GOP with PIXEL_BLT_ONLY format Ard Biesheuvel
2017-04-04 15:27 ` [PATCH 2/2] efifb: Avoid reconfiguration of BAR that covers the framebuffer Ard Biesheuvel
2017-05-19 16:27 ` Bjorn Helgaas
[not found] ` <20170519162716.GA684-1RhO1Y9PlrlHTL0Zs8A6p5iNqAH0jzoTYJqu5kTmcBRl57MIdRCFDg@public.gmane.org>
2017-05-19 16:37 ` Ard Biesheuvel
2017-05-19 20:44 ` Bjorn Helgaas
[not found] ` <20170519204445.GA25510-1RhO1Y9PlrlHTL0Zs8A6p5iNqAH0jzoTYJqu5kTmcBRl57MIdRCFDg@public.gmane.org>
2017-05-19 22:04 ` Ard Biesheuvel
[not found] ` <CGME20170405100833epcas1p4b5076679dc4f8644fa789b421a66f953@epcas1p4.samsung.com>
2017-04-05 10:08 ` Bartlomiej Zolnierkiewicz [this message]
2017-04-05 10:14 ` [GIT PULL 0/2] EFI fixes for v4.11 Ard Biesheuvel
2017-04-05 10:26 ` Ingo Molnar
2017-04-05 10:32 ` Ard Biesheuvel
[not found] ` <CAKv+Gu_VaKNDmaWc2Gqpg1JB6pBthCVUOGEsONb8sj2Uos7qcg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-04-05 10:44 ` Bartlomiej Zolnierkiewicz
2017-04-05 10:45 ` 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=5013223.ea6UCckGV3@amdc3058 \
--to=b.zolnierkie@samsung.com \
--cc=ard.biesheuvel@linaro.org \
--cc=eugene@hp.com \
--cc=hpa@zytor.com \
--cc=leif.lindholm@linaro.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=matt@codeblueprint.co.uk \
--cc=mingo@kernel.org \
--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).