Thanks for info. The issue for me turned out to be an incorrect “subsystem
id” in the device tree. I found it a bit surprising since the e1000e driver
doesn’t seem to directly care, but perhaps other workarounds got triggered that
caused issues. I found it also behaved well without setting
Hi Ricky,
>From coreboot leadership meeting minutes:
### [Martin] Gitiles is still disabled
* It was disabled since a web crawler was hitting it with a lot of
requests, causing a lot of
traffic and CPU utilization, and ultimately DOS'ing Gerrit.
Regards,
Jakub Czapiga
On Mon, Apr 8, 2024 at 2:48
Hello.
At https://github.com/coreboot/coreboot, links
https://review.coreboot.org/plugins/gitiles/coreboot/+/HEAD
https://review.coreboot.org/coreboot.git
are invalid.
Regards.
___
coreboot mailing list -- coreboot@coreboot.org
To unsubscribe send an
Hi,
ChipsetInitBinary is something consumed by ME. You may find references
of it in the FITc/FIT/mFIT, where you can integrate that binary as a
part of ME image.
Intel distributes a separate toolkit to generate a ChipsetInitBinary.
Mostly the binary comprises of voltage settings for some pads and
4 matches
Mail list logo