<ynezz>
jow: from xxd's manpage "-i output in C include file style. A complete static array definition is written (named after the input file), unless xxd reads from stdin."
<ynezz>
jow: so `xxd -i` with stdin input should produce just the array content, `xxd -i file` complete static array definition, `xxd < stdin` is xxdi.pl compat mode, complete array definition with file being set to `stdin`
<jow>
ynezz: yeah, I figured. See the paste
rsalvaterra has quit []
rsalvaterra has joined #openwrt-devel
Piraty has quit [Quit: --]
Piraty has joined #openwrt-devel
<ynezz>
jow: ah, seems to work fine, looks much better, thanks! going to CI build test it more in that PR
<ynezz>
btw that pastebin mangles the lineendings with \r
<nbd>
rmilecki: netifd handles setting ip addresses and routes
<jow>
f00b4r0: try logging out and in again
<f00b4r0>
jow: I did that to no avail. Reboot fixed it tho
<f00b4r0>
i even tried restarting uhttpd
<jow>
f00b4r0: did you also install ppp at the same time?
<jow>
pppd
<f00b4r0>
aye
<jow>
ah okay, thne the problem was not luci but netifd
<jow>
unfortunately netifd does not yet support hot-(re-)loading proto handlers, it needs a complete network restart
<f00b4r0>
ah ok, so I should have restarted netifd then I guess
<jow>
yep
<jow>
could paper it over in luci I guess by prompting the user whether a network restart should be performed after a proto handler install
<jow>
problem is that we can't do it unconditionally since we do not know if there's uncomitted / unapplied / non-uci managed changes to the network state
<jow>
restarting netifd has the nasty side effect of clearing all IP settings from all uci-managed interfaces
<minimal>
ldir: yes but that github issue said they *asked* upstream to revert the change on 26th Aug, there's no indication whether/when upstream reverted it
<ldir>
ahhh, true...maybe 64 then.
<minimal>
ldir: looking at the Changelog for 5.15.63 I don't see it mentioned
<minimal>
indeed 5.15.63 came out on 25th, the date *before* they were apparently asked to revert the change...
<ldir>
ha - yes that'll be the problem then :-) Thanks for your research minimal, very helpful.
<mrkiko>
Anyone has any idea on why 5.15.x kernel seems to not boot on mt7628? I did read on it on the forum and I have some devices. But no serial access so helping would be complicated for me.
<stintel>
hmmm I should probably hold off on updating my wired RPi devices then
csharper2005 has quit [Remote host closed the connection]
tlj has joined #openwrt-devel
minimal has quit [Remote host closed the connection]
minimal has joined #openwrt-devel
tlj has quit [Quit: tlj]
dangole has quit [Remote host closed the connection]
<hauke>
jow: do you want to add this to 22.03 too? https://git.openwrt.org/?p=openwrt/openwrt.git;a=commitdiff;h=c6d6306827e9296faad26981996825ce3e90259d
MaxSoniX has quit [Quit: Konversation terminated!]
<aparcar[m]>
hurricos: could you finish the eth renaming patch by adding two step renaming?
<aparcar[m]>
hauke: maybe fixup the backport with correct subject