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
philipp64 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]
srslypascal has quit [Ping timeout: 480 seconds]
srslypascal has joined #openwrt-devel
csharper2005 has joined #openwrt-devel
mzvd has joined #openwrt-devel
mzvd has quit [Read error: Connection reset by peer]
<csharper2005>
I would like to see 802.11k/v/r capabilities of the associated wireless clients in luci. Any ideas how I can get this information: using uci, other options?
srslypascal has quit [Quit: Leaving]
mzvd has joined #openwrt-devel
<russell-->
csharper2005: you might look around at /sys/kernel/debug/ieee80211/
<russell-->
or iwinfo or iw utilities
mzvd has quit [Read error: Connection reset by peer]
mzvd has joined #openwrt-devel
srslypascal has joined #openwrt-devel
mzvd has quit [Remote host closed the connection]
<csharper2005>
russell--: thanks for the ideas! I'll take a look.
<russell-->
possibly also hostapd
Tator has joined #openwrt-devel
mzvd has joined #openwrt-devel
tator_ has joined #openwrt-devel
mzvd has quit [Read error: Connection reset by peer]
Tator has quit [Quit: Page closed]
tator_ is now known as Tator
mzvd has joined #openwrt-devel
Tator has quit [Remote host closed the connection]
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
mzvd has quit [Read error: Connection reset by peer]
mzvd has joined #openwrt-devel
mzvd has quit [Read error: Connection reset by peer]
fda- has joined #openwrt-devel
fda has quit [Ping timeout: 480 seconds]
mzvd has joined #openwrt-devel
mzvd has quit [Read error: Connection reset by peer]
T-Bone has joined #openwrt-devel
f00b4r0 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
danitool has joined #openwrt-devel
mzvd has quit [Read error: Connection reset by peer]
<f00b4r0>
dunno about that but their hardware is usually really nice and well documented
<robimarko>
Not always
<robimarko>
Did they release the full Pi4 docs?
<f00b4r0>
*usually* :)
Misanthropos has quit [Ping timeout: 480 seconds]
<stintel>
Denver provided clear questions, ignored, suggested ways to improve the situation that would settle things, done differently. result: they still sorting out if we can legally publish the firmware in OpenWrt images
<stintel>
so yeah I'm pretty fed up with that
<robimarko>
They have various repos, most of which arent really traceable to the foundation at all
Misanthropos has joined #openwrt-devel
<robimarko>
So, yeah, I wouldnt distribute it as well until its cleared up
<robimarko>
Why dont they just send the fw to linux-firmware like for other models?
<stintel>
unfortunately radxa has similar issues with wireless firmware
<stintel>
I'm hoping the pine64 folks do a better job
<stintel>
haven't checked, but looking forward to their risc-v board
<robimarko>
Hopefully its in the affordable range
<stintel>
~60$ I read
<stintel>
waiting for the EU store to open
<robimarko>
Plus shipping and customs
<robimarko>
That is annoying me with their products, have a lot of them but slow shipping and customs are really annoying
<stintel>
and then I'm ordering some goodies, definitely the pinenote
<Habbie>
did anyone guess the name yet? :)
schwicht has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<stintel>
Star64 ?
<stintel>
maybe a specific star name
<Habbie>
oh, that's better than I've done
<Habbie>
it makes sense, yes
felix_ has joined #openwrt-devel
felix has quit [Read error: Connection reset by peer]
mzvd has joined #openwrt-devel
eduble has joined #openwrt-devel
mzvd has quit [Read error: Connection reset by peer]
mzvd has joined #openwrt-devel
<f00b4r0>
stintel: been reading the issue and the other one linked from there. Wow, so much drama. Does put you off indeed, *sigh*
mzvd has quit [Read error: Connection reset by peer]
<stintel>
and then I ask people to test and report back on the alternative I provided ... that seems difficult too
<stintel>
two have tried, but I assume they're failing
mzvd has joined #openwrt-devel
aleksander has quit [Quit: Leaving]
<f00b4r0>
i don't have a pi zero 2w, otherwise I'd have helped. Seems it's unobtainium these days too
<f00b4r0>
that aside, I really like the Pico. The PIO state machine is uber cool ;)
<csharper2005>
stintel: thanks!
<Habbie>
i have a 2w, but i haven't paid attention - anything i can help with?
<stintel>
I am running OpenWrt on my 2w since november or so
<Habbie>
ack
<Habbie>
i might give it a go
<stintel>
and I tested all 3 ways of adding the firmware as documented in the commit message
<stintel>
just need some other mortal to confirm the instructions work
<Habbie>
1 - wget+build, 2 - add files to a downloaded ext4 image, 3 - download a squashfs image and add files painfully?
<stintel>
also need to take change the firmware image for one of the chips, they apparently do some symlinking which is why I could not find one of them in the one branch
<stintel>
2 and 3 are meh because there are no prebuilt images
<Habbie>
right
<stintel>
but ones this commit goes in, the instructions should be valid
<stintel>
but you can build without doing 1
<Habbie>
ack - as downloads.openwrt.org will then build, but without the wgets
<Habbie>
yep
<stintel>
and then test 2 and 3
<Habbie>
got it
<stintel>
s/ones/once/
<stintel>
that's probably also the first properly documented way to access overlay from a non-OpenWrt device
<stintel>
I tried to find the offset differently but failed, binwalk doesn't seem to recognize f2fs
<f00b4r0>
stintel: reading the thread you linked before it seems symlinking is not necessary, they load from DTS based on chip ID?
<stintel>
a forum post hinted at losetup but getting that installed when your device has only wifi and no wifi firmware yet .. chicken egg
<stintel>
f00b4r0: but the firmware name in the buster repo is not the name they put in the dts ¯\_(ツ)_/¯
<stintel>
not sure what they smoking, I want some of it
<f00b4r0>
lol
mzvd has quit [Remote host closed the connection]
aiyion has quit [Remote host closed the connection]
aiyion has joined #openwrt-devel
mzvd has joined #openwrt-devel
Tator has joined #openwrt-devel
mzvd has quit [Read error: Connection reset by peer]
goliath has joined #openwrt-devel
Tator has quit [Remote host closed the connection]
mzvd has joined #openwrt-devel
Piraty_ has quit []
Piraty has joined #openwrt-devel
mzvd has quit [Read error: Connection reset by peer]
<stintel>
dual 10GbE copper NIC alternatives to Intel?
<stintel>
Broadcom P210TP
minimal has joined #openwrt-devel
<stintel>
lol HPE CN1200E 1.5k EUR 😂
<stintel>
and that doesn't look like copper
<SwedeMike>
stintel: why not intel?
<stintel>
diversity
<stintel>
I already have several Intel
<SwedeMike>
stintel: mellanox connectx-3 is one of the recommendations I've seen historically
<Habbie>
st-intel
<stintel>
stop taking intel?
<stintel>
:P
<stintel>
SwedeMike: thanks
<SwedeMike>
I haven't tested it myself, but the x-2 SFP+ were stable but a bit slow
<SwedeMike>
connectx-2
<stintel>
hmmm seems to be SFP+ based, prefer to avoid that
<stintel>
pfff P210TP Amazon.nl available but EUR459, Amazon.de EUR320 but out of stock
<stintel>
the price on Amazon.de is similar to the Intel X550-T2
<Habbie>
stintel, long story in PM - short story here, your commit message is fully approved - perhaps add 'mkdir -p files/lib/firmware/brcm' for the "build your own" variant as I was unsure it was correct, as I did not have a files/ dir at all
mzvd has joined #openwrt-devel
<stintel>
Habbie: thanks a lot!
<stintel>
I will probably update the commit with the newer firmware for 1 chip in the same branch as the other and your suggestion for mkdir and push it out
<stintel>
+ tomorrow
<stintel>
somewhere in that sentence
<stintel>
sorry, my weekend started and it's wine o'clock :D
<Habbie>
haha
<Habbie>
ok
<Habbie>
stintel, also, as mentioned earlier, it would be good if menuconfig mentioned the 2W
<stintel>
yeah
T-Bone has joined #openwrt-devel
f00b4r0 has quit [Read error: Connection reset by peer]
<Slimey>
ARM64 OpenWrt Linux-4.4.60
<Slimey>
another qca sdk user
<robimarko>
Good old QSDK "OpenWrt"
mzvd has quit [Read error: Connection reset by peer]
mzvd has joined #openwrt-devel
mzvd has quit [Read error: Connection reset by peer]
PaulFertser has quit [Ping timeout: 480 seconds]
robimarko has quit [Quit: Leaving]
PaulFertser has joined #openwrt-devel
gladiac has quit [Quit: k thx bye]
xes__ has joined #openwrt-devel
xes_ has quit [Ping timeout: 480 seconds]
mzvd has joined #openwrt-devel
mzvd has quit [Read error: Connection reset by peer]