<feed xmlns='http://www.w3.org/2005/Atom'>
<title>starfive-tech/u-boot.git/lib/zlib/deflate.c, branch rtthread_AMP</title>
<subtitle>StarFive Tech U-Boot for VisionFive (JH7110) boards (mirror)</subtitle>
<id>https://git.radix-linux.su/starfive-tech/u-boot.git/atom?h=rtthread_AMP</id>
<link rel='self' href='https://git.radix-linux.su/starfive-tech/u-boot.git/atom?h=rtthread_AMP'/>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/starfive-tech/u-boot.git/'/>
<updated>2021-01-17T00:17:11+00:00</updated>
<entry>
<title>lib: zlib: our putc() takes only one argument</title>
<updated>2021-01-17T00:17:11+00:00</updated>
<author>
<name>Heinrich Schuchardt</name>
<email>xypron.glpk@gmx.de</email>
</author>
<published>2020-12-28T20:41:40+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/starfive-tech/u-boot.git/commit/?id=986c841c8b41ba3dc8d8bc4ce3802779cf69bfc0'/>
<id>urn:sha1:986c841c8b41ba3dc8d8bc4ce3802779cf69bfc0</id>
<content type='text'>
In contrast to the C99 standard [1] our putc() takes only one argument.

[1] ISO/IEC 9899:1999

Signed-off-by: Heinrich Schuchardt &lt;xypron.glpk@gmx.de&gt;
</content>
</entry>
<entry>
<title>crc32: Use the crc.h header for crc functions</title>
<updated>2019-12-02T23:23:08+00:00</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2019-11-14T19:57:16+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/starfive-tech/u-boot.git/commit/?id=3db7110857524cf1b7d0a374c1ebcde8a2680de0'/>
<id>urn:sha1:3db7110857524cf1b7d0a374c1ebcde8a2680de0</id>
<content type='text'>
Drop inclusion of crc.h in common.h and use the correct header directly
instead.

With this we can drop the conflicting definition in fw_env.h and rely on
the crc.h header, which is already included.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
Reviewed-by: Tom Rini &lt;trini@konsulko.com&gt;
</content>
</entry>
<entry>
<title>lib: zlib: remove the limitation for cannot using 0 as start</title>
<updated>2012-09-29T14:26:08+00:00</updated>
<author>
<name>Lei Wen</name>
<email>adrian.wenl@gmail.com</email>
</author>
<published>2012-09-28T04:26:45+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/starfive-tech/u-boot.git/commit/?id=869c2abbaf98e91e7c9ef71806f6c8eef91206ae'/>
<id>urn:sha1:869c2abbaf98e91e7c9ef71806f6c8eef91206ae</id>
<content type='text'>
We often need the requirement that compressing those memory range start
from 0, but the default deflate code in zlib prevent us to do this.
Considering the special case of uboot, that it could access all memory
range, it is reasonable to be able to also take the address space from 0
into compression.

Signed-off-by: Lei Wen &lt;leiwen@marvell.com&gt;
</content>
</entry>
<entry>
<title>lib: zlib: import deflate source file from 1.2.5</title>
<updated>2012-09-29T14:26:08+00:00</updated>
<author>
<name>Lei Wen</name>
<email>adrian.wenl@gmail.com</email>
</author>
<published>2012-09-28T04:26:42+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/starfive-tech/u-boot.git/commit/?id=8a5f34effa2a2dd6ed1b57894e9b395094066504'/>
<id>urn:sha1:8a5f34effa2a2dd6ed1b57894e9b395094066504</id>
<content type='text'>
Signed-off-by: Lei Wen &lt;leiwen@marvell.com&gt;
</content>
</entry>
</feed>
