<feed xmlns='http://www.w3.org/2005/Atom'>
<title>staging/rmilecki/package/base-files, branch master</title>
<subtitle>Rafal Mileckis staging tree</subtitle>
<id>https://git.openwrt.org/openwrt/staging/rmilecki/atom?h=master</id>
<link rel='self' href='https://git.openwrt.org/openwrt/staging/rmilecki/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/rmilecki/'/>
<updated>2021-03-06T10:30:06Z</updated>
<entry>
<title>treewide: remove execute bit and shebang from board.d files</title>
<updated>2021-03-06T10:30:06Z</updated>
<author>
<name>Adrian Schmutzler</name>
</author>
<published>2021-02-26T13:43:50Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/rmilecki/commit/?id=85b1f4d8ca2d501664acce471117dc612bb69d82'/>
<id>urn:sha1:85b1f4d8ca2d501664acce471117dc612bb69d82</id>
<content type='text'>
So far, board.d files were having execute bit set and contained a
shebang. However, they are just sourced in board_detect, with an
apparantly unnecessary check for execute permission beforehand.

Replace this check by one for existance and make the board.d files
"normal" files, as would be expected in /etc anyway.

Note:

This removes an apparantly unused '#!/bin/sh /etc/rc.common' in
target/linux/bcm47xx/base-files/etc/board.d/01_network

Signed-off-by: Adrian Schmutzler &lt;freifunk@adrianschmutzler.de&gt;
</content>
</entry>
<entry>
<title>base-files: add new application led trigger backend</title>
<updated>2021-03-05T10:10:06Z</updated>
<author>
<name>Florian Eckert</name>
</author>
<published>2020-02-05T08:23:27Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/rmilecki/commit/?id=dec14ac436325abddd0ded06f34e95425fc9a75e'/>
<id>urn:sha1:dec14ac436325abddd0ded06f34e95425fc9a75e</id>
<content type='text'>
For now we have only kernel LED trigger support. With this change it is now
possible to use application triggers.

If we configure a LED with a non kernel trigger, then we check on every
restart and boot of the LED service if we have this trigger as an application
in "/usr/libexec/led-trigger". If this file with the name is found, then we
execute this to init the LED.

Possible use cases are:

- Start/Stop/Restart an application led trigger service for this led
- Init a LED that is configured by a hotplug script (VPN tunnel established)

Signed-off-by: Florian Eckert &lt;fe@dev.tdt.de&gt;
</content>
</entry>
<entry>
<title>treewide: fix spelling 'seperate' -&gt; 'separate'</title>
<updated>2021-02-28T23:59:21Z</updated>
<author>
<name>Daniel Golle</name>
</author>
<published>2021-02-28T23:58:10Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/rmilecki/commit/?id=ebcb4f1d0a091d1fa87d6aa04ecae355ef23ef22'/>
<id>urn:sha1:ebcb4f1d0a091d1fa87d6aa04ecae355ef23ef22</id>
<content type='text'>
This popular spelling mistake was also introduced by myself lately.
Fix it everywhere.

Signed-off-by: Daniel Golle &lt;daniel@makrotopia.org&gt;
</content>
</entry>
<entry>
<title>base-files: add support for restoring config from tmpfs</title>
<updated>2021-02-28T00:09:09Z</updated>
<author>
<name>Daniel Golle</name>
</author>
<published>2021-02-27T22:21:09Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/rmilecki/commit/?id=84a339f01523c7892f014cc5439c66b43ba6b6ff'/>
<id>urn:sha1:84a339f01523c7892f014cc5439c66b43ba6b6ff</id>
<content type='text'>
Instead of only relying in /sysupgrade.tgz being present in rootfs to
restore configuration, also grab /tmp/sysupgrade.tar which may have
magically gotten there during preinit...

Signed-off-by: Daniel Golle &lt;daniel@makrotopia.org&gt;
</content>
</entry>
<entry>
<title>base-files: remove unneeded '$' signs in nand.sh</title>
<updated>2021-02-24T11:42:02Z</updated>
<author>
<name>Daniel Golle</name>
</author>
<published>2021-02-24T11:40:50Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/rmilecki/commit/?id=287bd78e6f8af68fc3095839c7b70842cf3ddb4c'/>
<id>urn:sha1:287bd78e6f8af68fc3095839c7b70842cf3ddb4c</id>
<content type='text'>
When using Shell arithmetric evaluation via $((..)) the variables in
the expression do not need to be prefixed by the '$' sign.

Signed-off-by: Daniel Golle &lt;daniel@makrotopia.org&gt;
</content>
</entry>
<entry>
<title>sysupgrade-nand: allow limiting rootfs_data by setting env variable</title>
<updated>2021-02-24T01:35:20Z</updated>
<author>
<name>Daniel Golle</name>
</author>
<published>2021-02-17T15:17:49Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/rmilecki/commit/?id=5c10f26c28031c0d7e72b672623727adb5df7b2d'/>
<id>urn:sha1:5c10f26c28031c0d7e72b672623727adb5df7b2d</id>
<content type='text'>
Check if firmware environment variable 'rootfs_data_max' exists and is
set to a numerical value greater than 0. If so, limit rootfs_data
volume to that size instead of using the maximum available size.

