<feed xmlns='http://www.w3.org/2005/Atom'>
<title>staging/pepe2k, branch v21.02.1</title>
<subtitle>Staging tree of Piotr Dymacz</subtitle>
<id>https://git.openwrt.org/openwrt/staging/pepe2k/atom?h=v21.02.1</id>
<link rel='self' href='https://git.openwrt.org/openwrt/staging/pepe2k/atom?h=v21.02.1'/>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/pepe2k/'/>
<updated>2021-10-25T19:44:54Z</updated>
<entry>
<title>OpenWrt v21.02.1: adjust config defaults</title>
<updated>2021-10-25T19:44:54Z</updated>
<author>
<name>Hauke Mehrtens</name>
</author>
<published>2021-10-25T19:44:54Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/pepe2k/commit/?id=b4d7885af70a42df7577157b96f941500bd17bfb'/>
<id>urn:sha1:b4d7885af70a42df7577157b96f941500bd17bfb</id>
<content type='text'>
Signed-off-by: Hauke Mehrtens &lt;hauke@hauke-m.de&gt;
</content>
</entry>
<entry>
<title>ipq40xx: ar40xx: reset port status register</title>
<updated>2021-10-24T09:01:35Z</updated>
<author>
<name>David Bauer</name>
</author>
<published>2021-08-13T21:28:44Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/pepe2k/commit/?id=88151b8303f29f18e8b037076628fd82eda0978a'/>
<id>urn:sha1:88151b8303f29f18e8b037076628fd82eda0978a</id>
<content type='text'>
This resolves incosnsitencies of the configured RX / TX flow control
modes between different boards or bootloaders.

Signed-off-by: David Bauer &lt;mail@david-bauer.net&gt;
(cherry picked from commit 4d81f087715524994448ecaefd3ca87c8ba7e0a3)
</content>
</entry>
<entry>
<title>wolfssl: fix compile when enable-devcrypto is set</title>
<updated>2021-10-23T10:38:01Z</updated>
<author>
<name>Ivan Pavlov</name>
</author>
<published>2021-10-15T05:11:10Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/pepe2k/commit/?id=23778f067a5aa8d2fa7e15244521774bf849ae6b'/>
<id>urn:sha1:23778f067a5aa8d2fa7e15244521774bf849ae6b</id>
<content type='text'>
fixing linking error when --enable-devcrypto=yes
fixes: 7d92bb050961 wolfssl: update to 4.8.1-stable

Signed-off-by: Ivan Pavlov &lt;AuthorReflex@gmail.com&gt;
(cherry picked from commit be3e260f92643a841f4f83b03cbb07b9a26cff66)
</content>
</entry>
<entry>
<title>wolfssl: remove --enable-sha512 configure switch</title>
<updated>2021-10-23T10:37:51Z</updated>
<author>
<name>Andre Heider</name>
</author>
<published>2021-10-02T08:40:00Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/pepe2k/commit/?id=3f8adcb215edaa22448bdbf7cb12de9d95316671'/>
<id>urn:sha1:3f8adcb215edaa22448bdbf7cb12de9d95316671</id>
<content type='text'>
It's the default anyway and this just looks confusing, as if it wasn't.

Switch to AUTORELEASE while at it.

The binary size is unchanged.

Signed-off-by: Andre Heider &lt;a.heider@gmail.com&gt;
(cherry picked from commit 7cb5af30f48d6788cd471138820a772610a7f8e0)
</content>
</entry>
<entry>
<title>wolfssl: always build with --enable-reproducible-build</title>
<updated>2021-10-23T10:37:18Z</updated>
<author>
<name>Andre Heider</name>
</author>
<published>2021-10-02T08:50:49Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/pepe2k/commit/?id=249478ec48509ba42827867fd15372478f9f42d2'/>
<id>urn:sha1:249478ec48509ba42827867fd15372478f9f42d2</id>
<content type='text'>
This gates out anything that might introduce semantically frivolous jitter,
maximizing chance of identical object files.

The binary size shrinks by 8kb:
1244352 staging_dir/target-mipsel_24kc_musl/usr/lib/libwolfssl.so.4.8.1.39c36f2f
1236160 staging_dir/target-mipsel_24kc_musl/usr/lib/libwolfssl.so.4.8.1.39c36f2f

Signed-off-by: Andre Heider &lt;a.heider@gmail.com&gt;
(cherry picked from commit c76300707e8d705d9efc7ed4bb1b7449d0a5fe00)
</content>
</entry>
<entry>
<title>ath79: mikrotik: use 64 KiB SPI NOR erase sectors</title>
<updated>2021-10-23T02:34:11Z</updated>
<author>
<name>Roger Pueyo Centelles</name>
</author>
<published>2021-08-31T14:45:17Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/pepe2k/commit/?id=23cd9fafa89a8058a88763cc0526a1e85a9f7ebb'/>
<id>urn:sha1:23cd9fafa89a8058a88763cc0526a1e85a9f7ebb</id>
<content type='text'>
This patch removes CONFIG_MTD_SPI_NOR_USE_4K_SECTORS from the default
symbols for the ath79/mikrotik target.

