<feed xmlns='http://www.w3.org/2005/Atom'>
<title>staging/robimarko/package/base-files, branch master</title>
<subtitle>Staging tree of Robert Marko</subtitle>
<id>https://git.openwrt.org/openwrt/staging/robimarko/atom?h=master</id>
<link rel='self' href='https://git.openwrt.org/openwrt/staging/robimarko/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/robimarko/'/>
<updated>2024-02-12T19:46:51Z</updated>
<entry>
<title>base-files: move uci_set_poe() to uci-defaults.sh</title>
<updated>2024-02-12T19:46:51Z</updated>
<author>
<name>Sander Vanheule</name>
</author>
<published>2024-01-24T10:20:08Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/robimarko/commit/?id=6f83a708c8f1df14da9a24609d32bd7263d1798b'/>
<id>urn:sha1:6f83a708c8f1df14da9a24609d32bd7263d1798b</id>
<content type='text'>
PoE devices in the realtek target have the possibility to add PSE info
to the board description via 02_network. Make this available for all
targets, by moving the uci_set_poe() function to the globally available
uci-default.sh script.

Signed-off-by: Sander Vanheule &lt;sander@svanheule.net&gt;
</content>
</entry>
<entry>
<title>base-files/leds: add setting the LED color via uci</title>
<updated>2024-02-07T14:34:43Z</updated>
<author>
<name>Florian Eckert</name>
</author>
<published>2024-02-01T11:51:02Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/robimarko/commit/?id=c6fabd0bc3354099bcfc73aa4064139b23fb509d'/>
<id>urn:sha1:c6fabd0bc3354099bcfc73aa4064139b23fb509d</id>
<content type='text'>
Add the possibility that colored LEDs can also be configured via the uci.

config led 'led1'
	option name '&lt;name&gt;'
	option sysfs '&lt;path&gt;'
	option trigger 'default-on'
	option default '1'
--&gt;	option color_{$color} '&lt;0-255&gt;'

The supported names of the variable "${color}" for the selected LED can be
queried in the file with the name 'multi_index'.

Signed-off-by: Florian Eckert &lt;fe@dev.tdt.de&gt;
</content>
</entry>
<entry>
<title>base-files/leds: merging code sequences that belongs together</title>
<updated>2024-02-07T14:34:43Z</updated>
<author>
<name>Florian Eckert</name>
</author>
<published>2024-02-01T10:31:20Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/robimarko/commit/?id=3aa812d8bebdb40316d1d57150c766234f5245dd'/>
<id>urn:sha1:3aa812d8bebdb40316d1d57150c766234f5245dd</id>
<content type='text'>
Setting the trigger and checking whether the trigger can be set belong
together and should not be interrupted by other lines of code.

Signed-off-by: Florian Eckert &lt;fe@dev.tdt.de&gt;
</content>
</entry>
<entry>
<title>base-files/leds: save led color value if available</title>
<updated>2024-02-07T14:34:43Z</updated>
<author>
<name>Florian Eckert</name>
</author>
<published>2024-02-01T10:17:17Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/robimarko/commit/?id=102855b3c13e4fc6b1df4325ee51855a69874f88'/>
<id>urn:sha1:102855b3c13e4fc6b1df4325ee51855a69874f88</id>
<content type='text'>
There are monochrome LEDs that can only display one color. However, there
are also LEDs that can display multiple colors. This can be tested in the
led subsystem of the kernel if the files 'multi_index' and 'multi_intensity'
are present in the folder '/sys/class/leds/&lt;ledname&gt;'.

Until now it was not possible to reset the default color. This commit adds
the missing information in the file '/var/run/led.state' so that the bootup
color can be seen on the LED again when the LED configuration has been changed.

