On 22 June 2018 at 15:52, Sinan Kaya <okaya@xxxxxxxxxxxxxx> wrote: > Hi Ard, > > On 6/22/2018 7:21 AM, Ard Biesheuvel wrote: >> Apologies for only bringing this up now, but I think this patch is >> wrong after all. >> >> screen_info.lfb_base is supposed to be a CPU address, and so >> translating it like this is wrong. If you end up with a PCI address >> here, you have made a mistake in hacking support for PCI outbound >> translations into UEFI. Other users such as UEFI itself or GRUB will >> treat this as a CPU physical address as well, so the kernel should not >> treat it any differently. > > The behavior I'm seeing is from a UEFI BIOS vendor. I did not write the > code for it... > > I was asked to debug it. > > I'd like to dive into your statement about UEFI and GRUB using this address > as physical addresses. > > AFAIK, all PCI outbound requests go through PCI IO protocol in UEFI and the > translation information is hidden inside the UEFI PCI Host Bridge driver. > Drivers are not allowed to access PCI resources directly especially as a > memory mapped address. > > This particular vendor is programming the BAR address into the GOP protocol. > Since the host bridge driver is doing a translation, we are hitting this > issue. > > Is there a UEFI spec reference about the definition of this field? > Yes, it is part of the PCI I/O protocol definition. FrameBufferBase is described as """ Base address of graphics linear frame buffer. Info contains information required to allow software to draw directly to the frame buffer without using Blt().Offset zero in FrameBufferBase represents the upper left pixel of the display. """ -- To unsubscribe from this list: send the line "unsubscribe linux-arm-msm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