MikroTik devices hold some of their user-configurable settings in the
soft_config partition, which is typically sized 4 KiB, of the SPI NOR
flash memory. Previously, in the ar71xx target, it was possible to use
64 KiB erase sectors but also smaller 4 KiB ones when needed. This is
no longer the case in ath79 with newer kernels so, to be able to write
to these 4 KiB small partitions without erasing 60 KiB around, the
CONFIG_MTD_SPI_NOR_USE_4K_SECTORS symbol was added to the defaults.
However, this ended up making sysupgrade images which were built with
64 KiB size blocks not to keep settings (e.g., the files under
/etc/config/) over the flashing process.

Using 4 KiB erase sector size on the sysupgrade images (by setting
BLOCKSIZE = 4k) allows keeping settings over a flashing process, but
renders the process terribly slow, possibly causing a user to
mistakenly force a manual device reboot while the process is still on-
going. Instead, ditching the 4 KiB erase sectors for the default
64 KiB erase size provides normal SPI write speed and sysupgrade times,
at the expense of not being able to modify the soft_config partition
(which is rarely a required thing).

An OpenWrt patch for MTD_SPI_NOR_USE_4K_SECTORS_LIMIT may once have
allowed to use different per-partition erase sector sizes. Due to
changes on recent kernels it now only works on a per-device basis.
Also, partial eraseblock write can be performed in ath79 with kernels
5.4 and lower, by copying the blocks from the 64 KiB, erasing the whole
sector and restoring those blocks not meant to be modified. A kernel
bump had that patch broken for a long time, but got fixed in bf2870c.

Note: the settings in the soft_config partition can be reset to their
defaults by holding the reset button for 5 seconds (and less than 10
seconds) at device boot.

Fixes: FS#3492 (sysupgrade […] loses settings...)
Fixes: a66eee63368e (ath79: add mikrotik subtarget)

Signed-off-by: Roger Pueyo Centelles &lt;roger.pueyo@guifi.net&gt;
(cherry picked from commit 68d91f08edd0efd47841a2e53d3437d570a61612)
</content>
</entry>
<entry>
<title>wolfssl: update to 4.8.1-stable</title>
<updated>2021-10-23T02:34:11Z</updated>
<author>
<name>Ivan Pavlov</name>
</author>
<published>2021-09-14T15:06:32Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/pepe2k/commit/?id=16414718f9ae57f294a8a9f70f766e0d170fae05'/>
<id>urn:sha1:16414718f9ae57f294a8a9f70f766e0d170fae05</id>
<content type='text'>
Changes from 4.7.0:
  Fix one high (OCSP verification issue) and two low vulnerabilities
  Improve compatibility layer
  Other improvements and fixes

For detailed changes refer to https://github.com/wolfSSL/wolfssl/releases

Signed-off-by: Ivan Pavlov &lt;AuthorReflex@gmail.com&gt;
(cherry picked from commit 7d92bb0509615550b98e2dc71091073c8258d564)
[Added patch to allow compilation with libtool 2.4]
Signed-off-by: Eneas U de Queiroz &lt;cotequeiroz@gmail.com&gt;
</content>
</entry>
<entry>
<title>wolfssl: fix build with GCC 10 on 32 x86 targets</title>
<updated>2021-10-23T02:34:11Z</updated>
<author>
<name>Stijn Tintel</name>
</author>
<published>2021-09-14T15:06:31Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/pepe2k/commit/?id=5a02760c8f9c3b5ff2af8e6ba457b3a91d27d4e1'/>
<id>urn:sha1:5a02760c8f9c3b5ff2af8e6ba457b3a91d27d4e1</id>
<content type='text'>
Backport upstream patch to fix build with GCC 10 on 32 x86 targets.

Signed-off-by: Stijn Tintel &lt;stijn@linux-ipv6.be&gt;
(cherry picked from commit 718a4f47806da8f68cb8f1fe2ebecf403e14ae96)
</content>
</entry>
<entry>
<title>layerscape: Add missing config option</title>
<updated>2021-10-22T20:26:02Z</updated>
<author>
<name>Hauke Mehrtens</name>
</author>
<published>2021-10-22T19:30:02Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/pepe2k/commit/?id=24b23ed96a5570ce8ddd14f6f989f79d732acbae'/>
<id>urn:sha1:24b23ed96a5570ce8ddd14f6f989f79d732acbae</id>
<content type='text'>
This option is not set when building the target.
In master this is also unset.

Signed-off-by: Hauke Mehrtens &lt;hauke@hauke-m.de&gt;
</content>
</entry>
<entry>
<title>layerscape: Fix build in dtb</title>
<updated>2021-10-22T20:25:41Z</updated>
<author>
<name>Hauke Mehrtens</name>
</author>
<published>2021-10-22T20:09:16Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/pepe2k/commit/?id=7bf7f78891647cefd340a3f91ecaa7b62705f3f0'/>
<id>urn:sha1:7bf7f78891647cefd340a3f91ecaa7b62705f3f0</id>
<content type='text'>
This fixes a kernel build problem.
The removed parts of the patch are already applied upstream.

Fixes: b4ed8a92751f ("kernel: bump 5.4 to 5.4.154")
Signed-off-by: Hauke Mehrtens &lt;hauke@hauke-m.de&gt;
(cherry picked from commit 9501ce909f54b87dab95f17c0408a4962365e130)
</content>
</entry>
</feed>
