danitool has quit [Quit: Cubum autem in duos cubos, aut quadratoquadratum in duos quadratoquadratos]
hanetzer1 has joined #openwrt-devel
hanetzer has quit [Ping timeout: 480 seconds]
csrf has joined #openwrt-devel
hanetzer1 is now known as hanetzer
Tapper has quit [Ping timeout: 480 seconds]
goliath has quit [Quit: SIGSEGV]
mzvd has joined #openwrt-devel
mzvd has quit [Read error: Connection reset by peer]
ptudor has joined #openwrt-devel
ptudor_ has quit [Ping timeout: 480 seconds]
csrf has quit [Remote host closed the connection]
Misanthropos has quit [Ping timeout: 480 seconds]
csrf has joined #openwrt-devel
mzvd has joined #openwrt-devel
mzvd has quit [Read error: Connection reset by peer]
mzvd has joined #openwrt-devel
mzvd has quit [Read error: Connection reset by peer]
mzvd has joined #openwrt-devel
mzvd has quit [Read error: Connection reset by peer]
mzvd has joined #openwrt-devel
mzvd has quit [Read error: Connection reset by peer]
mzvd has joined #openwrt-devel
digitalcircuit has joined #openwrt-devel
mzvd has quit [Read error: Connection reset by peer]
mzvd has joined #openwrt-devel
mzvd has quit [Read error: Connection reset by peer]
mzvd has joined #openwrt-devel
mzvd has quit [Remote host closed the connection]
srslypascal has quit [Remote host closed the connection]
srslypascal has joined #openwrt-devel
mzvd has joined #openwrt-devel
mzvd has quit [Read error: Connection reset by peer]
mzvd has joined #openwrt-devel
AtomiclyCursed has quit [Quit: ZNC 1.8.2 - https://znc.in]
AtomiclyCursed has joined #openwrt-devel
mzvd has quit [Ping timeout: 480 seconds]
mzvd has joined #openwrt-devel
AtomiclyCursed has quit [Quit: ZNC 1.8.2 - https://znc.in]
AtomiclyCursed has joined #openwrt-devel
mzvd has quit [Read error: Connection reset by peer]
mzvd has joined #openwrt-devel
mzvd has quit [Read error: Connection reset by peer]
mzvd has joined #openwrt-devel
mzvd has quit [Read error: Connection reset by peer]
AtomiclyCursed has quit [Quit: ZNC 1.8.2 - https://znc.in]
AtomiclyCursed has joined #openwrt-devel
mzvd has joined #openwrt-devel
floof58 has quit [Ping timeout: 480 seconds]
floof58 has joined #openwrt-devel
mzvd has quit [Read error: Connection reset by peer]
mzvd has joined #openwrt-devel
mzvd has quit [Remote host closed the connection]
dhewg has joined #openwrt-devel
mzvd has joined #openwrt-devel
mzvd has quit [Read error: Connection reset by peer]
mzvd has joined #openwrt-devel
mzvd has quit [Read error: Connection reset by peer]
mzvd has joined #openwrt-devel
Borromini has joined #openwrt-devel
goliath has joined #openwrt-devel
danitool has joined #openwrt-devel
goliath has quit [Quit: SIGSEGV]
mzvd has quit [Read error: Connection reset by peer]
mzvd has joined #openwrt-devel
<rsalvaterra>
Ok, I think I got the 5.15.51 bump done correctly (thanks to John's tentative commit, I just had to fix a couple of patches).
<rsalvaterra>
Still, a single patch adding a TON of device trees… Whisky Tango Foxtrot.
<rsalvaterra>
In a related subject, I find commits like these conterproductive: https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=3c3367f03e3e45fb87698df9777eb0e3cf83f7b3
<rsalvaterra>
*counterproductive
<rsalvaterra>
They just make rebasing kernel bumps more difficult, and kernel patches are all refreshed no every bump, anyway.
mzvd has quit [Read error: Connection reset by peer]
mzvd has joined #openwrt-devel
mzvd has quit [Read error: Connection reset by peer]
robimarko has joined #openwrt-devel
T-Bone has joined #openwrt-devel
f00b4r0 has quit [Remote host closed the connection]
mzvd has joined #openwrt-devel
mzvd has quit [Read error: Connection reset by peer]
Borromini has quit [Quit: Lost terminal]
mzvd has joined #openwrt-devel
floof58 is now known as Guest4074
floof58 has joined #openwrt-devel
mzvd has quit [Remote host closed the connection]
Guest4074 has quit [Ping timeout: 480 seconds]
mzvd has joined #openwrt-devel
mzvd has quit [Read error: Connection reset by peer]
robimarko_ has joined #openwrt-devel
robimarko has quit [Ping timeout: 480 seconds]
sorinello has quit [Quit: Leaving]
sorinello has joined #openwrt-devel
minimal has joined #openwrt-devel
aiyion_ has quit [Remote host closed the connection]
aiyion_ has joined #openwrt-devel
sorinello has quit [Quit: Leaving]
sorinello has joined #openwrt-devel
<aphorise>
Is there a rc5 expected for 22.03.0 or is there a final GA release expected next?
mzvd has joined #openwrt-devel
Tapper has joined #openwrt-devel
mzvd has quit [Read error: Connection reset by peer]
mzvd has joined #openwrt-devel
mzvd has quit [Remote host closed the connection]
mzvd has joined #openwrt-devel
mzvd has quit [Read error: Connection reset by peer]
GNUmoon has joined #openwrt-devel
GNUmoon2 has quit [Ping timeout: 480 seconds]
mzvd has joined #openwrt-devel
mzvd has quit [Read error: Connection reset by peer]
mzvd has joined #openwrt-devel
mzvd has quit [Read error: Connection reset by peer]
mzvd has joined #openwrt-devel
mzvd has quit [Read error: Connection reset by peer]
mzvd has joined #openwrt-devel
mzvd has quit [Read error: Connection reset by peer]
mzvd has joined #openwrt-devel
Tapper has quit [Ping timeout: 480 seconds]
mzvd has quit [Read error: Connection reset by peer]
mzvd has joined #openwrt-devel
mzvd has quit [Read error: Connection reset by peer]
mzvd has joined #openwrt-devel
valku has joined #openwrt-devel
mzvd has quit [Remote host closed the connection]
mzvd has joined #openwrt-devel
mzvd has quit [Read error: Connection reset by peer]
mzvd has joined #openwrt-devel
goliath has joined #openwrt-devel
bkallus has joined #openwrt-devel
mzvd has quit [Read error: Connection reset by peer]
mzvd has joined #openwrt-devel
Tapper has joined #openwrt-devel
mzvd has quit [Remote host closed the connection]
mzvd has joined #openwrt-devel
mzvd has quit [Read error: Connection reset by peer]
srslypascal is now known as Guest4090
srslypascal has joined #openwrt-devel
Guest4090 has quit [Ping timeout: 480 seconds]
danitool has quit [Quit: Cubum autem in duos cubos, aut quadratoquadratum in duos quadratoquadratos]
mzvd has joined #openwrt-devel
danitool has joined #openwrt-devel
mzvd has quit [Read error: Connection reset by peer]
danitool has quit [Remote host closed the connection]
mzvd has joined #openwrt-devel
danitool has joined #openwrt-devel
aphorise has quit [Remote host closed the connection]
mzvd has quit [Read error: Connection reset by peer]
mzvd has joined #openwrt-devel
mzvd has quit [Read error: Connection reset by peer]
mzvd has joined #openwrt-devel
mzvd has quit [Read error: Connection reset by peer]
mzvd has joined #openwrt-devel
mzvd has quit [Read error: Connection reset by peer]
<hauke>
OpenWrt 2102 build problem should be fixed
mzvd has joined #openwrt-devel
<Habbie>
was that the protobuf thing?
mzvd has quit [Read error: Connection reset by peer]
<mrnuke_>
hurricos: having fun here with the MCU protocol. I found it sends several "incomplete request" packets to a single command when we flood it with requests. Migh have to rewrite the Rx loop.
<hauke>
Habbie: no, I missed a patch needed for wireguard after the kernel update
<hurricos>
mrnuke_: I see some of your [HACK] commits. Ping me if you think any are worth testing.
<mrnuke_>
hurricos: too early to test. Generally, if you see a commit from me, and it has a positive SLOC count, be suspicious :p
<stintel>
lol
<hurricos>
mrnuke_: Testing out your fix for #5, and I find the compiler dislikes poe_cmd_global_port_enable being defined, now that it's not used.
<hurricos>
Thinking about it, I went down a bit of a rabbit-hole ...
<hurricos>
Most users don't really care to manually configure each of their ports (it's a huge PITA), yet our conf requires it
<hurricos>
Maybe we should look at a slightly different model for realtek-poe, which would make interacting with it over a web UI much easier --
<hurricos>
allow a default "whatever, turn 'em on" config, retrieving as much model-specific data from the devicetree as possible, and exposing more callbacks through ubus
<hurricos>
I don't think this is an original thought. I haven't looked at poemgr or other poe solutions for long enough to know, though
<olmari>
mm.. I'd say models should have sane defaults... "always has been" that way anyway... then if wanting something else then need to touch :)
<hurricos>
olmari: in that case, I should definitely start rolling together a patch to add wattage conf to the device tree for all of these boards
<hurricos>
so that the information is just immediately available
<olmari>
How big of an job it is and so on is ofcourse wholly other thing
<hurricos>
There's no standard bindings so probably "enormous work"
<hurricos>
either that or I'm throwing the work of upstreaming onto someone else's back ;(
<olmari>
I'd imagine something like that
<olmari>
In broad general things just works at wild with PoE-switches too, while managed switches has often all sorts of settings that could be touched, including power-priorisations
<hurricos>
realtek-poe gives us that but it can only be changed using the default OpenWrt model (modify conf, commit change, reload)
<olmari>
At least such ought to be nice goal, if something :)
<hurricos>
this is cumbersome if I want to restart an AP on a specific port :P
srslypascal has quit [Ping timeout: 480 seconds]
srslypascal has joined #openwrt-devel
<mrnuke_>
hurricos: only downside of merging one of my commits that's not in a PR is I might have to write a "Fixes:" and write a snarky commit message about my own changes ;)
<mrnuke_>
The first thing I'd like to see as a user interface is a luci modyle that just tells you the status of each port. Kind of like "Network -> Switch"
<mrnuke_>
I agree that most users just want "my poe device to turn on".
<olmari>
if it is "poe as powering oneself", then it can have dedicated set port for that.. for PSE all the (capable) ports ought to deliver power per default... setup is then if budgeting or anything is actually wanted to configure... but indeed default should always be "just works"
<hurricos>
when I suspect something is wrong but my brain isn't sufficiently online to determine what it is, I build the snark into the original commit usually
<mrnuke_>
That's how I git blamed for everything in the repo!
mzvd has joined #openwrt-devel
<hurricos>
then the fix: is "I told you. Didn't I tell you? I told you, dammit."
<mrnuke_>
Nope. I't's "realtek-poe: I told you. Didn't I tell you? I told you, dammit."
<hurricos>
this is why I'll never be an official openwrt dev
<hurricos>
maybe I have respect for the standards, yes, but I don't really know them.
<hurricos>
I don't really know how to prefix my commits right without someone telling me ;')
mzvd has quit [Read error: Connection reset by peer]
<mrnuke_>
I wouldn't put URLs in commit messages. A couple of years down the line, when git blame stumbles across this commit, and someone's trying to figure out the _why_... What do you do when the URL is a dead link? Now your commit message is incompete. Same thing goes for github-spefici links. What does "#5" mean if the repo is mirrored soemwhere, forked, or you're reading the commit message from a local clone?
<hurricos>
I could go ahead and describe the whole thing but it's really self-describing
<hurricos>
as for the patchwork link, well, I can drop that, but if patchwork no longer has the original code, then nobody does, at which point it's moot
<hurricos>
mrnuke_: Also, the '[1] "#5"' is not actually that -- github is just eating it in the web-view.
robimarko_ has quit [Quit: Leaving]
<mrnuke_>
hurricos: you did a ninja edit as I was typing my review
<hurricos>
I edited just the cover letter
<hurricos>
Commits are unchaged
<hurricos>
oh well
<hurricos>
no, sorry
<hurricos>
I pushed your commit behind mine as well so that both commits compile
<hurricos>
or, underneath.
<mrnuke_>
I gotta do some AFK business for a few hours. I'm certain github will harras me over email :)
<hurricos>
:thumbsup:
<hurricos>
mrnuke_: Thank you for all your work today :D