Re: [PATCH 2/2] efifb: Avoid reconfiguration of BAR that covers the framebuffer

2017-05-19 Thread Ard Biesheuvel
On 19 May 2017 at 21:44, Bjorn Helgaas wrote: > On Fri, May 19, 2017 at 05:37:30PM +0100, Ard Biesheuvel wrote: >> Hi Bjorn, >> >> On 19 May 2017 at 17:27, Bjorn Helgaas wrote: >> > [+cc linux-pci] >> > >> > On Tue, Apr 04, 2017 at 04:27:44PM +0100, Ard Biesheuvel wrote: >> >> On UEFI systems, th

Re: [PATCH 2/2] efifb: Avoid reconfiguration of BAR that covers the framebuffer

2017-05-19 Thread Bjorn Helgaas
On Fri, May 19, 2017 at 05:37:30PM +0100, Ard Biesheuvel wrote: > Hi Bjorn, > > On 19 May 2017 at 17:27, Bjorn Helgaas wrote: > > [+cc linux-pci] > > > > On Tue, Apr 04, 2017 at 04:27:44PM +0100, Ard Biesheuvel wrote: > >> On UEFI systems, the PCI subsystem is enumerated by the firmware, > >> and

Re: [PATCH 2/2] efifb: Avoid reconfiguration of BAR that covers the framebuffer

2017-05-19 Thread Ard Biesheuvel
Hi Bjorn, On 19 May 2017 at 17:27, Bjorn Helgaas wrote: > [+cc linux-pci] > > On Tue, Apr 04, 2017 at 04:27:44PM +0100, Ard Biesheuvel wrote: >> On UEFI systems, the PCI subsystem is enumerated by the firmware, >> and if a graphical framebuffer is exposed by a PCI device, its base >> address and

Re: [PATCH 2/2] efifb: Avoid reconfiguration of BAR that covers the framebuffer

2017-05-19 Thread Bjorn Helgaas
[+cc linux-pci] On Tue, Apr 04, 2017 at 04:27:44PM +0100, Ard Biesheuvel wrote: > On UEFI systems, the PCI subsystem is enumerated by the firmware, > and if a graphical framebuffer is exposed by a PCI device, its base > address and size are exposed to the OS via the Graphics Output > Protocol (GOP