<philipp64>
I recently rebased my tree to master and it's been a minute... was last running 5.15 if I remember. Now when I build I'm having issues with linkage related to CONFIG_CRYPTO_ACOMP2 wanting to be a module and not built-in. Did I miss a step refreshing my env/kernel-config file? Anyone else having issues building 6.6 for x86_64 hardware?
<f00b4r0>
I'll just update_git_source_package.sh in 23.05 branch, cherry picking all the intermediary patches is just too much hassle
<f00b4r0>
hauke: in the meantime you're welcome to deal with 22.03, I won't be touching that :)
radxanaoki has joined #openwrt-devel
<f00b4r0>
hauke: FWIW been test-building ath79 with 23.05 buildbot config to confirm ucode builds, I'm getting image file too big errors for a couple tp-link devices (re355-v1, re450-v{1,2}). Dunno if that's expected.
<f00b4r0>
i'll submit the patch now
Daanct12 has joined #openwrt-devel
_lore_ has joined #openwrt-devel
_lore_ has quit [Quit: ZNC 1.8.2+deb2+b1 - https://znc.in]
_lore_ has joined #openwrt-devel
<romany>
hi all! anybody is having problems with ethernet link detection (always stays UP even if there is no cable) on ath79 target?
<romany>
I'm having this problem on ar9331 but curious maybe it's also a problem with other SoCs
torv has quit [Remote host closed the connection]
torv has joined #openwrt-devel
<schmars[m]>
hauke: mt76 802.11s regressions but they're already "older" and not since last 23.05.x release
<philipp64>
KanjiMonster: that looks right. I also think that CRYPTO_ACOMP needs to be selected when CRYPTO_ACOMP2. so what's the solution? back out this patch for now?
<KanjiMonster>
philipp64: just disable CRYPTO_MANAGER_DISABLE_TESTS in your kernel config, that should fix it for you
<philipp64>
building...
<philipp64>
being prompted for settings for CRASH_HOTPLUG and CRASH_MAX_MEMORY_RANGES ...
goliath has joined #openwrt-devel
<philipp64>
KanjiMonster: sigh. still fails exactly the same.
<philipp64>
nbd: any ideas?
<romany>
tmn505, that looks similar, yeah... but I already tried adding phy-handle to eth node (referencing correct internal switch port), it only starts detecting link if I remove fixed-link, but then there is no data flow, looks like phy-handle and fixed-link are in conflict somehow :/
<tmn505>
the link is up but probably no speed is negotiated, that is why Leo added builtin-switch property in the mentioned PR
<romany>
tmn505, ah, let me try
minimal has joined #openwrt-devel
<romany>
tmn505, that worked!
<romany>
I wonder why that PR was never merged
<tmn505>
beats me, don't know either, maybe with enough reports it'll get in
<tmn505>
.names
<tmn505>
oops
rua has quit [Remote host closed the connection]
<hauke>
tmn505: Is it fine to switch tegra to kernel 6.6 by default?
<tmn505>
yes
<tmn505>
want to send me the patch?
<hauke>
schmars[m]: I was hoping that one of the ~10 fixes related to 802.11s would fix it, but this will not block the release
<hauke>
tmn505: yes it would be nice if you could send a patch
<hauke>
f00b4r0: The ucode change is pretty late. I am not sure if we should take it
<f00b4r0>
hauke: I mentioned many times now that there are bug fixes in there
<f00b4r0>
and we came to the apparent consensus a week ago that we should just bump instead of cherrypick
<f00b4r0>
so, ¯\_(ツ)_/¯
<tmn505>
hauke: will do
<f00b4r0>
hauke: fwiw I made sure to use the exact same version as what has been in master since June 21.
<hauke>
f00b4r0: I will have a look at this
robimarko has quit [Remote host closed the connection]