YuSeok,
It looks your platform has enabled the Memory Down function.
The MEM_DOWN_DIMM_SPD_DATA structure supposed to be filled with the
relative DIMM SPD data as described in comments, for example,
DRAMDeviceType =>>> SPD Byte Offset 2
ModuleType =>>> SPD Byte offset 3
DramManufacturerIdLsb
Here is a sample,
Please select INCLUDE_ME to y and set ME_PATH to point to your
descriptor.bin (Path/descriptor.bin, refer to FSP_FILE as a sample).
On Mon, Jun 20, 2016 at 10:48 PM, WANG FEI wrote:
> YuSeok, how did you attach the descriptor.bin to your coreboot? Did
On Mon, 20 Jun 2016, Julius Werner wrote:
> Yes, this definitely looks like a bug... thanks a lot for reporting
> it. The fix is simple and I've uploaded it here:
> https://review.coreboot.org/15273
>
Thank you for this commit. I've just tested it - and now it works
correctly.
> I'm curious
Looking at the logs you've got, the final bios only have BIOS/coreboot and
descriptor.bin, the GbE/ME areas are not used, I think as long as your
enable the descripor.bin, it should be good enough.
poplinux@raw rangeley $ > ./tools/ifdtool -x ./oem_dumped.bin
File ./oem_dumped.bin is 8388608
Hi,
I reply to myself: '241' is also git stuff. It's the number of commit in this
branch.
Found the info after a 'man git-describe'.
So please ignore this request.
Best regards,
Patrick Agrain
-Message d'origine-
De : Agrain Patrick
Envoyé : mardi 21 juin 2016 14:47
À :
Coreboot for Intel ApolloLake needs FSP v2.0 blobs. Unfortunately FSP v2.0 is
not offered at www.intel.com/fsp.
Do you know, how or where I could get it?
Kind regards,
Rolf
--
coreboot mailing list: coreboot@coreboot.org
https://www.coreboot.org/mailman/listinfo/coreboot
I have a kgpe-d16 with coreboot and it *was* working with linux. I now have
a linux kernel that won't boot on fuctory bios or coreboot. I can't recall
changing anything ...
If somebody's got a known good .config for linux I could sure use it. I'm
booting stock tinycore and it seems to hang a lot.
On Thu, Jun 16, 2016 at 8:55 AM, Rolf Evers-Fischer
wrote:
> Hello,
> my ApolloLake board was not able to find the "romstage" in the SPI memory,
> because it searched in the wrong part of the memory.
>
> ___FMAP__COREBOOT_BASE was set to the relative offset within the
Hi Rolf,
I think blobs aren't uploaded yet because ApolloLake has not been
officially announced.
You should try contacting Intel to get the blobs. I know Intel does
offer blobs to certain customers who use FSP-based solutions.
Andrey
On 06/21/2016 06:25 AM, Rolf Evers-Fischer wrote:
Yes, this definitely looks like a bug... thanks a lot for reporting
it. The fix is simple and I've uploaded it here:
https://review.coreboot.org/15273
I'm curious why this hasn't been noticed anywhere before, though...
(on some boards this just happens to work out because the parent
section of
10 matches
Mail list logo