<feed xmlns='http://www.w3.org/2005/Atom'>
<title>staging/blocktrron/scripts, branch master</title>
<subtitle>Staging tree of David Bauer</subtitle>
<id>https://git.openwrt.org/openwrt/staging/blocktrron/atom?h=master</id>
<link rel='self' href='https://git.openwrt.org/openwrt/staging/blocktrron/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/blocktrron/'/>
<updated>2025-11-12T11:05:53Z</updated>
<entry>
<title>scripts: feeds: Don’t hardcode IS_TTY</title>
<updated>2025-11-12T11:05:53Z</updated>
<author>
<name>Ernestas Kulik</name>
</author>
<published>2025-11-12T08:16:30Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/blocktrron/commit/?id=fd7e43d429a370665795fb14c859c046c761e4e9'/>
<id>urn:sha1:fd7e43d429a370665795fb14c859c046c761e4e9</id>
<content type='text'>
When building in environments that set IS_TTY, the feeds script does not
honor it and passes a hardcoded value to scan.mk, causing unwanted
control characters to appear in stdout.

This commit addresses the issue by checking IS_TTY and MAKE_TERMOUT
variables and uses their values if defined.

Closes #8039

Signed-off-by: Ernestas Kulik &lt;ernestas.k@iconn-networks.com&gt;
Link: https://github.com/openwrt/openwrt/pull/20743
Signed-off-by: Christian Marangi &lt;ansuelsmth@gmail.com&gt;
</content>
</entry>
<entry>
<title>scripts/make-index-json: ensure that manifest output is in opkg format</title>
<updated>2025-11-01T18:42:20Z</updated>
<author>
<name>Eric Fahlgren</name>
</author>
<published>2025-09-19T17:01:07Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/blocktrron/commit/?id=3b21f97641f9a03a01d1a40bc5ed740bae7a7c27'/>
<id>urn:sha1:3b21f97641f9a03a01d1a40bc5ed740bae7a7c27</id>
<content type='text'>
Certain existing tooling, such as 'package-metadata.pl', are written
to accept the output of 'opkg list' with package manifest delimited
by '-'.  The 'make-index-json.py --manifest' output was emulating
the 'apk list --manifest' format without the delimiting dash,
thus breaking these legacy tools.

We fix this by adding the dash to the manifest output, which allows
all existing tooling to process the output irrespective of whether
the build system uses opkg or apk.

Signed-off-by: Eric Fahlgren &lt;ericfahlgren@gmail.com&gt;
Link: https://github.com/openwrt/openwrt/pull/20094
Signed-off-by: Robert Marko &lt;robimarko@gmail.com&gt;
</content>
</entry>
<entry>
<title>scripts/mkits.sh: move out .pagesync generation for RootFS blob</title>
<updated>2025-10-23T16:14:01Z</updated>
<author>
<name>Christian Marangi</name>
</author>
<published>2025-10-23T13:31:46Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/blocktrron/commit/?id=c70894c855e54624b918ab50c9afa53301c462d4'/>
<id>urn:sha1:c70894c855e54624b918ab50c9afa53301c462d4</id>
<content type='text'>
It's expected the mkits.sh script to generate only the relevant DTS
entry and have all the blob already prepared to use for mkimage.

This is not the case for the RootFS case where the script generates a
.pagesync with the dd command.

To better handle this, drop the dd command and instead error out if the
.pagesync blob is not found if RootFS is used.

Adapt the generic fit build in image-commands.mk to call the dd for
.pagesync right before mkits.sh.

Link: https://github.com/openwrt/openwrt/pull/20492
Signed-off-by: Christian Marangi &lt;ansuelsmth@gmail.com&gt;
</content>
</entry>
<entry>
<title>scripts/feeds: implement support for --root option</title>
<updated>2025-10-13T09:47:07Z</updated>
<author>
<name>Christian Marangi</name>
</author>
<published>2025-10-12T23:59:52Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/blocktrron/commit/?id=e112fd8e59e37ae323fdaebb74bdd6084176d8e4'/>
<id>urn:sha1:e112fd8e59e37ae323fdaebb74bdd6084176d8e4</id>
<content type='text'>
Some feeds might need to set the source for their packages in a
different directory than the cloned one.

For example a feed "test" might be an entire repository and the relevant
packages that wants to be included are in the directory "foo".

In such scenario the source info in the package will result in something
like "feeds/test/foo/network/dnsmasq" instead of an expected entry like
"feeds/test/network/dnsmasq".

To give a more real-world example, this problem is currently present
with OpenWrt SDK where the SDK clone the entire OpenWrt core repository
as "base" feeds but the package are present in the "package" directory.

This cause every package to have the source entry set to
"feeds/base/package/..." conflicting with what a non-SDK build do with
setting the source entry to "feeds/base/..."

