<schmars[m]>
blocktrron: nevermind, it was my mistake. i can confirm that both snapshot and 22.03-snapshot flash fine on vendor firmware v4.0.66 and latest v6.4.18. both cpus are activated and the overlay is expanded fine. very cool
awgh has quit [Ping timeout: 480 seconds]
hanetzer has joined #openwrt-devel
fakuivan_ has joined #openwrt-devel
fakuivan has quit [Quit: No Ping reply in 180 seconds.]
guidosarducci has joined #openwrt-devel
guidosarducci has quit [Remote host closed the connection]
guidosarducci has joined #openwrt-devel
<Mangix>
\x: t4 is a huge size increase
valku has quit [Quit: valku]
floof58 is now known as Guest5533
floof58 has joined #openwrt-devel
<\x>
Mangix: I have tthe space for it hehe, as long as it can fit on 128M nand then im fineeee
Guest5533 has quit [Ping timeout: 480 seconds]
goliath has joined #openwrt-devel
Tapper has joined #openwrt-devel
goliath has quit [Quit: SIGSEGV]
nitroshift has joined #openwrt-devel
Atomicly- has joined #openwrt-devel
AtomiclyCursed has quit [Ping timeout: 480 seconds]
<dhewg>
nbd: the mesh issue happened again, the mt7621 side couldn't reach the ipq4019 side. Once I started pinging mt from the ipq side, it started working again
nitroshift has joined #openwrt-devel
minimal has joined #openwrt-devel
nitroshift has quit [Quit: Gone that way --->]
bluew has quit [Ping timeout: 480 seconds]
<mrkiko>
stintel: yes, I confused them. Thanks a lot!!
<stintel>
yw
Tapper has quit [Ping timeout: 480 seconds]
gromero has joined #openwrt-devel
<oliv3r[m]>
how does openwrt parse key presses (reset / WPS etc) buttons. Does it need CONFIG_INPUT at all for that? or is that something I am only familiar with for debugging :) (because of /dev/input/evdev)
<robimarko>
It actually has a downstream implementation that uses hotplug instead
<oliv3r[m]>
any reason that is used/needed instead of the 'standard stuff'?
<oliv3r[m]>
udev/mdev would be able to handle this just fine no?
<stintel>
if you look at the copyright lines in the src, you realize part of the answer is "legacy"
<stintel>
so then the question is: is there an alternative that isn't size-bloated compared to this, if yes, are we already using it, if no, why not, etc
floof58 is now known as Guest5559
floof58 has joined #openwrt-devel
Guest5559 has quit [Read error: Connection reset by peer]
<oliv3r[m]>
I figured :p
<oliv3r[m]>
but do all targets support/use mdev/udev by default nowadays?
<oliv3r[m]>
or rather, this is input related, so I think it's not even using mdev/udev; but something more simple, aking to acpid
<oliv3r[m]>
but my guess is, nobody investigated/spent time on this, thus legacy survives :)
<robimarko>
My guess is that any alternative is going to be way bigger in size
gladiac has joined #openwrt-devel
<oliv3r[m]>
'way bigger' idk, you could do most of it just through some shell magic; but you don't have 'events' unless you use something like FAMd/inotify
<robimarko>
Well, if you want to use the in-kernel input system which has the GPIO key driver
<robimarko>
Then its gotta be bigger
valku has joined #openwrt-devel
<oliv3r[m]>
i think i saw that that hotplug driver subscribes to hid/input events though?
<oliv3r[m]>
anyway, I guess for 4M targets this will be difficult, but having a cleaner more upstream code base in the end, is probably more desireable :)
<robimarko>
I agree, it would be nice to just use the kernel driver
<oliv3r[m]>
time and priorities; first need to get this switch in better shape :D
<oliv3r[m]>
btw, still nobody else is running into issues of 'faked' being problematic?
<mrkiko>
robimarko: hi!! :)
<mrkiko>
robimarko: regarding aqr min and max temp properties - would it make sense to stick them in the related ethernet-phy node? And what names would you suggest for them?
<mrkiko>
robimarko: or may I consider putting them somewhere else?
maciekb has quit [Read error: Connection reset by peer]
maciekb has joined #openwrt-devel
<robimarko>
mrkiko: Its the only place where they can go
<robimarko>
Do note that you have to document those in DT bindings
<mrkiko>
robimarko: sure
<mrkiko>
robimarko: I asked you also about the name since i know it will be an important factor later on. But grepping didn't help me find any kind of min or max temperature; found over-heat but not under-heat or whatever
<robimarko>
What are the sysfs entry names?
nwf has quit [Ping timeout: 480 seconds]
nwf has joined #openwrt-devel
<mrkiko>
robimarko: searcing for them right now...
<mrkiko>
robimarko: thanks, didn't thinkabout that
<mrkiko>
well, e.g.: in /sys/class/thermal/thermal_zone12 (aqr) I am not finding interesting entries: http://ix.io/4oUr
<robimarko>
Not in the thermal zone, but under the hwmon device
<mrkiko>
robimarko: from name I think it's the aqr hwmon
<robimarko>
It is, so names should probably be similar
<robimarko>
temperature-critical-alarm, etc
<robimarko>
I am sure that DT guys will have some ideas as well
goliath has joined #openwrt-devel
danitool has quit [Ping timeout: 480 seconds]
cmonroe_ has joined #openwrt-devel
<mrkiko>
robimarko: thanks!
raggi has joined #openwrt-devel
<raggi>
hello friends. I'm reading the notes in this commit https://github.com/openwrt/packages/commit/aabfc3f51027d653455bca91587774e47f26e3b7 and I'm curious if there is an API by which the openwrt firewall can be informed of desired configuration changes by additional software running on the system such as tailscale, if so, are there docs for that interface you can point me to?
Tapper has joined #openwrt-devel
dangole has joined #openwrt-devel
gladiac has quit [Quit: k thx bye]
dangole has quit [Remote host closed the connection]
dangole has joined #openwrt-devel
<Znevna>
I'm sick of reading about "Full Cone NAT" in the last days
<stintel>
ah that's one of the terms that make me insta ctrl+w the browser tab