Attention is currently required from: Jakub Czapiga, Paul Fagerburg, Jan Dabros. Julius Werner has posted comments on this change. ( https://review.coreboot.org/c/coreboot/+/56305 )
Change subject: tests: Add lib/lzmadecode-test test case ......................................................................
Patch Set 1:
(1 comment)
File tests/include/tests/lib/lzmadecode_data.h:
https://review.coreboot.org/c/coreboot/+/56305/comment/326d0282_a0669b41 PS1, Line 24: unsigned char test_lzmadecode_data_binary[] = {
I have checked the `xz` manual again. Specifically, the `Streamed vs. non-streamed .lzma files` section. It says, that XZ Utils always use end-of-payload marker, and put unknown (zero) uncompressed file size in the LZMA header. Moreover, manual suggests using LZMA Utils instead, if one needs uncompressed file size field to be filled.
Sorry, actually, I confused myself there... Chrome OS is using XZ for kernel compression, but coreboot isn't involved in decompressing that (although libpayload is which should(?) pretty much use the same algorithm). For payload compression we just use what's built into cbfstool. So if you're saying that XZ util output doesn't work in coreboot I guess we can skip testing that. The most important thing to test is the one built into cbfstool (you should be able to use cbfs-compression-tool to generate files with that more easily).