Hello Alex, On 16.02.19 18:39, Alex Feinman wrote: > In my Coreboot build I provide both VBIOS and VBT blobs via appropriate > configuration items. The VBIOS blob contains expected signature at the > top and VBT is valid as confirmed by running intelvbttool against it. > The platform is slightly modified kblrvp (RVP3).
AIUI, you only need the VBT. If you are not going to run the VBIOS, you don't need that one. > > During the build I can see cbfstool reporting that both blobs were > placed in the image: To see the image's read-only sections as well, > rerun with the -w option. > > However, once the system boots, the VBIOS is not found at address > 0xc0000 You'd have to tell coreboot or a payload to load the VBIOS. AFAIK, coreboot only does it when you also tell it to use it for gfx init (`VGA_ROM_RUN`). > and VBT cannot be located either. I need VBT to be accessible > in order to specify the DP connector configuration for eDP. Suggestions > are appreciated Maybe check the coreboot console for clues. For instance there should be a line "ACPI: * IGD OpRegion" telling us that an OpRegion is set up that points to the VBT. If that doesn't happen, one possible cause is that your processors SKU isn't listed here: `src/soc/intel/common/block/graphics/graphics.c:108`. There is no reliable public source for these IDs. So it's hard to tell if the list is comprehensive. In any case, please report back. If you can't find a solution, please point to the exact code you are using and attach your `.config` file. Nico _______________________________________________ coreboot mailing list -- [email protected] To unsubscribe send an email to [email protected]
