<Znevna>
If i drink coffee all day I give the energy back when I go to sleep
<Znevna>
job done
<mrkiko>
Znevna: eheh, would be nice
<oliv3r[m]>
How do I properly define a PHY_INTERFACE_MODE_10GBASER | PHY_INTERFACE_MODE_1000BASEX port in the dts's phy-mode node? Since this is an SFP+ port, it depends on what you insert, or does the phy-mode in the dts just set the initial/highest mode and after that, it doesn't matter? (which in case it means phy-mode should be 10GBASER, unless of course the default is the lowest :p)
<nbd>
mrkiko: pong
robimarko has joined #openwrt-devel
dether has quit [Remote host closed the connection]
cmonroe has quit [Ping timeout: 480 seconds]
<mrkiko>
nbd: hi!! Sorry for the late reply. Wanted ot ask youfor some hints on why mtk_eth fails sometimes to "remove" peers emitting messages in the dmesg
<mrkiko>
nbd: don't have the message anymore available, but said if failed to remove peer via 0 from FDB
robimarko has quit [Remote host closed the connection]
robimarko has joined #openwrt-devel
<mrkiko>
robimarko: hi!! :D
<robimarko>
hi
<mrkiko>
robimarko: have you runtime-tested yhe QNAP AQR thermal zone ? Does it work as expected? or, in other words, are you experiencing the other termal zones disappearing as well?
<robimarko>
mrkiko: Yes, I ran it but without any trips
<robimarko>
Other zones were present as well
<mrkiko>
robimarko: given my current patch state (dts): http://ix.io/4oib do you think I should assume the dts changes are correct and move on to search for problems elsewhere?
<nbd>
mrkiko: i think it's probably not mtk_eth, but the mt7530 driver
<robimarko>
Znevna: You are just wasting energy on that guy, he will continue working on his magic secret code
<Znevna>
yes I don't care about him wasting time on it
<Znevna>
just I don't know if the OpenWrt forums is the place for builds using those drivers
<robimarko>
Its not
<Znevna>
well we're allowing people posting builds apparently
<Znevna>
in various topics
<robimarko>
Its fine as long as the source is there
<Znevna>
none shared the source afaik
<Znevna>
and the license on that source is .. not that open?
<nbd>
Znevna: you're right about the legal status of the builds
<nbd>
as long as they're not hosted on any openwrt servers, i don't have a problem with allowing discussion about those builds
<Znevna>
I'd hate MediaTek poking OpenWrt with sticks because of them.
<nbd>
an occasional reminder of the legal status might be appropriate
<stintel>
if any vendor starts pointing sticks we can talk about the use of the OpenWrt name in their builds ;)
<stintel>
s/name/trademark/
<Znevna>
yeah i doubt the vendors we should worry about ;P
<nbd>
i don't think MTK will be poking OpenWrt about this, as long as we don't host any of this stuff ourselves
<Znevna>
ok, let's hope they see it that way :P
<Znevna>
too*
<nbd>
MTK has too much to lose if they alienate us :)
<robimarko>
Doubt vendors go chasing random binaries on the internet
<robimarko>
They would have work for years in all of the rando china forks
<robimarko>
stintel: They have upgraded to leaving out the "based" part, now its all just running "OpenWrt"
<stintel>
if SFC provides access to their ticket system we can start filing tickets for legal action to each of them ;)
goliath has quit [Quit: SIGSEGV]
f00b4r0 has joined #openwrt-devel
lmahmutov has joined #openwrt-devel
srslypascal is now known as Guest5140
srslypascal has joined #openwrt-devel
Guest5140 has quit [Read error: Connection reset by peer]
<rmilecki>
nbd: I assume I should use -P4 with iperf?
<rmilecki>
for testing threaded rps patch
valku has joined #openwrt-devel
minimal has joined #openwrt-devel
goliath has joined #openwrt-devel
<stintel>
Build dependency: Please reinstall the GNU C++ Compiler (6 or later) - it appears to be broken
<stintel>
wtf
<dwfreed>
nice
<stintel>
if it's going to be one of those days I'm just gonna play call of duty
<stintel>
it will probably involve the same amount of cursing :D
<nbd>
rmilecki: yes
<rmilecki>
nbd: thanks, starting tests
<Slimey>
:]
g___ is now known as g_____
g_____ is now known as g___
<Znevna>
no way
<Znevna>
ramips switched to 5.15
<Znevna>
hell incoming
<mrkiko>
Znevna: why?
gladiac has quit [Quit: k thx bye]
<Znevna>
I expect a few devices to have issues
<mrkiko>
Znevna: eh - I'm little bit worried by mt7620 / mt7628
<mrkiko>
or maybe the R6220 breaks being MT7621ST ...
<Znevna>
some initramfs might not boot anymore
<gch981213>
Znevna: FYI MTK used to host a repo for .ko of their proprietary drivers compiled against OpenWrt master and stable releases themselves. So I doubt if MTK minds it at all.
<Znevna>
binary blobs offered by them ok
<Znevna>
but the source code with that license in them? :)
<gch981213>
Znevna: Er... Publishing source code is likely against the NDA.
lmahmutov has quit [Quit: Page closed]
<Znevna>
sketchy
<stintel>
I'm confused by that statement. you're talking about MTK so it's their source code, they don't need to sign an NDA to get access to that?
<mrkiko>
Znevna: understandable, but I think you should let go
<Znevna>
of what?
<mrkiko>
Znevna: of this thing :D
<Znevna>
never :P
<mrkiko>
Znevna: I agree with you it would be better to avoid private build with proprietary drivers and violating the NDAs, but ... if someone in the right position tought it was time to stop them, they would have said so at least. Nothing happening...
<Znevna>
they could fix a bug or two and actually contribute to OpenWrt instead of using the forums as their personal playground
<gch981213>
Znevna: Users may want battle-tested garbage from vendors. It does perform better after all :P
<mrkiko>
Znevna: this is your opinion and I agree with that, but - as you see - nobody in the position to do so is listening to you. I'vebeen in the place you are several times, and maybe I'll find myself here again soon. but there is nothing you can do, and continuing to insist on that, you're actually "resonating" the problem. Sure, speaking about something is better than not, and hiding problems by not
<mrkiko>
speaking about them is surely a bad thing. But while we are a community, we are not all equal, and you know that.
<stintel>
maybe someone should try to convince them of trying to improve mt76 rather than messing with the mtk driver
<stintel>
in a constructive way
<stintel>
use the example of ath10k being so utterly broken because qca doesn't give a rat's ass about fixing their shitty firmware, so you end up with unfixable junk
<stintel>
the same can happen if you're betting on proprietary drivers
<stintel>
my .02 [insert_currency_here]
<Znevna>
you can't convince people like bricco to work on something else, he's so convinced that the mtk drivers are so much better
<stintel>
have you tried?
<gch981213>
stintel:Building vendor crap is easier than understanding that :P
<stintel>
well then just leave them be, you mention wasting time, yet you're wasting time getting worked up over it
<stintel>
just ignore them
<Znevna>
stintel: think I've tried, but then some forum mod came and said that this helps openwrt development
<Znevna>
and that's where I've stopped
<stintel>
alright, on to better things then ;)
<stintel>
like fixing the ramips hell that's incoming
* stintel
hides
<Znevna>
:P hah
<rmilecki>
nbd: enabling threaded rps EARLY (in rc.local) causes WARNINGs in net/core/dev.c:7124 (napi_threaded_poll+0xfc/0x120)