<Tator>
I'm absolutely pulling my hair out trying to figure out how to compile an external kernel module for OpenWRT.
<Tator>
You can't build the SDK on the device because it doesn't have YACC, and the hell if I feel like attempting to build a toolchain just so that I can run into 20 other unanticipated problems.
<Tator>
And when you build it on a host system and call the makefile in the kernel source tree, it doesn't seem to know what configuration file to use. You could drop one in, I guess, but then it raises the question of whether the source tree is configured properly, and you'd might as well just go ask whether there is some offical way to do it.
<Tator>
But you know what? I'm just going to drop the .config file in the source tree and see what other 50 unexpected and incomprehensible errors occur.
kistlin has quit [Remote host closed the connection]
kistlin has joined #openwrt-devel
csrf has joined #openwrt-devel
mzvd has quit [Remote host closed the connection]
minimal has quit [Quit: Leaving]
kistlin has quit [Remote host closed the connection]
<PaulFertser>
Tator: there're examples of compiling external modules in the core repo.
<PaulFertser>
Tator: e.g. package/kernel/exfat/Makefile
<PaulFertser>
Or nat46
<PaulFertser>
Tator: instead of trying to trick the OpenWrt system I suggest you just follow along the established way.
<PaulFertser>
Tator: I have to warn you that if you're trying to build one of those out of tree realtek wifi drivers it's unlikely to be fruitful, they're a horrible mess.
<Tator>
Great. Typical. Thanks for the pointers.
mzvd has joined #openwrt-devel
schwicht_ has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
mzvd has quit [Read error: Connection reset by peer]
schwicht has joined #openwrt-devel
schwicht has quit []
mzvd has joined #openwrt-devel
mzvd has quit [Read error: Connection reset by peer]
mzvd has joined #openwrt-devel
gladiac has quit [Quit: k thx bye]
mzvd has quit [Read error: Connection reset by peer]
<mrkiko>
nbd: hi! Any news about the firmware thing? I supposed not yet, but was curious to know
AtomiclyCursed has quit [Quit: ZNC 1.8.2 - https://znc.in]
AtomiclyCursed has joined #openwrt-devel
robimarko has quit [Quit: Leaving]
mzvd has joined #openwrt-devel
<nbd>
mrkiko: the issue has apparently been reproduced and a fix is being worked on
bluew has joined #openwrt-devel
mzvd has quit [Read error: Connection reset by peer]
<Tapper>
So I am looking at pr10095
<Tapper>
ath10k: enable encapsulation offload by default
<Tapper>
Just how do people expect people to know how to use a thing if they never say how to switch it on or off?
srslypascal has quit [Quit: Leaving]
srslypascal has joined #openwrt-devel
<Ansuel>
Tapper sorry for being rude but again it's really a value changed by default... on the user side he will just notice the perf increase if it does use use ath10k that's all... can't understand all the mess
<Tapper>
Ansuel It's OK but why add it to openwrt then?
<Tapper>
OpenWrt does not even ship with the rite drivers.
<Tapper>
Ansuel I will switch to chatting on here if you like.
<dwfreed>
Ansuel: is -ct still needed for multiple APs on a single radio?
<Ansuel>
Various reason... example we have some community firmware that ship with ath10k and also an user can build its own image from master with ath10k... actually the 2 reason are 1. testing and checking if it does work 2. hope it does get some attention and ath10k-ct actually care to add support for it
goliath has joined #openwrt-devel
<Ansuel>
3. it's free... the patch is present upstream so we don't have to support it. so it's really 2 line to enable it. Can't see why we shouldn't enable it if someone for whatever reason wants to use ath10k
<Tapper>
Ansuel OK
<Ansuel>
problem of using ath10k is that in some situation is problematic and at times we notice ath10k-ct actually fixed some issue
<Tapper>
Ansuel So what you are saying now is that is I change my r7800 over to the ath10k driver then that will be offloading? I don't to have to change any thing on my end just the driver?
<Ansuel>
you should remove the ath10k-ct opkg and firmware and install the ath10k plain firmware and package
<Ansuel>
and you should be done
<Tapper>
OK thanks
Lechu has quit [Quit: changing servers]
Lechu has joined #openwrt-devel
<Ansuel>
np and i honestly hope we will finally have a working ath10k-ct firmware with that feature
<Tapper>
Ansuel I posted on the CT github asking for any news.
<Ansuel>
but i'm still negative about that, from what i remember that part of the code in the firmware is problematic and conflicts with the mgmt implementation of the ct firmware
mzvd has quit [Read error: Connection reset by peer]
<Slimey>
:P
<Ansuel>
stintel it's a pitty considering the hw :(
<Ansuel>
guess we can the same of broadcom but that's another nightmare
<mangix>
Ansuel: this RT-N16 has two drivers for it. The one that supports 802.11n only supports client mode
<Ansuel>
btw just added stmmac support for change the MTU with the interface running... it was a nice trip with fixing a qca8k bug and investigating ancient stmmac code
goliath has quit [Quit: SIGSEGV]
<Ansuel>
(also discovered the best way to stress an ethernet driver and check for stability --> while true; do free; done
<Ansuel>
Mangix: wth o.O
<mangix>
the funny part is, the client only driver is from broadcom
<Ansuel>
the other one is from ?
<mangix>
reverse engineered
<Ansuel>
ehehe
<mangix>
talking about b43 and brcmsmac
<mangix>
the latter is basically abandoned
<Ansuel>
anyway such thing still exist today... the intel ax210 driver
<Ansuel>
intel provided client only driver
<Ansuel>
on linux
<Ansuel>
on win you can totally use is as hotspot
<mangix>
well, it also does monitor mode
<mangix>
intel fixed packet injection after I mentioned it
<Ansuel>
oh wow
<mangix>
funny part is, intel driver just didn't work. mt76 actually crashed the system when injecting. nbd was nice enough to fix the bug in 8 hours or so.