mzvd has quit [Read error: Connection reset by peer]
wvdakker has joined #openwrt-devel
* russell--
is trying to figure out why my .config stub with openvpn-openssl is randomly not surviving a make defconfig
<russell-->
also, why tf i'd be getting a CONFIG_ZABBIX_POSTGRESQL=y in my .config
mzvd has joined #openwrt-devel
mzvd has quit [Read error: Connection reset by peer]
mzvd has joined #openwrt-devel
danitool has quit [Ping timeout: 480 seconds]
<mrnuke>
hurricos: I have a couple more realtek-poe PRs. No idea what to do about walterav's switch "Requesting Power" yet
mangix has joined #openwrt-devel
mzvd has quit [Read error: Connection reset by peer]
mzvd has joined #openwrt-devel
kistlin 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
mzvd has quit [Read error: Connection reset by peer]
csharper2005 has joined #openwrt-devel
<csharper2005>
Hi all. Is it ok to add support of 2 devices in 1 PR? Reasons: common recipes, scripts, dtsi. Devices are close to each other from the technical point of view.
slh64 has joined #openwrt-devel
<csharper2005>
commits will be separated of course
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]
gladiac has joined #openwrt-devel
mzvd has joined #openwrt-devel
mzvd has quit [Read error: Connection reset by peer]
lmore377 has quit [Read error: Connection reset by peer]
lmore377 has joined #openwrt-devel
mzvd has joined #openwrt-devel
mzvd has quit [Remote host closed the connection]
goliath 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]
dedeckeh has joined #openwrt-devel
goliath has quit [Quit: SIGSEGV]
mzvd has joined #openwrt-devel
valku has quit [Remote host closed the connection]
mzvd has quit [Read error: Connection reset by peer]
dedeckeh has quit [Remote host closed the connection]
mzvd has quit [Ping timeout: 480 seconds]
mzvd has joined #openwrt-devel
mzvd has quit [Read error: Connection reset by peer]
<rmilecki>
bcm53xx news: BCM4708 can do ~940 Mb/s NAT with flow_offloading=1; BCM47094 can do flow_offloading=0 940 Mb/s (CPU load 90%) and flow_offloading=1 940 Mb/s (CPU load 70%) :)
<rmilecki>
bad news: switching 5.10 -> 5.15 drops speed by 10% :/ some kernel regression
<rsalvaterra>
rmilecki: XDP is just a fastpath to avoid the kernel networking stack for very specific operations.
mzvd has quit [Remote host closed the connection]
mzvd has joined #openwrt-devel
<mrkiko>
rmilecki: do you still use the R6220 sometimes?
<mrkiko>
rmilecki: if you have JTAG access maybe you could help port the upstream u-boot to it since mt7621 support is available right now
mzvd has quit [Read error: Connection reset by peer]
<kistlin>
in ppp mode i could send AT commands with echo and read the response with cat, now after switching to QMI mode, echo/cat only works when i open a second terminal and let cat run, else i can't catch the response
<kistlin>
does someone know what it's about? :) can it be changed?
<kistlin>
there was also a bigger upgrade of OpenWRT, maybe it relates to that
<kistlin>
ppp was on the modules interface 1 "Modem interface For PPP connection and AT command transmission
<kistlin>
now i have to use interface 3 "AT interface For AT command transmission
mzvd has joined #openwrt-devel
mzvd has quit [Read error: Connection reset by peer]
danitool has joined #openwrt-devel
mzvd has joined #openwrt-devel
<rmilecki>
mrkiko: no JTAG here
mzvd has quit [Read error: Connection reset by peer]
srslypascal is now known as Guest3125
srslypascal has joined #openwrt-devel
mzvd has joined #openwrt-devel
mzvd has quit [Read error: Connection reset by peer]
Guest3125 has quit [Ping timeout: 480 seconds]
robimarko has joined #openwrt-devel
<russell-->
mrkiko: what kind of flash does it have?
<mrkiko>
russell--: nand flash
<mrkiko>
russell--: but do not remember manifacturer / model right now
rua has quit [Quit: Leaving.]
<russell-->
Macronix MX30LF1G08AA, looks like a tidal wave of pain
Sagi has quit [Ping timeout: 480 seconds]
rua has joined #openwrt-devel
mzvd has joined #openwrt-devel
rua has quit [Remote host closed the connection]
rua has joined #openwrt-devel
<stintel>
friendlyngeeks: my rpi02w is currently not online and I'm 500km away from home, but like I said, the camera-dummy-reg is the last message I see during boot. just press enter afterwards
<stintel>
[ 31.833602] cam-dummy-reg: disabling
mzvd has quit [Read error: Connection reset by peer]
rua has quit []
rua has joined #openwrt-devel
mzvd has joined #openwrt-devel
Sagi has joined #openwrt-devel
minimal has joined #openwrt-devel
Sagi has quit [Remote host closed the connection]
csharper2005 has quit [Remote host closed the connection]
<T-Bone>
stintel: pardon the silly question but what's the use for roaming on iot devices? Typically these are fairly immobile, aren't they? ;)
T-Bone is now known as f00b4r0
<stintel>
sysupgrading APs will result in the ESPs sticking to the AP that comes back online first
<f00b4r0>
ah, i see!
<stintel>
usteerd with option roam_trigger_snr -75 + 11v on the ESPs should fix that in my case :)
<karlp>
cute, just needed hooking up to the hardware stintel?
<stintel>
hmm?
<karlp>
the changes in esphome are mostly just hooking up the config options, so it was "easy"
<karlp>
just nice to gain functionality with that little work.
<stintel>
yes, esp-idf supports it
Sagi has joined #openwrt-devel
<Habbie>
stintel, nice!
<stintel>
added a bit about the usefulness for non-mobile clients in the comment
<stintel>
I might do MBO next, but after MBO lands in OpenWrt ;)
<f00b4r0>
i hear about usteer all the time, too bad it seems completely undocumented ;P
<stintel>
it's definitely not ideal, and it makes rather weird decisions, but there's a usteer2 in the making, if it's going to be equally undocumented I'll try to improve that
<f00b4r0>
👍
<stintel>
usteer2 is also the reason I will not invest time in trying to understand usteer1 code
<f00b4r0>
makes sense :)
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
dedeckeh 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 [Remote host closed the connection]
mzvd has joined #openwrt-devel
bluew 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
mzvd has quit [Ping timeout: 480 seconds]
mzvd has joined #openwrt-devel
mzvd has quit [Read error: Connection reset by peer]
ldir has joined #openwrt-devel
mzvd has joined #openwrt-devel
mzvd has quit [Read error: Connection reset by peer]
mzvd has joined #openwrt-devel
ldir has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
mzvd has quit [Read error: Connection reset by peer]