<feed xmlns='http://www.w3.org/2005/Atom'>
<title>staging/aparcar/tools/mkimage, branch master</title>
<subtitle>Staging tree of Paul Spooren</subtitle>
<id>https://git.openwrt.org/openwrt/staging/aparcar/atom?h=master</id>
<link rel='self' href='https://git.openwrt.org/openwrt/staging/aparcar/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/aparcar/'/>
<updated>2023-01-13T14:49:52Z</updated>
<entry>
<title>tools/mkimage: update to 2023.01</title>
<updated>2023-01-13T14:49:52Z</updated>
<author>
<name>Linhui Liu</name>
</author>
<published>2023-01-12T10:10:02Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/aparcar/commit/?id=1909a3d69be15b34430f8c30b9ec7c8ef07c9650'/>
<id>urn:sha1:1909a3d69be15b34430f8c30b9ec7c8ef07c9650</id>
<content type='text'>
Remove upstreamed patches:
- 020-tools-mtk_image-split-gfh-header-verification-into-a.patch
- 021-tools-mtk_image-split-the-code-of-generating-NAND-he.patch
- 022-tools-mtk_image-add-support-for-nand-headers-used-by.patch

Signed-off-by: Linhui Liu &lt;liulinhui36@gmail.com&gt;
</content>
</entry>
<entry>
<title>tools/mkimage: bring back removed patches</title>
<updated>2022-10-23T15:29:59Z</updated>
<author>
<name>Daniel Golle</name>
</author>
<published>2022-10-23T15:21:26Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/aparcar/commit/?id=e3706bf49756557636105f0d5f6ecf45d5b12e20'/>
<id>urn:sha1:e3706bf49756557636105f0d5f6ecf45d5b12e20</id>
<content type='text'>
Patches for mtk_image supporting newer SoCs have been dropped in the
process of updating mkimage to U-Boot 2022.10. While it is true that
the patches have been merged upstream a while ago, they were not merged
in time to be part of the U-Boot 2022.10 release.
See also commit 537b423d9f ("uboot-mediatek: update to U-Boot 2022.10")
which explicitly mentions that.

Fixes: 6e245777bd ("tools/mkimage: update to 2022.10")
Signed-off-by: Daniel Golle &lt;daniel@makrotopia.org&gt;
</content>
</entry>
<entry>
<title>tools/mkimage: update to 2022.10</title>
<updated>2022-10-22T20:50:36Z</updated>
<author>
<name>Nick Hainke</name>
</author>
<published>2022-10-21T20:53:58Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/aparcar/commit/?id=6e245777bdfe75f73766ef06458de6313a7d4d5e'/>
<id>urn:sha1:6e245777bdfe75f73766ef06458de6313a7d4d5e</id>
<content type='text'>
Remove upstreamed patches:
- 020-tools-mtk_image-split-gfh-header-verification-into-a.patch
- 021-tools-mtk_image-split-the-code-of-generating-NAND-he.patch
- 022-tools-mtk_image-add-support-for-nand-headers-used-by.patch

Refreshed manually:
- 030-allow-to-use-different-magic.patch

Signed-off-by: Nick Hainke &lt;vincent@systemli.org&gt;
</content>
</entry>
<entry>
<title>tools: mkimage: Add support for MediaTek MT798x</title>
<updated>2022-08-28T18:01:55Z</updated>
<author>
<name>Daniel Golle</name>
</author>
<published>2022-08-05T12:18:20Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/aparcar/commit/?id=8686a9a085d4313a0107a3e4378b3762c8293570'/>
<id>urn:sha1:8686a9a085d4313a0107a3e4378b3762c8293570</id>
<content type='text'>
Import pending patches for mtk_image to support BootROM headers of
newer MediaTek SoCs.

Signed-off-by: Daniel Golle &lt;daniel@makrotopia.org&gt;
</content>
</entry>
<entry>
<title>mkimage: fix validation of legacy images with custom magic</title>
<updated>2022-08-12T10:02:41Z</updated>
<author>
<name>Daniel Golle</name>
</author>
<published>2022-08-12T10:02:04Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/aparcar/commit/?id=68cd4dc3ed6e50988bcc4f1eaeec9902677f109b'/>
<id>urn:sha1:68cd4dc3ed6e50988bcc4f1eaeec9902677f109b</id>
<content type='text'>
All images generated by mkimage are now always validated.
This change broke our downstream support for setting a custom value for
IH_MAGIC (mkimage -M ...). Make sure also plain legacy kernel images
with custom value set for IH_MAGIC validate correctly.

