<philipp64>
hmm. also don't see the SD drive in the factory image.
tvc has quit [Ping timeout: 480 seconds]
eluks has quit [Remote host closed the connection]
tvc has joined #openwrt-devel
eluks has joined #openwrt-devel
n3ph has joined #openwrt-devel
n3ph has quit [Ping timeout: 480 seconds]
n3ph has joined #openwrt-devel
<f00b4r0>
hauke[m]: so for service releases we care more about adding new devices than fixing major bugs for which patches exist, afaict?
<f00b4r0>
this is great.
goliath has joined #openwrt-devel
valku has quit [Quit: valku]
n3ph has quit [Ping timeout: 480 seconds]
n3ph has joined #openwrt-devel
mrnuke has quit [Ping timeout: 480 seconds]
robimarko has joined #openwrt-devel
hitech95 has joined #openwrt-devel
mrnuke has joined #openwrt-devel
<hauke[m]>
f00b4r0: yes because you are unable to provide a PR with the fix
danitool has joined #openwrt-devel
n3ph has quit [Ping timeout: 480 seconds]
<hitech95>
is there anyone with a mt7986 dev board with the audio codec. I'm trying to bring up alsa but so far no luck. Even with the mainline machine driver and a custom dummy codec.
<hitech95>
I'm just ending with a wm8960-playback: ASoC: no backend DAIs enabled for wm8960-playback, possibly missing ALSA mixer-based routing or UCM profile
cmonroe has quit [Ping timeout: 480 seconds]
tohojo has quit [Ping timeout: 480 seconds]
sorinello has joined #openwrt-devel
bluew has quit [Quit: Leaving]
bluew has joined #openwrt-devel
valku has joined #openwrt-devel
geekythings has joined #openwrt-devel
KGB-2 has quit [Remote host closed the connection]
KGB-2 has joined #openwrt-devel
tohojo has joined #openwrt-devel
minimal has joined #openwrt-devel
bluew_ has joined #openwrt-devel
bluew has quit [Read error: Connection reset by peer]
bluew_ has quit [Read error: Connection reset by peer]
mrnuke has quit [Ping timeout: 480 seconds]
bluew_ has joined #openwrt-devel
tohojo has quit [Ping timeout: 480 seconds]
tohojo has joined #openwrt-devel
mrnuke has joined #openwrt-devel
mrnuke has quit [Ping timeout: 480 seconds]
goliath has quit [Quit: SIGSEGV]
mrnuke has joined #openwrt-devel
fakuivan has quit [Remote host closed the connection]
fakuivan has joined #openwrt-devel
ungeskriptet_ has joined #openwrt-devel
ungeskriptet has quit [Ping timeout: 480 seconds]
cmonroe has joined #openwrt-devel
<f00b4r0>
hauke[m]: wonderful. Duly noted.
<f00b4r0>
I wasn't aware I was supposed to provide PRs for fixes committed by write-access developers.
<f00b4r0>
I guess one can only expect so much.
fakuivan has quit [Remote host closed the connection]
fakuivan has joined #openwrt-devel
hanetzer1 has joined #openwrt-devel
hanetzer has quit [Remote host closed the connection]
Sawzallz has joined #openwrt-devel
n3ph has joined #openwrt-devel
geekythings has quit [Quit: Leaving.]
Sawzall has quit [Ping timeout: 480 seconds]
Sawzall has joined #openwrt-devel
Sawzallz has quit [Ping timeout: 480 seconds]
n3ph has quit [Ping timeout: 480 seconds]
enyc has joined #openwrt-devel
valku has quit [Quit: valku]
cmonroe has quit [Ping timeout: 480 seconds]
<enyc>
#openwrt-devel topic needs updaing now r.e. 24.10.2
cmonroe has joined #openwrt-devel
<robimarko>
f00b4r0: what is the major issue?
Sawzall has quit [Read error: Connection reset by peer]
Sawzall has joined #openwrt-devel
<stintel>
I guess the horrible instability of mt76 for him, combined with qca being even less usable, making openwrt near unusable
<stintel>
or it could be that DSA bug
<stintel>
I don't have links, and I'm too lazy to search for them right now
<stintel>
but I share his sentiment
<schmars[m]>
yeah i think some mt76 (and potentially mt7530?) patches didnt find someone to backport them in time. it's good knowledge that simple backporting PRs are welcome :)
hitech95 has quit [Ping timeout: 480 seconds]
<schmars[m]>
i've had mediatek issues too, i think i'm just less reliant on openwrt releases (always following snapshot / release snapshot)
<robimarko>
stintel: I feel his pain but somebody with interest is the one that can fix those
<neocturne>
How do you want to proceed with this? Did you have time to look into it, or should I give implementing your suggestions a try?
<f00b4r0>
robimarko: major issue is recurring firmware crashes on mt7915e. A workaround was implemented by nbd, but that had other issues, eventually fixed by blocktrron in Gluon. One side effect of the firmware crash is very likely https://github.com/openwrt/openwrt/issues/19164
<f00b4r0>
I wasn't sure which patches needed backporting, so pinged blocktrron and nbd, but was never told a PR was needed.
<f00b4r0>
I've also identified a kernel panic caused by some rogue Tuya clients, currently only informally reported here to nbd but I suppose I'll open another issue for everyone else to ignore :P
<f00b4r0>
there's also a slab leak somewhere in the hostapd code, also reported informally, will also open an issue I suppose
<blocktrron>
f00b4r0: I did talk with picking the firmware fix for 24
<f00b4r0>
the mt753x DSA vlan leak has been going on forever, nobody seems to care either. Makes it impossible to run extra vlans on these devices when used as APs
geekythings has joined #openwrt-devel
<blocktrron>
However Felix intended to push the master of the driver for 24.10. this is currently not building as there are apis missing in 24.10
<blocktrron>
I did say to Hauke to just release, as stalling that does not benefit anyone
<f00b4r0>
the end result is the same. There was a service release which fixes apparently nothing major, adds a whole bunch of new devices (which makes me think it was the main goal here), and leaves fixes for known major bug out.
<f00b4r0>
really, what's the benefit from this release then, because it's not obvious to me.
<f00b4r0>
unless of course the new moto is "let's support as many devices as we can, no matter how poorly" ;P
<blocktrron>
i got multiple fixes from the ervice releases, just because they dont impact you doesnt mean it is worthless
<blocktrron>
to switch up the perspective here - i got 0 (zero) feedback for the mtk patches for roughly four months
<f00b4r0>
the release announce lists afaict a single broad-scope fix (UDPv6 GSO), afaict.
<blocktrron>
For me, i pretty much lost track of everything since stuff went to github (regarding the broad scope)
<blocktrron>
I manage to keep track of the stuff that i get notified for, but over the past 6 months this went downhill, as i get regularly pinged for stuff i have absolutely no stakes in just because i touched some random dts 4 years ago
<f00b4r0>
well I'm not sure what fixes you're referring to, I'm sure we'd at least announce major fixes if/when they happen. Wouldn't we?
<blocktrron>
ex400 led fixes, rutx50, realtek is usable again
<blocktrron>
just the ones i get from the back of my head
<schmars[m]>
if somebody finds time for them - announcments/docs are subject to the same lack of resources / everybody being spread thin
<f00b4r0>
realtek is a target only devs use. led fixes, sure, that's major.
<blocktrron>
cant help with your attitude
hitech95_ has joined #openwrt-devel
<f00b4r0>
My attitude stems from the fact that I don't understand why you fixed this in gluon and then apparently didn't try to get this fixed in OpenWrt
hitech95 has quit [Read error: Connection reset by peer]
<f00b4r0>
and then all the support I got here was "[2025-06-17T23:50:11+0200] <blocktrron> hauke: I don't have a strong opinion. For me the fixes did resolve all issues I had, but I'd let this nbd to decide"
<f00b4r0>
no strong opinion makes it sound as if the underlying bug is no big deal.
<f00b4r0>
but well, what's done is done. let's move on.
<blocktrron>
i did talk to felix in person about it, he merged it to his linux-wireless staging tree 2 weeks ago at the same time, it just didnt cut it to push the mt76 driver
<stintel>
honestly a PR shouldn't be needed, ML the git hashes to cherry-pick should be enough, we did plenty of that in the past
<blocktrron>
i did my best to push the whole process forward
<blocktrron>
so please dont imply i "did not try", i believe in upstream first even for gluon, so i did not drop anything once patch arrived there.
<blocktrron>
off for 3 hours, gotta get back to shitty-adsl-and-gsm-wonderland
hitech95 has quit [Read error: Connection reset by peer]
hitech95_ has quit [Read error: Connection reset by peer]
<hauke>
We do regular service releases to get the stuff which pilled up in the release branch gets out again.
<hauke>
If we wait till all issues are fixed there will never be a release
<hauke>
When I ask if something is missing for the next service release I am looking for changes which we should cherry pick from main, but not some problems which first need extensive debugging.
<dwfreed>
f00b4r0: hey, I'm about to have 4 realtek switches running openwrt (all netgear; 2 GS308T, 1 GS108Tv3, 1 GS110TPv3)
<hauke>
such problems should get fixed independently
<hauke>
f00b4r0: you just said there are some problems in mt76, but you did not even provide a link to a commit hash which we should backport
SnakesAndStuff has quit [Remote host closed the connection]
goliath has quit [Quit: SIGSEGV]
SnakesAndStuff has joined #openwrt-devel
<hauke>
f00b4r0: I am doing OpenWrt as a hobby, your behavior is very demotivating
<hauke>
If you need professional support you should buy profession support which can grantee that they fix your problems.
<stintel>
fun fact is that he actually reached out to several devs to pay to fix his problems and got ignored
<f00b4r0>
hauke: i told you I didn't know which commits where required, because who else than the author of said commits would actually know?
<f00b4r0>
and now you slap me with this "you didn't provide a PR" bs, and *I* am the demotivating factor? I give up.
<f00b4r0>
in fact if I had been told that extra work was required to get this into 24.10 (as blocktrron - said author) pointed out earlier, I'd have happily churned in to help. But I wasn't even provided with that opportunity.
<f00b4r0>
anyhow, I rest my case, this is depressing.
hitech95__ has quit [Read error: Connection reset by peer]
aparcar[m] has joined #openwrt-devel
<aparcar[m]>
huh, quite busy here today
valku has joined #openwrt-devel
<hauke>
f00b4r0: I also do not know which commits are needed to fix your bugs
SlimeyX has quit [Remote host closed the connection]
vincejv has quit []
vincejv has joined #openwrt-devel
minimal has quit [Quit: Leaving]
geekythings has quit [Quit: Leaving.]
dryimpact1 has joined #openwrt-devel
dryimpact has quit [Read error: Connection reset by peer]
dryimpact1 is now known as dryimpact
danitool has quit [Quit: Cubum autem in duos cubos, aut quadratoquadratum in duos quadratoquadratos]