Signed-off-by: Florian Eckert &lt;fe@dev.tdt.de&gt;
</content>
</entry>
<entry>
<title>wifi-scripts: add new package, move wifi scripts to a single place</title>
<updated>2024-02-03T15:16:36Z</updated>
<author>
<name>Felix Fietkau</name>
</author>
<published>2024-01-26T10:03:39Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/robimarko/commit/?id=2716853132d23a35fc18cbe8b438aa70e4d2c563'/>
<id>urn:sha1:2716853132d23a35fc18cbe8b438aa70e4d2c563</id>
<content type='text'>
Signed-off-by: Felix Fietkau &lt;nbd@nbd.name&gt;
</content>
</entry>
<entry>
<title>base-files: upgrade: nand.sh: mute umount error</title>
<updated>2024-02-01T00:52:54Z</updated>
<author>
<name>Daniel Golle</name>
</author>
<published>2024-01-25T03:06:45Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/robimarko/commit/?id=efcc100ef0d6953f60c0eaf46fee3239070bcc91'/>
<id>urn:sha1:efcc100ef0d6953f60c0eaf46fee3239070bcc91</id>
<content type='text'>
Send error output of umount to /dev/null to mute error in case
ubiblock device has already been unmounted (which is usually the
case).
Gets rid of bogus error message:
umount: can't unmount /dev/ubiblock0_4: Invalid argument

Signed-off-by: Daniel Golle &lt;daniel@makrotopia.org&gt;
</content>
</entry>
<entry>
<title>base-files: functions.sh: prepend() always adds separator</title>
<updated>2024-01-15T17:41:09Z</updated>
<author>
<name>Philip Prindeville</name>
</author>
<published>2024-01-01T22:37:34Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/robimarko/commit/?id=95157dde046058f745437a37a35d8136c8c84608'/>
<id>urn:sha1:95157dde046058f745437a37a35d8136c8c84608</id>
<content type='text'>
It shouldn't gate on the value, since the value will ostensibly
always be set; instead it should depend on the variable being
prepended to being non-empty.

Fixes #14403

Signed-off-by: Philip Prindeville &lt;philipp@redfish-solutions.com&gt;
</content>
</entry>
<entry>
<title>base-files: add support for rootfs mount options from cmdline</title>
<updated>2024-01-15T15:44:29Z</updated>
<author>
<name>Christian Marangi</name>
</author>
<published>2023-09-16T15:16:04Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/robimarko/commit/?id=0b23d3608c1f01f9dc4d042b0217ee0291c0fd70'/>
<id>urn:sha1:0b23d3608c1f01f9dc4d042b0217ee0291c0fd70</id>
<content type='text'>
Add support for configuring rootfs mount options from cmdline.

Rootfs mount options can be passed by declaring in the kernel
cmdline as much options as needed prefixed with "rootfs_mount_options."

An example usage is with rootfs with F2FS filesystem to enable
compress_algorithm to reduce flash wear by compressing the files before
writing to flash.

Example usage:
"... rootfs_mount_options.compress_algorithm=zstd ..."

To pass multiple options:
"... rootfs_mount_options.compress_algorithm=zstd rootfs_mount_options.noinline_data ..."

Signed-off-by: Christian Marangi &lt;ansuelsmth@gmail.com&gt;
</content>
</entry>
<entry>
<title>base-files: execute package's "postinst" after executing uci-defaults</title>
<updated>2023-12-27T15:01:30Z</updated>
<author>
<name>Rafał Miłecki</name>
</author>
<published>2023-11-26T20:24:28Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/robimarko/commit/?id=b799dd3c705dfd95745cdd94b13d1cd2ad2367a6'/>
<id>urn:sha1:b799dd3c705dfd95745cdd94b13d1cd2ad2367a6</id>
<content type='text'>
Allow "postinst" scripts to perform extra actions after applying all
kind of fixups implemented using uci-defaults.

This is needed e.g. by uhttpd-mod-ubus which after installation in a
running systems needs to:
1. Update uhttpd config using its uci-defaults script
2. Reload uhttpd

While this approach makes sense there is a risk it'll blow up some
corner case postinst usages. There is only 1 way to find out.

Cc: Hauke Mehrtens &lt;hauke@hauke-m.de&gt;
Signed-off-by: Rafał Miłecki &lt;rafal@milecki.pl&gt;
</content>
</entry>
<entry>
<title>base-files: ipcalc.sh: Add tests for unroutable, etc</title>
<updated>2023-12-12T19:30:35Z</updated>
<author>
<name>Philip Prindeville</name>
</author>
<published>2023-12-11T06:35:57Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/robimarko/commit/?id=e906ccfc8c8a75872405efaf1bc2e2b625369c30'/>
<id>urn:sha1:e906ccfc8c8a75872405efaf1bc2e2b625369c30</id>
<content type='text'>
See RFC-1918, RFC-3927, and RFC-1122.

Signed-off-by: Philip Prindeville &lt;philipp@redfish-solutions.com&gt;
</content>
</entry>
</feed>
