(This covers commits 6cb3a59 (which is the 4.1 tag) up to commit 406effd5)
This week brought the addition of one new chipset and four new
mainboards: Welcome the Intel Skylake SoC, and the new mainboards
google/cyan, intel/kunimitsu, intel/sklrvp, and intel/strago, which
are Braswell or Skylake based.
As for tools, the script that generated the 4.1 release was added to
the tree. To aid with debugging build issues, buildgcc shows the URLs
it uses to download the sources to the toolchain. The standard git
hook now uses a customized version of Linux’s checkpatch.pl utility
for better coding style compliance tests. The cbmem utility gained
OpenBSD compatibility when reading timestamps.
The USB host drivers in libpayload saw improvements both for USB3,
supporting SuperSpeed hubs and showing more robustness in the presence
of strangely behaving USB devices, and for DWC2 controllers, which now
support LowSpeed devices behind HighSpeed hubs. coreboot also passes
more information to libpayload on where to find the flash part as well
as the parameters of the CBFS that was used during boot.
The CBFS format is seeing new development: The default alignment for
files is now hardcoded to 64 bytes, which was already the default.
There are no known instances where this value was changed, and it
simplifies development going forward. The change is forward compatible
in that old users can still read new CBFS images. New CBFS consumers
run into problems if they work on a CBFS image with a different
Furthermore there were discussions on how to extend the CBFS format
compatibly. So far this led to numerous refactorings in cbfstool to
simplify further development.
Finally, there were a whole lot of bug fixes: ARM64, the code for
Nvidia’s Tegra210 chipset and the google/foster and google/smaug
boards saw lots of development, from making them boot again to various
hardware enablement. AMD’s RS780 chipset was effectively disabled due
to a typo in the build system. There’s an ongoing effort to bring AMD
K8/Fam10h into shape again, which also positively affected HD Audio
configuration. CBMEM timestamps are more complete than ever.
There was also the usual bunch of cleanups that get rid of unused
Kconfig symbols and configuration options, deal with wrong
indentation, and replace magic numbers with meaningful names.
Google Germany GmbH, ABC-Str. 19, 20354 Hamburg
Registergericht und -nummer: Hamburg, HRB 86891, Sitz der Gesellschaft: Hamburg
Geschäftsführer: Graham Law, Christine Elizabeth Flores