jeff___m has quit [Remote host closed the connection]
jeff___m has joined #openwrt-devel
<Igel>
curious, armv8 target is not packaging any binaries for grub-efi-arm64
goliath has joined #openwrt-devel
bluew has quit [Quit: Leaving]
<slh>
Igel: which ARMv8 target, there are multiple? (armsr is probably the only one that would need attention in this direction, the 64 bit RPi ones could (and probably should), sunxi and rockchip probably could)
<Igel>
yes, armsr. youre right. i can test on metal if you give a hint what to patch.
jeff___m has quit [Remote host closed the connection]
<Znevna>
having no label on power led made it kinda useless, was this fixed?
<Ansuel>
what do you mean?
jeff___m has quit [Ping timeout: 480 seconds]
<Znevna>
for example on ax53u (mt7621) the power led with a label acts as a status something, as in it blinks when flashing ? and other times I can't remember
<Znevna>
without the label it's just a dumb led
<Ansuel>
in theory the change should not cause regression unless we actively have functions that check the label property
<Znevna>
ah
<Znevna>
I think the aliases don't work
<Znevna>
I see led-boot, led-failsafe, led-running, led-upgrade
<Znevna>
I guess those have a meaning somewhere
<Ansuel>
files/lib/functions/leds.sh mhhh this check the label property
<Znevna>
sorry for mentioning :P but I don't want broken LEDs again ^^
<Ansuel>
nha maybe leave a comment in the pr?
<Ansuel>
it's something that has to be done at at least improved
<Znevna>
I wouldn't know how to properly report what I just did
<tmn505>
Znevna: if everything is properly translated, sysfs paths will be same and that's what is used for all userspace scripts
<Ansuel>
anyway no the change should not cause any problem, we already support parsing led color func
<Ansuel>
tmn505 yes the final LED name is the same
<Ansuel>
the main problem is that we have lots of tplink:system:blu
<Ansuel>
those must be fixed and will require the user to change configuration