adrianschmutzler has joined #openwrt-devel
indy has quit [Quit: ZNC - http://znc.sourceforge.net]
SergioCabral has joined #openwrt-devel
Rene__ has quit [Ping timeout: 272 seconds]
Rene__ has joined #openwrt-devel
goliath has quit [Quit: SIGSEGV]
lipnitsk has joined #openwrt-devel
danitool has quit [Quit: Cubum autem in duos cubos, aut quadratoquadratum in duos quadratoquadratos]
Tapper has quit [Ping timeout: 240 seconds]
<hurricos> Lotta bugs in this code. Apparently Wind River Linux's fork has most of them fixed but
<hurricos> I have no idea how to turn this bug link https://support2.windriver.com/index.php?page=defects&on=view&id=LIN5-19186 into something I can git clone.
<hurricos> They have some crazy rolling patch release layer thing which they supply via ....
<hurricos> well. They compile binaries which they send you which can clone from those URLs.
hgl has quit [Ping timeout: 256 seconds]
hgl has joined #openwrt-devel
hgl has quit [Changing host]
hgl has joined #openwrt-devel
<hurricos> but looks like for Linux there are patches galore to be merged. Yay!
black_ant has quit [Ping timeout: 246 seconds]
lipnitsk has quit [Ping timeout: 264 seconds]
hgl has quit [Ping timeout: 256 seconds]
hgl has joined #openwrt-devel
hgl has joined #openwrt-devel
hgl has quit [Changing host]
lipnitsk has joined #openwrt-devel
urjaman has quit [Read error: Connection reset by peer]
codehero has quit [Quit: Connection closed]
urjaman has joined #openwrt-devel
victhor has quit [Ping timeout: 264 seconds]
hbug__ has joined #openwrt-devel
hbug_ has quit [Ping timeout: 268 seconds]
tobleminer-tSYS has quit [Quit: AS4242423214]
tobleminer-tSYS has joined #openwrt-devel
adrianschmutzler has quit [Quit: ~ Trillian - www.trillian.im ~]
philipp64 has quit [Quit: philipp64]
philipp64 has joined #openwrt-devel
Slimey__ has quit [Remote host closed the connection]
Slimey has joined #openwrt-devel
xback has quit [Ping timeout: 256 seconds]
xback has joined #openwrt-devel
philipp64 has quit [Quit: philipp64]
<hurricos> can I just say how much I hate Android's process for managing code
hurricos has quit [Ping timeout: 264 seconds]
indy has joined #openwrt-devel
hurricos has joined #openwrt-devel
Katana_Steel has quit [Read error: Connection reset by peer]
philipp64 has joined #openwrt-devel
Katana_Steel has joined #openwrt-devel
rmilecki has joined #openwrt-devel
Tost has joined #openwrt-devel
lipnitsk has left #openwrt-devel [#openwrt-devel]
koniu has quit [Remote host closed the connection]
koniu has joined #openwrt-devel
valku has quit [Quit: valku]
goliath has joined #openwrt-devel
koniu has quit [Ping timeout: 268 seconds]
Tapper has joined #openwrt-devel
black_ant has joined #openwrt-devel
black_ant has joined #openwrt-devel
Katana_Steel has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
slh64 has joined #openwrt-devel
koniu has joined #openwrt-devel
snh has quit [Quit: ZNC - http://znc.in]
snh has joined #openwrt-devel
Katana_Steel has joined #openwrt-devel
ivanich has joined #openwrt-devel
Darkmatter66 has joined #openwrt-devel
damex has quit [Ping timeout: 246 seconds]
Borromini has joined #openwrt-devel
zkrx has quit [Ping timeout: 256 seconds]
zkrx has joined #openwrt-devel
damex has joined #openwrt-devel
feriman has joined #openwrt-devel
damex has quit [Ping timeout: 240 seconds]
MichaelOF has joined #openwrt-devel
glyph_ has joined #openwrt-devel
paracyst has quit [Ping timeout: 272 seconds]
mrkiko has quit [Ping timeout: 272 seconds]
paracyst_ has joined #openwrt-devel
lechner has quit [Ping timeout: 246 seconds]
glyph has quit [Ping timeout: 272 seconds]
glyph_ is now known as glyph
mrkiko has joined #openwrt-devel
goliath has quit [Ping timeout: 272 seconds]
Sebastiii has quit [Ping timeout: 272 seconds]
elektroman has quit [Ping timeout: 272 seconds]
elektroman has joined #openwrt-devel
__lore__ has joined #openwrt-devel
_lore_ has quit [Ping timeout: 265 seconds]
lechner has joined #openwrt-devel
_lore_ has joined #openwrt-devel
__lore__ has quit [Ping timeout: 240 seconds]
Sebastiii has joined #openwrt-devel
Sebastiii has quit [Excess Flood]
Sebastiii has joined #openwrt-devel
guerby has quit [Remote host closed the connection]
goliath has joined #openwrt-devel
guerby has joined #openwrt-devel
ilario has joined #openwrt-devel
feriman has quit [Read error: Connection reset by peer]
<rsalvaterra> I'm a bit miffed I still see the GPIO IRQ handler fucking off after a while, on the Omnia (not mine, mind you, as I disabled GPIO IRQs as a workaround). It really needs to survive spurious interrupts.
<rsalvaterra> I'm going to try and fix it myself.
feriman has joined #openwrt-devel
victhor has joined #openwrt-devel
Rene__ has quit [Quit: leaving]
ilario has quit [Quit: Leaving]
grift has quit [Quit: Bye]
grift has joined #openwrt-devel
grift has quit [Client Quit]
grift has joined #openwrt-devel
<Borromini> pkgadd: ping
CrazyLemon has quit [Ping timeout: 258 seconds]
CrazyLemon has joined #openwrt-devel
<rsalvaterra> Hm. The potential fix isn't trivial to backport. Whatever. I just diffed the v5.4 gpio-pca953x driver against the current v5.11-rc7 and made a patch. Hopefully it'll build/run.
<rsalvaterra> The world changed a lot between 5.4 and 5.11…
<Borromini> rsalvaterra: mt7621?
<Borromini> wait, the Omnia... that's mvebu right
csrf has quit [Quit: ZNC 1.7.2+deb3 - https://znc.in]
csrf has joined #openwrt-devel
Borromini has quit [Ping timeout: 272 seconds]
<rsalvaterra> Borromini: Yeah, mvebu.
<rsalvaterra> … and boom. Build failed. Oh, well…
<rsalvaterra> … speleology time.
mkresin has quit [Read error: Connection reset by peer]
mkresin has joined #openwrt-devel
<rmilecki> anyone here understands NAT / routing implementation defailts in Linux kernel?
<rmilecki> is that even possible to use multiple CPU cores for doing RX, NAT, TX?
<rmilecki> afaik it's not implemented
<rmilecki> but is that doable at all?
<rmilecki> so we get multiple CPU cores handle single TCP stream traffif
<rmilecki> nbd: ?
Borromini has joined #openwrt-devel
MichaelOF has quit [Quit: Konversation terminated!]
feriman has quit [Quit: WeeChat 3.0.1]
<nbd> rmilecki: a single stream needs to be pinned to one CPU, otherwise you get reordering
<rmilecki> nbd: is that possible to improve it anyway?
<rmilecki> not for me ofc, but for someone with good routing, nat, napi, skb, whatever knowledge?
nitroshift has joined #openwrt-devel
<nbd> rmilecki: well, the way to improve it is to make sure that as few cycles as possible are spent handling it
<nbd> i don't think it's worth trying to parallelize a single flow
<rmilecki> nbd: some devices have 2.5 Gbit Ethernet now but OpenWrt/Linux is still capable of doing only 800 - 900 Mb/s NAT
<nbd> what platform?
<rmilecki> nbd: even with optimized paths I'm afraid we won't hit 2000 - 2500 Mb/s
<rmilecki> BCM4908
<rmilecki> 4 x ARM A53
<nbd> how much can it do with multiple flows?
<rmilecki> i didn't get iperf2 yet, let me do testing later this week
_lore_ has quit [Ping timeout: 240 seconds]
_lore_ has joined #openwrt-devel
feriman has joined #openwrt-devel
<nbd> make sure you don't run iperf on the router itself
<nbd> and if you have some time, you could make a perf flamegraph
<nbd> to narrow down where the bottleneck is
_lore_ has quit [Ping timeout: 272 seconds]
<nbd> i've merged an updated version of the netfilter flow offload code to my staging tree 5.10 kernel
<nbd> maybe it'll help as well
_lore_ has joined #openwrt-devel
<nbd> and i'll pull in the latest version of napi threading support as well
<plntyk> with >1Gbit there are some effect of jumbo frames on single flow too
<plntyk> so the "PPS" packet per second might be relevant to compare since some firewalls have these benchmarks beside Mbit/Gbits too
Darkmatter66 has quit [Ping timeout: 240 seconds]
adrianschmutzler has joined #openwrt-devel
qdel has joined #openwrt-devel
koniu has quit [Remote host closed the connection]
koniu has joined #openwrt-devel
valku has joined #openwrt-devel
nitroshift has quit [Quit: Gone that way --->]
valku has quit [Quit: valku]
valku has joined #openwrt-devel
<rsalvaterra> Borromini: The gpio-pca953x backport requires me to frob with the bitmap library… I only added API, so it should be fine.
* rsalvaterra can't wait for Linux 5.10 to hit master…
Jusic has joined #openwrt-devel
<Borromini> :)
<Borromini> i switched to master thinking we'd get to 20.xx or 21.xx rather quickly :P
<Tapper> Borromini You just made me chuckle!
<Tapper> Borromini I have bin using OpenWrt since BB so....
Rene__ has joined #openwrt-devel
<Borromini> Tapper: if we're doing e-penises, i since 10.03 :P
<Tapper> Borromini so long! hahahah
<Borromini> yeah getting old xD
danitool has joined #openwrt-devel
<owrt-snap-builds> build #744 of malta/be is complete: Failure [failed tools] Build details are at http://buildbot.openwrt.org/master/images/builders/malta%2Fbe/builds/744 blamelist: INAGAKI Hiroshi <musashino.open@gmail.com>, John Audia <graysky@archlinux.us>
jlsalvador has joined #openwrt-devel
<rsalvaterra> Borromini: I miss the cocktail version names… :P
jlsalvador has quit [Quit: WeeChat 3.0]
jlsalvador has joined #openwrt-devel
<jlsalvador> Hello. I just received an ubnt unifi 6-lr. Is there currently someone working to port openwrt to it? Do you need help with something (ex: mtd dump)?
<Borromini> jlsalvador: https://git.openwrt.org/?p=openwrt/staging/blocktrron.git;a=summary
<Borromini> if you bought it blindly, you're a *very* lucky guy.
<blocktrron> Borromini: :)
<jlsalvador> Borromini: Hehe, I wasn't fast enough. :)
<jlsalvador> BTW, blocktrron thank you!
<blocktrron> FunFact about this device: It has an Aquantia AQR112 2.5G PHY which Ubiquiti crippled to 1 Gbit/s in software
<blocktrron> I'm seriously interested in the stuff their PM smokes
<jlsalvador> blocktrron: Why ubnt software-limit it? To prevent thermal problems?
<blocktrron> Most likely so they don't piss off their hardcore fans who bought the Early Access LR
<blocktrron> The LR which is on the market was intended to be the U6-Pro
<blocktrron> But yeah, I've ordered a 2.5G Adapter, which is set to arrive on monday to see whetehr or not 2.5G works
<blocktrron> sadly linux has no support for this PHY, so we will have to see
<jlsalvador> It's a good reason. I think that Ubnt its more PR than tech-y.
<jlsalvador> Oh! You lifted the restriction? :D
Darkmatter66 has joined #openwrt-devel
Darkmatter66 has quit [Read error: Connection reset by peer]
Darkmatter66 has joined #openwrt-devel
joaohcca has joined #openwrt-devel
<Borromini> credit where credit is due eh blocktrron ;)
<blocktrron> well, technically 2.5G should work with the hardware, I'm just not sure whether or not the PHY will advertise it.
<blocktrron> If not, I'll either have to find a datasheet, wait for someone with one to add this PHY to the linux driver or hope the U-Boot sources supporting this PHY work with 2.5G
<Hauke> blocktrron: the 10G Aquantia Phys need some special FW and this FW can restrict the supported modes
<Hauke> is the FW loaded at runtime or is theer an extra SPI flash?
<Hauke> or is there no extra FW needed for this PHY
<blocktrron> Hauke there are indeed two SPI flashes
<blocktrron> i can dump the firmware of the second one, as it's a multilayer PCB i can't say for yure whether or not it is wired to the marvell PHY
valku has quit [Remote host closed the connection]
valku has joined #openwrt-devel
joaohcca has quit [Quit: Connection closed]
<blocktrron> The host system does not interact with the PHY at all. It's configured for a reference board with a RTL switch
joaohcca has joined #openwrt-devel
philipp64 has quit [Quit: philipp64]
<Hauke> blocktrron: why does it use a RTL switch and a Aquantia PHY? The RTL switch has integrated PHYs and only supports 1G on the LAN ports
<blocktrron> Hauke: It doesn't have a RTL switch at all. The U-Boot as well as the kernel are however configured for an RTL switch
<Hauke> do you see the PHY on the MDIO bus?
<blocktrron> The Phy is at ID8 on the MDIo bus, yes
<Borromini> blocktrron: and it's a production device? as in: available to consumers?
<Borromini> you didn't get your hands on some early dev version? (just curious)
<blocktrron> It also does not detect link state in the OS at all, the link is fixed to 1G
<blocktrron> Borromini: nope
<rsalvaterra> Hmpf… My gpio-pca953x backport patch is weighing at about 27 kiB. Not great, not terrible…
<joaohcca> tmn505 just a follow up from what we discussed on tuesday. The device kept the config after a flash so I believe that the filesystem marker found at 0x0 is ok to ignore. I've try to remove my dts node with the wdt declaration but I the device enter a bootloop as I mentioned.  do you have any other sugestions to ignore de node imported from the
<joaohcca> dtsi?
<joaohcca> I'm trying to port CF-E375AC from ar71xx to ath79, PR available https://github.com/openwrt/openwrt/pull/3319/ for reference the match file from ar71xx https://github.com/openwrt/openwrt/blob/openwrt-18.06/target/linux/ar71xx/files/arch/mips/ath79/mach-cf-e316n-v2.c#L356
dedeckeh has joined #openwrt-devel
philipp64 has joined #openwrt-devel
philipp64 has quit [Client Quit]
<tmn505> joaohcca: then the watchdog from dtsi needs to be enabled, but it's weird that it spews error when activating and works. Btw. the mach file You pointed activates watchdog by toggling gpio to high but Your dts uses low, maybe there's the issue?
<joaohcca> tmn505 I'll change to ACtive_high and test
joaohcca has quit [Quit: Connection closed]
joaohcca has joined #openwrt-devel
<joaohcca> tmn505 still got the same messages from the wdt-ath79 [    1.673024] ath79-wdt 18060008.wdt: unable to register misc device, err=-16
<joaohcca> [    1.680269] ath79-wdt: probe of 18060008.wdt failed with error -16
<joaohcca> my /dev has watchdog and watchdog0. Could be an issue when trying to register /dev/watchdog?
<tmn505> joaohcca: probably, if it doesn't reboot then it's somehow toggled. I'm out of ideas about this since I don't know much about it. Consider the support done, since all of the devices on the unit work.
<joaohcca> tmn505 I've seen this messages on other ported devices from COMFAST such as https://github.com/openwrt/openwrt/pull/1957
<tmn505> yeah, so don't bother Yourself with it too much.
<joaohcca> would like to understand what happen so if anyone has any suggestions feel free to drop a comment at the PR
<joaohcca> tmn505 thanks for taking some time for this, much appreciate
philipp64 has joined #openwrt-devel
Borromini has quit [Quit: leaving]
joaohcca46 has joined #openwrt-devel
joaohcca has quit [Quit: Connection closed]
joaohcca46 has quit [Client Quit]
philipp64 has quit [Quit: philipp64]
philipp64 has joined #openwrt-devel
Tost has quit [Ping timeout: 256 seconds]
joaohcca has joined #openwrt-devel
rmilecki has quit [Ping timeout: 240 seconds]
black_ant has quit [Quit: simplicity does not kill]
dedeckeh has quit [Quit: Connection closed]
<Hauke> nbd: do you have a better version of the package/kernel/mac80211/patches/subsys/300-mac80211-optimize-skb-resizing.patch patch which works better with mac80211 5.10?
<Hauke> joaohcca: I think the GPIO and the ath79 watchdig driver want to register a misc char device for the watchdog and it looks like only one is possible
Borromini has joined #openwrt-devel
Darkmatter66 has quit [Ping timeout: 264 seconds]
Acinonyx_ has joined #openwrt-devel
Acinonyx has quit [Ping timeout: 256 seconds]
<Borromini> nbd: sorry for the drive-by. i am still trying to find the commit causing the timeout errors on the mt7613 radio, but by now i'm essentially at 2021-01-14 and it looks like even that shows timeout errors, although the AP had been up over 24h now. my backup testing device isn't showing any timeout errors yet with the same build, but it's only been up half as long for now. will keep you posted.
<Borromini> bbl.
Borromini has quit [Quit: leaving]
joaohcca has quit [Ping timeout: 240 seconds]
feriman has quit [Ping timeout: 256 seconds]
Acinonyx_ has quit [Ping timeout: 240 seconds]
Acinonyx has joined #openwrt-devel
valku has quit [Quit: valku]
philipp64 has quit [Quit: philipp64]
philipp64 has joined #openwrt-devel
philipp64 has quit [Client Quit]
adrianschmutzler has quit [Quit: ~ Trillian - www.trillian.im ~]