Fixes: fa9895ee5b ("tools: mkimage: update to U-Boot release 2022.07")
Signed-off-by: Daniel Golle &lt;daniel@makrotopia.org&gt;
</content>
</entry>
<entry>
<title>tools: mkimage: update to U-Boot release 2022.07</title>
<updated>2022-08-11T15:11:54Z</updated>
<author>
<name>Daniel Golle</name>
</author>
<published>2022-08-05T12:06:22Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/aparcar/commit/?id=fa9895ee5bae9fa91b18b7a8e06bc63374b0a2a0'/>
<id>urn:sha1:fa9895ee5bae9fa91b18b7a8e06bc63374b0a2a0</id>
<content type='text'>
Removed patch 090-macos-arm64-builing-fix.patch as an equivalent
solution was applied upstream:
 3b142045e8 Support building on macOS/arm64

To not add new host dependencies (libuuid, gnuTLS) don't build the
anyway unused mkeficapsule tool which would otherwise now be built
by default.

Signed-off-by: Daniel Golle &lt;daniel@makrotopia.org&gt;
</content>
</entry>
<entry>
<title>tools/mkimage: increase tmpfile name length limit</title>
<updated>2022-06-05T10:32:58Z</updated>
<author>
<name>Daniel Golle</name>
</author>
<published>2022-06-05T10:28:11Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/aparcar/commit/?id=3fbf9689b652e230e21bbc7ab2a9b8c936bd6e80'/>
<id>urn:sha1:3fbf9689b652e230e21bbc7ab2a9b8c936bd6e80</id>
<content type='text'>
mkimage limits the length of the file paths in can deal with to 256
characters. Turns out that in automated builds by asu we break this
limit, so increase it to 1024 characters.

Signed-off-by: Daniel Golle &lt;daniel@makrotopia.org&gt;
</content>
</entry>
<entry>
<title>tools/mkimage: update to 2022.01</title>
<updated>2022-02-28T23:08:08Z</updated>
<author>
<name>Huangbin Zhan</name>
</author>
<published>2022-02-23T14:51:09Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/aparcar/commit/?id=4a19cf3bc7caa8e1010dc5d2f6fc4411349ae6e4'/>
<id>urn:sha1:4a19cf3bc7caa8e1010dc5d2f6fc4411349ae6e4</id>
<content type='text'>
- enable dot config
- enable openwrt verbose
- add bison as dependency to avoid failure
```
  bison -oscripts/kconfig/zconf.tab.c -t -l scripts/kconfig/zconf.y
bison: /builder/shared-workdir/build/staging_dir/host/share/bison/m4sugar/m4sugar.m4: cannot open: No such file or directory
```

Signed-off-by: Huangbin Zhan &lt;zhanhb88@gmail.com&gt;
</content>
</entry>
<entry>
<title>tools/mkimage: update to 2021.10</title>
<updated>2021-12-27T12:51:41Z</updated>
<author>
<name>Huangbin Zhan</name>
</author>
<published>2021-11-26T00:38:31Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/aparcar/commit/?id=b6385a36680b6924239cbc6766a253cab45db8d9'/>
<id>urn:sha1:b6385a36680b6924239cbc6766a253cab45db8d9</id>
<content type='text'>
Changelog:

 - upstream now needs OpenSSL in order to be able to sign FITs. See:
commit cb9faa6f98ae ("tools: Use a single target-independent config to enable OpenSSL")

 - removes upstream patches.

Link: https://github.com/u-boot/u-boot/commit/cb9faa6f98ae56d70d59505dad290dd3d381cb7b
Tested-by: Sergey V. Lobanov &lt;sergey@lobanov.in&gt;
Signed-off-by: Huangbin Zhan &lt;zhanhb88@gmail.com&gt;
Signed-off-by: Christian Lamparter &lt;chunkeey@gmail.com&gt;
</content>
</entry>
<entry>
<title>tools/mkimage: fix build on MacOS arm64</title>
<updated>2021-12-06T22:36:35Z</updated>
<author>
<name>Sergey V. Lobanov</name>
</author>
<published>2021-12-02T16:02:23Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/aparcar/commit/?id=8261b85844a0018c6c79e10c1abb581aca102e45'/>
<id>urn:sha1:8261b85844a0018c6c79e10c1abb581aca102e45</id>
<content type='text'>
Fixed -no-pie compilation warning on MacOS
Fixed errors related to using absolute addressing on MacOS arm64

Based on upstream patch from Jessica Clarke and suggestions from Ronny Kotzschmar

Link to original patch and discussion:
https://github.com/u-boot/u-boot/commit/3b142045e8a7f0ab17b6099e9226296af45967d0

Signed-off-by: Sergey V. Lobanov &lt;sergey@lobanov.in&gt;
</content>
</entry>
</feed>
