Re: [PATCH] arm64: Relocate screen_info.lfb_base on PCI BAR allocation

(Pulling in efifb maintainer, Peter) On Fri, 29 Apr, at 06:31:19PM, Bjorn Helgaas wrote: > > The efifb.c driver doesn't do anything at all with PCI (it includes > linux/pci.h, but probably doesn't need it). That's part of what I'm > suggesting -- if it *did* register as a PCI device driver,

Re: [PATCH] arm64: Relocate screen_info.lfb_base on PCI BAR allocation

(Pulling in efifb maintainer, Peter) On Fri, 29 Apr, at 06:31:19PM, Bjorn Helgaas wrote: > > The efifb.c driver doesn't do anything at all with PCI (it includes > linux/pci.h, but probably doesn't need it). That's part of what I'm > suggesting -- if it *did* register as a PCI device driver,

Re: [PATCH] arm64: Relocate screen_info.lfb_base on PCI BAR allocation

[+cc Matt, because I'm out of my depth in this UEFI stuff] On Fri, Apr 29, 2016 at 11:52:47PM +0200, Alexander Graf wrote: > On 29.04.16 23:37, Bjorn Helgaas wrote: > > On Fri, Apr 29, 2016 at 10:51:34PM +0200, Alexander Graf wrote: > >> I think the only thing we can really take as granted is

Re: [PATCH] arm64: Relocate screen_info.lfb_base on PCI BAR allocation

[+cc Matt, because I'm out of my depth in this UEFI stuff] On Fri, Apr 29, 2016 at 11:52:47PM +0200, Alexander Graf wrote: > On 29.04.16 23:37, Bjorn Helgaas wrote: > > On Fri, Apr 29, 2016 at 10:51:34PM +0200, Alexander Graf wrote: > >> I think the only thing we can really take as granted is

Re: [PATCH] arm64: Relocate screen_info.lfb_base on PCI BAR allocation

On 29.04.16 23:52, Alexander Graf wrote: > > > On 29.04.16 23:37, Bjorn Helgaas wrote: > > Can you point me to the code that does "read[ing] the BARs"? So far my > impression was that we don't even try to read out the current BAR values > from pci config space, but I can't claim I fully grasp

Re: [PATCH] arm64: Relocate screen_info.lfb_base on PCI BAR allocation

On 29.04.16 23:52, Alexander Graf wrote: > > > On 29.04.16 23:37, Bjorn Helgaas wrote: > > Can you point me to the code that does "read[ing] the BARs"? So far my > impression was that we don't even try to read out the current BAR values > from pci config space, but I can't claim I fully grasp

Re: [PATCH] arm64: Relocate screen_info.lfb_base on PCI BAR allocation

On 29.04.16 23:37, Bjorn Helgaas wrote: > On Fri, Apr 29, 2016 at 10:51:34PM +0200, Alexander Graf wrote: >> >> >> On 29.04.16 22:25, Ard Biesheuvel wrote: >>> On 29 apr. 2016, at 22:06, Bjorn Helgaas wrote: > On Fri, Apr 29, 2016 at 03:51:49PM +0200, Ard

Re: [PATCH] arm64: Relocate screen_info.lfb_base on PCI BAR allocation

On 29.04.16 23:37, Bjorn Helgaas wrote: > On Fri, Apr 29, 2016 at 10:51:34PM +0200, Alexander Graf wrote: >> >> >> On 29.04.16 22:25, Ard Biesheuvel wrote: >>> On 29 apr. 2016, at 22:06, Bjorn Helgaas wrote: > On Fri, Apr 29, 2016 at 03:51:49PM +0200, Ard Biesheuvel wrote: >>

Re: [PATCH] arm64: Relocate screen_info.lfb_base on PCI BAR allocation

On Fri, Apr 29, 2016 at 10:51:34PM +0200, Alexander Graf wrote: > > > On 29.04.16 22:25, Ard Biesheuvel wrote: > > > >> On 29 apr. 2016, at 22:06, Bjorn Helgaas wrote: > >> > >>> On Fri, Apr 29, 2016 at 03:51:49PM +0200, Ard Biesheuvel wrote: > On 29 April 2016 at

Re: [PATCH] arm64: Relocate screen_info.lfb_base on PCI BAR allocation

On Fri, Apr 29, 2016 at 10:51:34PM +0200, Alexander Graf wrote: > > > On 29.04.16 22:25, Ard Biesheuvel wrote: > > > >> On 29 apr. 2016, at 22:06, Bjorn Helgaas wrote: > >> > >>> On Fri, Apr 29, 2016 at 03:51:49PM +0200, Ard Biesheuvel wrote: > On 29 April 2016 at 15:41, Bjorn Helgaas

Re: [PATCH] arm64: Relocate screen_info.lfb_base on PCI BAR allocation

On Fri, Apr 29, 2016 at 10:25:13PM +0200, Ard Biesheuvel wrote: > > > On 29 apr. 2016, at 22:06, Bjorn Helgaas wrote: > > > >> On Fri, Apr 29, 2016 at 03:51:49PM +0200, Ard Biesheuvel wrote: > >>> On 29 April 2016 at 15:41, Bjorn Helgaas wrote: > On

Re: [PATCH] arm64: Relocate screen_info.lfb_base on PCI BAR allocation

On Fri, Apr 29, 2016 at 10:25:13PM +0200, Ard Biesheuvel wrote: > > > On 29 apr. 2016, at 22:06, Bjorn Helgaas wrote: > > > >> On Fri, Apr 29, 2016 at 03:51:49PM +0200, Ard Biesheuvel wrote: > >>> On 29 April 2016 at 15:41, Bjorn Helgaas wrote: > On Thu, Apr 28, 2016 at 11:39:35PM +0200,

Re: [PATCH] arm64: Relocate screen_info.lfb_base on PCI BAR allocation

On 29.04.16 22:25, Ard Biesheuvel wrote: > >> On 29 apr. 2016, at 22:06, Bjorn Helgaas wrote: >> >>> On Fri, Apr 29, 2016 at 03:51:49PM +0200, Ard Biesheuvel wrote: On 29 April 2016 at 15:41, Bjorn Helgaas wrote: > On Thu, Apr 28, 2016 at

Re: [PATCH] arm64: Relocate screen_info.lfb_base on PCI BAR allocation

On 29.04.16 22:25, Ard Biesheuvel wrote: > >> On 29 apr. 2016, at 22:06, Bjorn Helgaas wrote: >> >>> On Fri, Apr 29, 2016 at 03:51:49PM +0200, Ard Biesheuvel wrote: On 29 April 2016 at 15:41, Bjorn Helgaas wrote: > On Thu, Apr 28, 2016 at 11:39:35PM +0200, Alexander Graf wrote: >

Re: [PATCH] arm64: Relocate screen_info.lfb_base on PCI BAR allocation

> On 29 apr. 2016, at 22:06, Bjorn Helgaas wrote: > >> On Fri, Apr 29, 2016 at 03:51:49PM +0200, Ard Biesheuvel wrote: >>> On 29 April 2016 at 15:41, Bjorn Helgaas wrote: On Thu, Apr 28, 2016 at 11:39:35PM +0200, Alexander Graf wrote: On

Re: [PATCH] arm64: Relocate screen_info.lfb_base on PCI BAR allocation

> On 29 apr. 2016, at 22:06, Bjorn Helgaas wrote: > >> On Fri, Apr 29, 2016 at 03:51:49PM +0200, Ard Biesheuvel wrote: >>> On 29 April 2016 at 15:41, Bjorn Helgaas wrote: On Thu, Apr 28, 2016 at 11:39:35PM +0200, Alexander Graf wrote: On 28.04.16 20:06, Bjorn Helgaas wrote: > >

Re: [PATCH] arm64: Relocate screen_info.lfb_base on PCI BAR allocation

On Fri, Apr 29, 2016 at 03:51:49PM +0200, Ard Biesheuvel wrote: > On 29 April 2016 at 15:41, Bjorn Helgaas wrote: > > On Thu, Apr 28, 2016 at 11:39:35PM +0200, Alexander Graf wrote: > >> On 28.04.16 20:06, Bjorn Helgaas wrote: > >> > If firmware is giving us a bare address of

Re: [PATCH] arm64: Relocate screen_info.lfb_base on PCI BAR allocation

On Fri, Apr 29, 2016 at 03:51:49PM +0200, Ard Biesheuvel wrote: > On 29 April 2016 at 15:41, Bjorn Helgaas wrote: > > On Thu, Apr 28, 2016 at 11:39:35PM +0200, Alexander Graf wrote: > >> On 28.04.16 20:06, Bjorn Helgaas wrote: > >> > If firmware is giving us a bare address of something, that

Re: [PATCH] arm64: Relocate screen_info.lfb_base on PCI BAR allocation

On 29 April 2016 at 15:41, Bjorn Helgaas wrote: > On Thu, Apr 28, 2016 at 11:39:35PM +0200, Alexander Graf wrote: >> On 28.04.16 20:06, Bjorn Helgaas wrote: >> > On Thu, Apr 28, 2016 at 06:41:42PM +0200, Alexander Graf wrote: >> >> On 04/28/2016 06:20 PM, Bjorn Helgaas wrote:

Re: [PATCH] arm64: Relocate screen_info.lfb_base on PCI BAR allocation

On 29 April 2016 at 15:41, Bjorn Helgaas wrote: > On Thu, Apr 28, 2016 at 11:39:35PM +0200, Alexander Graf wrote: >> On 28.04.16 20:06, Bjorn Helgaas wrote: >> > On Thu, Apr 28, 2016 at 06:41:42PM +0200, Alexander Graf wrote: >> >> On 04/28/2016 06:20 PM, Bjorn Helgaas wrote: >> >>> On Thu, Apr

Re: [PATCH] arm64: Relocate screen_info.lfb_base on PCI BAR allocation

On Thu, Apr 28, 2016 at 11:39:35PM +0200, Alexander Graf wrote: > On 28.04.16 20:06, Bjorn Helgaas wrote: > > On Thu, Apr 28, 2016 at 06:41:42PM +0200, Alexander Graf wrote: > >> On 04/28/2016 06:20 PM, Bjorn Helgaas wrote: > >>> On Thu, Apr 28, 2016 at 12:22:24AM +0200, Alexander Graf wrote: >

Re: [PATCH] arm64: Relocate screen_info.lfb_base on PCI BAR allocation

On Thu, Apr 28, 2016 at 11:39:35PM +0200, Alexander Graf wrote: > On 28.04.16 20:06, Bjorn Helgaas wrote: > > On Thu, Apr 28, 2016 at 06:41:42PM +0200, Alexander Graf wrote: > >> On 04/28/2016 06:20 PM, Bjorn Helgaas wrote: > >>> On Thu, Apr 28, 2016 at 12:22:24AM +0200, Alexander Graf wrote: >

Re: [PATCH] arm64: Relocate screen_info.lfb_base on PCI BAR allocation

On Thu, Apr 28, 2016 at 11:39:35PM +0200, Alexander Graf wrote: > > > On 28.04.16 20:06, Bjorn Helgaas wrote: > > On Thu, Apr 28, 2016 at 06:41:42PM +0200, Alexander Graf wrote: > >> On 04/28/2016 06:20 PM, Bjorn Helgaas wrote: > >>> On Thu, Apr 28, 2016 at 12:22:24AM +0200, Alexander Graf

Re: [PATCH] arm64: Relocate screen_info.lfb_base on PCI BAR allocation

On Thu, Apr 28, 2016 at 11:39:35PM +0200, Alexander Graf wrote: > > > On 28.04.16 20:06, Bjorn Helgaas wrote: > > On Thu, Apr 28, 2016 at 06:41:42PM +0200, Alexander Graf wrote: > >> On 04/28/2016 06:20 PM, Bjorn Helgaas wrote: > >>> On Thu, Apr 28, 2016 at 12:22:24AM +0200, Alexander Graf

Re: [PATCH] arm64: Relocate screen_info.lfb_base on PCI BAR allocation

On 28.04.16 20:06, Bjorn Helgaas wrote: > On Thu, Apr 28, 2016 at 06:41:42PM +0200, Alexander Graf wrote: >> On 04/28/2016 06:20 PM, Bjorn Helgaas wrote: >>> On Thu, Apr 28, 2016 at 12:22:24AM +0200, Alexander Graf wrote: When booting with efifb, we get a frame buffer address passed into

Re: [PATCH] arm64: Relocate screen_info.lfb_base on PCI BAR allocation

On 28.04.16 20:06, Bjorn Helgaas wrote: > On Thu, Apr 28, 2016 at 06:41:42PM +0200, Alexander Graf wrote: >> On 04/28/2016 06:20 PM, Bjorn Helgaas wrote: >>> On Thu, Apr 28, 2016 at 12:22:24AM +0200, Alexander Graf wrote: When booting with efifb, we get a frame buffer address passed into

Re: [PATCH] arm64: Relocate screen_info.lfb_base on PCI BAR allocation

On Thu, Apr 28, 2016 at 06:41:42PM +0200, Alexander Graf wrote: > On 04/28/2016 06:20 PM, Bjorn Helgaas wrote: > >On Thu, Apr 28, 2016 at 12:22:24AM +0200, Alexander Graf wrote: > >>When booting with efifb, we get a frame buffer address passed into the > >>system. > >>This address can be backed

Re: [PATCH] arm64: Relocate screen_info.lfb_base on PCI BAR allocation

On Thu, Apr 28, 2016 at 06:41:42PM +0200, Alexander Graf wrote: > On 04/28/2016 06:20 PM, Bjorn Helgaas wrote: > >On Thu, Apr 28, 2016 at 12:22:24AM +0200, Alexander Graf wrote: > >>When booting with efifb, we get a frame buffer address passed into the > >>system. > >>This address can be backed

Re: [PATCH] arm64: Relocate screen_info.lfb_base on PCI BAR allocation

On 04/28/2016 06:20 PM, Bjorn Helgaas wrote: On Thu, Apr 28, 2016 at 12:22:24AM +0200, Alexander Graf wrote: When booting with efifb, we get a frame buffer address passed into the system. This address can be backed by any device, including PCI devices. I guess we get the frame buffer address

Re: [PATCH] arm64: Relocate screen_info.lfb_base on PCI BAR allocation

On 04/28/2016 06:20 PM, Bjorn Helgaas wrote: On Thu, Apr 28, 2016 at 12:22:24AM +0200, Alexander Graf wrote: When booting with efifb, we get a frame buffer address passed into the system. This address can be backed by any device, including PCI devices. I guess we get the frame buffer address

Re: [PATCH] arm64: Relocate screen_info.lfb_base on PCI BAR allocation

On Thu, Apr 28, 2016 at 12:22:24AM +0200, Alexander Graf wrote: > When booting with efifb, we get a frame buffer address passed into the system. > This address can be backed by any device, including PCI devices. I guess we get the frame buffer address via EFI, but it doesn't tell us what PCI

Re: [PATCH] arm64: Relocate screen_info.lfb_base on PCI BAR allocation

On Thu, Apr 28, 2016 at 12:22:24AM +0200, Alexander Graf wrote: > When booting with efifb, we get a frame buffer address passed into the system. > This address can be backed by any device, including PCI devices. I guess we get the frame buffer address via EFI, but it doesn't tell us what PCI