To solve this, actually enable support for "flags" in the feeds script
and implement a new option "--root" to set the root directory for the
defined feed to an inner directory.

The "flags" in the feed script are no more than argument option that can
be defined right after the "src-" type in the feed.conf file.

This feature was partially implemented but never actually used for
anything keeping it dormant with all the core piece there (the pattern
regex always accounted for these extra option but they were never passed
to the relevant functions)

An example of the "--root" flag is the following:

src-git --root=package base https://git.openwrt.org/openwrt/openwrt.git;main

With "--root" defined, the script will append "_root" to the feed name
clone directory and will create a symbolic link named with the feed name
and pointing to the feed name clone directory + the value in root.

From the previous example:

feed name: base -&gt; clone directory: base_root
symbolic link: base -&gt; base_root/package

The script internally reference the "_root" directory for every update
operation and OpenWrt build system transparently use the feed name
directory to reference feed packages producing consistent source info
entry.

Link: https://github.com/openwrt/openwrt/pull/20396
Signed-off-by: Christian Marangi &lt;ansuelsmth@gmail.com&gt;
</content>
</entry>
<entry>
<title>ramips: add support for Plasma Cloud PAX1800-Lite</title>
<updated>2025-10-04T18:30:36Z</updated>
<author>
<name>Sven Eckelmann (Plasma Cloud)</name>
</author>
<published>2023-10-12T11:57:32Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/blocktrron/commit/?id=c7c54f313425d8f05203d141d056a104ee05c512'/>
<id>urn:sha1:c7c54f313425d8f05203d141d056a104ee05c512</id>
<content type='text'>
Plasma Cloud PAX1800-Lite is a dual-band Wi-Fi 6 router, based on MediaTek
MT7621A + MT79x5D platform.

Specifications:

