[coreboot] BayleyBay FSP booting
martin.roth at se-eng.com
Sat Jul 19 22:05:28 CEST 2014
Tuan, Sorry - I've been on vacation and missed this thread until now.
What Wang Fei suggested is exactly right - you need to start with a
different BIOS flashed on the board.. The problem is the Descriptor/TXE
that is being used. Intel has said that they would update the build
instructions included with the FSP to highlight this issue, but I don't
know if this has been done.
I'm thinking I'll put in a check for this condition and print out a
message stating what needs to be done. I'll try to get that added shortly.
On 07/17/2014 03:55 PM, WANG FEI wrote:
> Your platform's northbirdge and GFX device ID is 0x0 and 0x0031? It's
> definitely wrong, I would suggest you to download the Bayley Bay
> platform's official UEFI BIOS from Intel IBL and flash it to you
> Bayley Bay platform, then see what's the correct ID.
> On Fri, Jul 11, 2014 at 4:36 AM, Patrick Georgi
> <patrick at georgi-clan.de <mailto:patrick at georgi-clan.de>> wrote:
> Am 01.07.2014 17:55, schrieb Tuan Vu:
> > Typically, what creates the memory ranges?
> To a large degree the memory init code, which is closed source in the
> FSP model and thus unavailable to us.
> When it comes to memory issues with FSP, it might be better to ask
> coreboot mailing list: coreboot at coreboot.org
> <mailto:coreboot at coreboot.org>
More information about the coreboot