This is useful on devices with lots of flash where users may want to
have eg. a volume for persistent logs and statistics or for external
applications/containers. Persistence on rootfs overlay is limited by
the size of memory available during the sysugprade process as that
data needs to be copied to RAM while the volume is being recreated
during sysupgrade. Hence it is unsuitable for keeping larger amounts
of data accross upgrade which makes additional volume(s) for
application data desirable.

Signed-off-by: Daniel Golle &lt;daniel@makrotopia.org&gt;
</content>
</entry>
<entry>
<title>image: add support for building FIT image with filesystem</title>
<updated>2021-02-24T01:35:20Z</updated>
<author>
<name>Daniel Golle</name>
</author>
<published>2021-02-15T14:37:17Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/rmilecki/commit/?id=e6aac8d98f5663be99163f9e61dad23ad657b7ed'/>
<id>urn:sha1:e6aac8d98f5663be99163f9e61dad23ad657b7ed</id>
<content type='text'>
Allow for single (external-data) FIT image to hold kernel, dtb and
squashfs. In that way, the bootloader verifies the system integrity
including the rootfs, because what's the point of checking that the
hash of the kernel is correct if it won't boot in case of squashfs
being corrupted? Better allow bootloader to check everything needed
to make it at least up to failsafe mode. As a positive side effect
this change also makes the sysupgrade process on nand potentially
much easier as it is now.
In short: mkimage has a parameter '-E' which allows generating FIT
images with 'external' data rather than embedding the data into the
device-tree blob itself. In this way, the FIT structure itself remains
small and can be parsed easily (rather than having to page around
megabytes of image content). This patch makes use of that and adds
support for adding sub-images of type 'filesystem' which are used to
store the squashfs. Now U-Boot can verify the whole OS and the new
partition parsers added in the Linux kernel can detect the filesystem
sub-images, create partitions for them, and select the active rootfs
volume based on the configuration in FIT (passing configuration via
device tree could be implemented easily at a later stage).

This new FIT partition parser works for NOR flash (on top of mtdblock),
NAND flash (on top of ubiblock) as well as classic block devices
(ie. eMMC, SDcard, SATA, NVME, ...).
It could even be used to mount such FIT images via `losetup -P` on a
user PC if this patch gets included in Linux upstream one day ;)

Signed-off-by: John Crispin &lt;john@phrozen.org&gt;
Signed-off-by: Daniel Golle &lt;daniel@makrotopia.org&gt;
</content>
</entry>
<entry>
<title>base-files: use hwclock --systz</title>
<updated>2021-02-14T14:15:32Z</updated>
<author>
<name>Rosen Penev</name>
</author>
<published>2021-02-01T00:15:52Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/rmilecki/commit/?id=157cd0bd97bcfec8a34d4ebb558f37bee4f0515f'/>
<id>urn:sha1:157cd0bd97bcfec8a34d4ebb558f37bee4f0515f</id>
<content type='text'>
The date -k patch is non standard and will be removed in the next
commit.

Tested behavior to be identical with a simple C program:

 #define _GNU_SOURCE
 #include &lt;unistd.h&gt;
 #include &lt;stdio.h&gt;
 #include &lt;sys/time.h&gt;
 #include &lt;sys/syscall.h&gt;

int main()
{
        struct timezone tt;
	struct timezone tz;

        int a = syscall(SYS_gettimeofday, NULL, &amp;tt);
        int b = gettimeofday(NULL, &amp;tz);
        printf("%d - %d, %d\n", a, tt.tz_minuteswest, tt.tz_dsttime);
        printf("%d - %d, %d\n", b, tz.tz_minuteswest, tz.tz_dsttime);
}

Signed-off-by: Rosen Penev &lt;rosenp@gmail.com&gt;
</content>
</entry>
<entry>
<title>base-files: mount pstore if present</title>
<updated>2021-01-29T21:26:36Z</updated>
<author>
<name>Brian Norris</name>
</author>
<published>2021-01-23T23:08:00Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/rmilecki/commit/?id=95b30f84d274ababc99a4e17aa8dee3ce643c2a1'/>
<id>urn:sha1:95b30f84d274ababc99a4e17aa8dee3ce643c2a1</id>
<content type='text'>
Pstore (persistent store) can be used to stash debug information (kernel
console, panics, ftrace) across reboots or crashes. If the filesystem is
present, mount it.

Signed-off-by: Brian Norris &lt;computersforpeace@gmail.com&gt;
</content>
</entry>
<entry>
<title>base-files: remove execute bit and shebang from functions.sh</title>
<updated>2021-01-29T13:30:32Z</updated>
<author>
<name>Adrian Schmutzler</name>
</author>
<published>2021-01-25T11:48:43Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/rmilecki/commit/?id=396a35dd51f1d58c051d0c1f1100e44950933d3b'/>
<id>urn:sha1:396a35dd51f1d58c051d0c1f1100e44950933d3b</id>
<content type='text'>
/lib/functions.sh was executable for no obvious reason and its
execute property was even checked in package-ipkg.mk just to
source it afterwards.

Remove the execute bit and shebang as this is clearly a library.

Signed-off-by: Adrian Schmutzler &lt;freifunk@adrianschmutzler.de&gt;
Reviewed-by: Philip Prindeville &lt;philipp@redfish-solutions.com&gt;
</content>
</entry>
</feed>
