Re: [coreboot] Porting coreboot to new board

2018-05-30 Thread Zvi Vered
Hi All, The links you provided: https://www.coreboot.org/Motherboard_Porting_Guide https://www.coreboot.org/Developer_Manual Does not mention Intel's FSP at all. How FSP is integrated during coreboot porting ? src\venorcode\intel contains 2 FSP versions. src\soc\intel contains fsp_baytrail,

Re: [coreboot] Porting coreboot to new board

2018-05-30 Thread Youness Alaoui
This is the best I can do for you : https://ark.intel.com/products/89608/Intel-Xeon-Processor-E3-1505M-v5-8M-Cache-2_80-GHz Product Collection: Intel® Xeon® Processor E3 v5 Family Code Name: Products formerly Skylake kakaroto@kakaroto:~/coding/purism/coreboot$ git grep SOC_INTEL_SKYLAKE | grep

Re: [coreboot] AMD IMC open source firmware replacement

2018-05-30 Thread Rudolf Marek
Dne 30.5.2018 v 16:06 Mike Banon napsal(a): > Hi Rudolf, > > Regarding this part: > " To check if IMC is active check if PCI 0:14.3 0x40 bit7 set. " > what command do I need to use to check this? Try: sudo setpci -s 14.3 40.b Despite command name, it will print the value. Thanks Rudolf --

[coreboot] AMD IMC open source firmware replacement

2018-05-30 Thread Vincent Legoll
Hello, you can try with: lspci -vvv -- Vincent Legoll -- coreboot mailing list: coreboot@coreboot.org https://mail.coreboot.org/mailman/listinfo/coreboot

Re: [coreboot] Porting coreboot to new board

2018-05-30 Thread Zvi Vered
Hello Youness, Thank you very much for the detailed information ! Can you please tell what is the best starting point for a XEON board ? I think there are no "Intel® XEON® Processor E3-1505M v5" boards in last version of coreboot. Am I right ? Best regards, Zvika On Tue, May 29, 2018 at 9:15

Re: [coreboot] AMD IMC open source firmware replacement

2018-05-30 Thread Mike Banon
Hi Rudolf, Regarding this part: " To check if IMC is active check if PCI 0:14.3 0x40 bit7 set. " what command do I need to use to check this? Thanks in advance, Mike On Fri, May 25, 2018 at 7:30 PM, Rudolf Marek wrote: > Hi Mike, > > My firmware was just a proof of concept. It was never