- SOC:      MT7621AT (880 MHz)
- DRAM:     DDR3 448 MiB (Nanya NT5CC256M16DP-DI)
- Flash:    2 MiB SPI NOR (S25FL016K) + 128 MB SPI NAND (W25N02KVZEIR)
- Ethernet: 1x 10/100/1000 Mbps (SOC's built-in switch, with PoE+)
- Wi-Fi:    2x2:2 2.4/5 GHz (MT7905DAN + MT7975DN)
            (MT7905DAN doesn't support background DFS scan/BT)
- LED:      tri-color LED for status (red, blue, green)
- Buttons:  1x (reset)
- Antenna:  4x internal, non-detachable omnidirectional
- UART:     1x 4-pin (2.54 mm pitch, marked as "3V3 G/RX GND W/TX")
- Power:    12 V DC/2 A (DC jack)

MAC addresses:

WAN:     54:9C:27:xx:xx:00 (factory 0x3fff4, device label)
2.4 GHz: 54:9C:27:xx:xx:02 (factory 0x4, device label +2)
5 GHz:   54:9C:27:xx:xx:08 (factory 0xa, device label +8)

Flashing instructions:
======================

Various methods can be used to install the actual image on the flash.
Two easy ones are:

ap51-flash
----------

The tool ap51-flash (https://github.com/ap51-flash/ap51-flash) should be
used to transfer the image to the u-boot when the device boots up.

initramfs from TFTP
-------------------

The serial console (115200 8N1) must be used to access the u-boot shell
during bootup. It can then be used to first boot up the initramfs image
from a TFTP server (here with the IP 192.168.1.21):

    setenv serverip 192.168.1.21
    setenv ipaddr 192.168.1.1
    tftpboot 0x83001000 &lt;filename-of-initramfs-kernel&gt;.bin &amp;&amp; bootm $fileaddr

The actual sysupgrade image can then be transferred (on the LAN port) to the
device via

    scp &lt;filename-of-squashfs-sysupgrade&gt;.bin root@192.168.1.1:/tmp/

On the device, the sysupgrade must then be started using

    sysupgrade -n /tmp/&lt;filename-of-squashfs-sysupgrade&gt;.bin

Signed-off-by: Sven Eckelmann (Plasma Cloud) &lt;se@simonwunderlich.de&gt;
Link: https://github.com/openwrt/openwrt/pull/20152
Signed-off-by: Hauke Mehrtens &lt;hauke@hauke-m.de&gt;
</content>
</entry>
<entry>
<title>scripts/patch-kernel.sh: do not try to check files after patch</title>
<updated>2025-09-29T11:33:07Z</updated>
<author>
<name>George Tsiamasiotis</name>
</author>
<published>2025-09-23T20:11:19Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/blocktrron/commit/?id=75ca6bafd614efd1427a979d28d551af775b8e5d'/>
<id>urn:sha1:75ca6bafd614efd1427a979d28d551af775b8e5d</id>
<content type='text'>
Since we are not using patch -b, *.orig files are only created when
there are conflicts, or never according to posix patch.

As such, it doesn't really make sense to always delete *.orig files
presuming they are patch backups, even if they are patch backups.
Doing so is both deleting potentially useful information for failed
patch applications and creating hard to diagnose bugs [1].

In a similar vein, checking for *.rej files does not add any value
since we're already checking the patch command's return code.

[1]: https://github.com/openwrt/packages/issues/27485

Signed-off-by: George Tsiamasiotis &lt;george@tsiamasiotis.gr&gt;
Link: https://github.com/openwrt/openwrt/pull/20141
Signed-off-by: Robert Marko &lt;robimarko@gmail.com&gt;
</content>
</entry>
<entry>
<title>build: parsing "git log" breaks with gpg signature verification</title>
<updated>2025-09-23T19:49:54Z</updated>
<author>
<name>Bjørn Mork</name>
</author>
<published>2024-12-27T11:43:18Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/blocktrron/commit/?id=ae9c9d0f8e41621c1bde94a43ec463052fa58c8a'/>
<id>urn:sha1:ae9c9d0f8e41621c1bde94a43ec463052fa58c8a</id>
<content type='text'>
Parsing "git log" is fragile.  The actual output depends on both global and
local configuration files. Enabling "log.showSignature" makes "git log" prefix
signed commits with multiple lines of gpg verify output, regardless of the
configured log format.

Add "--no-show-signature" to "git log" commands to work around this particular
issue.

Signed-off-by: Bjørn Mork &lt;bjorn@mork.no&gt;
Link: https://github.com/openwrt/openwrt/pull/20127
Signed-off-by: Robert Marko &lt;robimarko@gmail.com&gt;
</content>
</entry>
<entry>
<title>download: add support for gitweb snapshots</title>
<updated>2025-07-26T12:38:08Z</updated>
<author>
<name>Michael Pratt</name>
</author>
<published>2025-05-31T18:00:45Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/blocktrron/commit/?id=685fc753a7fd0e87cf61204620348ec0b40ba426'/>
<id>urn:sha1:685fc753a7fd0e87cf61204620348ec0b40ba426</id>
<content type='text'>
When downloading a snapshot archive from gitweb,
the filename is not part of the URL,
and adding the filename to the URL causes errors.

The gitweb API exclusively uses query parameters
instead of paths in order to execute snapshot downloads.

Add a condition to the Perl download script
that removes the filename if the relevant
query parameter matches in the URL.

Also, to reduce server load of the original sources
try the Openwrt CDN servers first for these downloads.

Even though snapshot downloads are not ideal
due to the impact on the source's server health,
they are better for download performance than using git only.
Therefore, attempting it last will reduce the impact
and thus encourage maintainers to keep the option enabled.

This change is partly inspired by a conversation linked below
about snapshot downloads and server performance issues
which led to the feature being disabled for a particular server.

Link: https://lists.gnu.org/archive/html/bug-gnulib/2024-12/msg00124.html
Signed-off-by: Michael Pratt &lt;mcpratt@pm.me&gt;
Link: https://github.com/openwrt/openwrt/pull/16522
Signed-off-by: Robert Marko &lt;robimarko@gmail.com&gt;
</content>
</entry>
<entry>
<title>projectsmirrors: remove kernel mirror ftp.riken.jp</title>
<updated>2025-07-25T23:05:44Z</updated>
<author>
<name>Shiji Yang</name>
</author>
<published>2025-07-24T10:50:50Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/blocktrron/commit/?id=71fa099ef7f4f425a65d12ce2acbad4aba00dea4'/>
<id>urn:sha1:71fa099ef7f4f425a65d12ce2acbad4aba00dea4</id>
<content type='text'>
This mirror has not been synchronized for over a year.

Signed-off-by: Shiji Yang &lt;yangshiji66@outlook.com&gt;
Link: https://github.com/openwrt/openwrt/pull/19509
Signed-off-by: Hauke Mehrtens &lt;hauke@hauke-m.de&gt;
</content>
</entry>
<entry>
<title>projectsmirrors: update Apache mirror apache.cs.utah.edu</title>
<updated>2025-07-25T23:05:43Z</updated>
<author>
<name>Shiji Yang</name>
</author>
<published>2025-07-24T10:50:50Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/blocktrron/commit/?id=f696a1874376d75ee939006b69388d88fc341b67'/>
<id>urn:sha1:f696a1874376d75ee939006b69388d88fc341b67</id>
<content type='text'>
The original URL no longer works.

Signed-off-by: Shiji Yang &lt;yangshiji66@outlook.com&gt;
Link: https://github.com/openwrt/openwrt/pull/19509
Signed-off-by: Hauke Mehrtens &lt;hauke@hauke-m.de&gt;
</content>
</entry>
</feed>
