There is a coreboot build for Camelback Mountain CRB, which uses Broadwell DE (aka Xeon D). It uses the Intel FSP for Broadwell DE package.
At least one version of the FSP binary plus wrapper files is available from an Intel GitHub area.
You can clone coreboot from the coreboot.org repo, build it, and try it, if you want.
As you are no doubt aware, if you already have UEFI working on your board with a commercial BIOS, you might want to ensure you understand any potential tradeoffs or pitfalls before committing to some other solution.
Sure, Calos. From my Linux /proc/cpuinfo dump, I get 1 copy of the following -
processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 86 model name : Intel(R) Xeon(R) CPU D-1527 @ 2.20GHz stepping : 3 microcode : 0x700000d cpu MHz : 800.421 cache size : 6144 KB physical id : 0 siblings : 8 core id : 0 cpu cores : 4 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 20 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch ida arat epb pln pts dtherm intel_pt tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm cqm rdseed adx smap xsaveopt cqm_llc cqm_occup_llc
Oh, man, I didn't realize my last post has all the formats messed up completely. I thought I just did a simple text copy and paste.
Anyway, the board comes from Congatec B7XD. Website:
We're using Camelback Mountain BSP from Intel (Yocto Project reference). Please let me know what else you may need to know.
Hello, rksyeung :
We apologize for the delay to give you an update.
Based on your previous communication, we would like to give you the proper information but you should contact the manufacturer of the affected board.
Due to this fact, we suggest you address this consultation as a reference to the form and the channels listed at the following website:
We hope that this information may help you.