<f00b4r0>
Adding SoB without authorisation is a big no-no imo
<Ansuel>
hope to get some NACK in the mailing list so we can take the dummy sob approach
<f00b4r0>
Ansuel: here's mine :D
<f00b4r0>
Ansuel: that being said, I'm not even sure about the dummy SoB. I don't see how you can satisfy a) b) or c); nor who (as a person) would assume this SoB?
srslypascal has quit [Quit: Leaving]
Piraty has quit [Ping timeout: 480 seconds]
Piraty has joined #openwrt-devel
srslypascal has joined #openwrt-devel
rua has quit [Ping timeout: 480 seconds]
rua has joined #openwrt-devel
<nbd>
why add a dummy SoB?
<nbd>
just leave out the SoB tag in the patches
<robimarko>
nbd: Would git-am allow applying those?
<nbd>
of course
<nbd>
git doesn't care about SoB tags
<robimarko>
Oh yeah, basically just From needs to be there
<nbd>
right. everything else is just text that's part of the commit description
<robimarko>
Then just leave out the SoB
<robimarko>
If somebody wants to send it upstream, just preserve From: and put your own SoB
<nbd>
for upstreaming, there needs to be a SoB that matches the From field
<nbd>
but that's just a matter of getting the original dev's permission when upstreaming it
<robimarko>
Well, thats gonna be an issue
<robimarko>
Cause, there are gonna be patches that you have no way of contacting the author
<robimarko>
I am sure we have those
<nbd>
if there is no way of contactin the author, just overwrite the From field and put a note in the description
<Ansuel>
they are hacks patch they will be reworked anyway
<Ansuel>
so i think we just have to add an header with from tag
srslypascal has quit [Ping timeout: 480 seconds]
srslypascal has joined #openwrt-devel
<ldir>
Does this look like illegal nft stuff? ' insert rule inet dscpclassify dscp_match meta l4proto { udp } th dport { 3478-3497 } th sport { 3478-3497, 16384-16387 } goto ct_set_ef comment "Facetime" '
<ldir>
I get the wonderful response "BUG: unhandled op 4
<Ansuel>
All-in-one platform: Integrates an 11ax radio, MAC and baseband, plus a quad-core 64-bit A53 CPU and dual-core network accelerator to provide a fully-offloaded 11ax subsystem. The 14nm design provides power and size advantages, while a wide range of external WAN and media interfaces allows customers to build a full portfolio of 802.11ax products.
<robimarko>
I can tell you that it looks like GlobalFoundries makes it
<\x>
I do wonder on how much wifi 6/6e adoption got hampered by chip shortage
goliath has quit [Quit: SIGSEGV]
<Namidairo>
I suspect widespread adoption may not take place until after dbdc wifi 7 radios become widespread.
shibboleth has joined #openwrt-devel
<Namidairo>
and adoption is so low that I just found a jurisdiction that needs a patch sent upstream because nobody noticed 6e has been allowed for ~6 months
<\x>
US regdb is still NO-IR for it ahaha
<stintel>
anyone knows how to convince ax210 in OpenWrt to connect to a 5GHz AP ?
<\x>
on ax200 it just works, you set it to AX then client mode, no mods needed
<stintel>
everything is PASSIVE-SCAN in the self-managed regdb, I've modified OpenWrt scripts to disable scan_ssid and enable passive_scan still no luck
<stintel>
keeps going to the 2.4G network
<\x>
oh yeah, its hard to force if it has same ssid on 2.4 and 5ghz
<stintel>
*facepalm*
<stintel>
it's my LoRa gateway and it's on my IOT SSID which is 2.4 only
<stintel>
lol
<\x>
stintel: think you can see if theres a way to remove no IR on its 6Ghz? are you in a country where its fine to IR on 6GHz now?
<\x>
stintel: thanks for that test, so so far what i can see is that yeah it doesnt really accept the full table for your country. but it does accept the hinted country code.
<stintel>
np
<\x>
then after accepting the hinted country code, it still uses its embedded frequency table and rules
<\x>
hardware does allow ap on 6ghz as iw phy said but yeah we are at mercy of intel for the frequencies allowed.
<stintel>
/home/stijn/Development/OpenWrt/openwrt/staging_dir/toolchain-aarch64_cortex-a53_gcc-11.3.0_musl/lib/gcc/aarch64-openwrt-linux-musl/11.3.0/../../../../aarch64-openwrt-linux-musl/bin/ld: <artificial>:(.text.wpas_dpp_chirp_next.lto_priv.0+0x544): undefined reference to `crypto_ec_key_set_pub_point'
<\x>
theres that openwrt discord out there, I asked the guy for an iw list dump, but he never got back to me
<robimarko>
Price is good, I just wish shipping wasnt the same amount plus customs
<robimarko>
Oh, so Codico has AX cards from Compex available now
<stintel>
robimarko: mtk ?
<robimarko>
Nope, Compex is still QCA only
<stintel>
:(
<stintel>
I have those 8devices but the only device it fits in refuses to boot OpenWrt (BSAP-3040)
<robimarko>
I am dissapointed by those
<robimarko>
They were supposed to start shipping like 16 months ago
<stintel>
yeah :P
<robimarko>
Eventually I gave up on waiting for them
<stintel>
ordered in October, took delivery 2 weeks ago or so
<robimarko>
Not to mention the stupid form factor and 5V requirment
<stintel>
I was actually planning to cancel the order but then got a shipping notification
<stintel>
oh well
<stintel>
more stuff to collect dust 😂
<robimarko>
WLE3000HX ones look cool
<shibboleth>
anyone able to decipher the sysupgrade logic for wpa8630pv2? ever since the change to ath79-tiny i've been unable to sysupgrade +keep config
<shibboleth>
i'm running master and i'm upgrading from -tiny to -tiny, and still: openwrt-ath79-tiny-tplink_tl-wpa8630p-v2.0-eu-sq
<shibboleth>
uashfs-sysupgrade.bin
<shibboleth>
Tue Sep 20 16:08:22 CEST 2022 upgrade: The device is supported, but this image is incompatible for sysupgrade based on the image version (1.0->2.0).
<robimarko>
Ugh, Codico doesnt have the QCN9074 ones, only weaker models
srslypascal has joined #openwrt-devel
<stintel>
shibboleth: should contain more info in the message, probably swconfig -> DSA
<shibboleth>
not the case
<shibboleth>
lemme paste full output
<stintel>
The flash erase blocksize has changed to 4k from the 64k in previous versions,
<stintel>
...
<robimarko>
That would do it
<shibboleth>
yeah, i know
<shibboleth>
and i'm upgrading from master to master
<shibboleth>
tiny-to-tiny
<stintel>
that's the reason sysupgrade doesn't work
<shibboleth>
i've already done a "clean flash"
<stintel>
add option compat_version '2.0' in /etc/config/system
<stintel>
in config system section
<shibboleth>
nice, thanks
<stintel>
there is some logic to do that automagically but I failed to get that working
<shibboleth>
is this documented somewhere?
<shibboleth>
k
<stintel>
so when I changed compat_version for the m300 I wrote this in the commit message
<shibboleth>
stintel, why doesn't it just look in /tmp/board.json instead?
<shibboleth>
if you're already on -tiny/2.0, board.json will say 2.0
goliath has joined #openwrt-devel
<stintel>
dangole_: thoughts on https://git.openwrt.org/?p=openwrt/staging/stintel.git;a=commitdiff;h=c828f89d4c0900a792eec07dcf4910d407497eef ?
<dangole>
stintel: oh no, another fall-out of the v1/v2 split. odd that i didn't notice it when booting initramfs... please apply to both master and 22.03
<stintel>
dangole: thanks, shall I add your acked-by ?
Guest1016 has quit [Quit: Page closed]
<dangole>
stintel: yes, feel free to do that. thank you for taking care of it!
goliath has quit [Quit: SIGSEGV]
<stintel>
dangole: thanks for review/ack!
gladiac has quit [Quit: k thx bye]
robimarko has quit [Quit: Leaving]
<stintel>
Mangix: actually the problem was DPP related, I had a WIP patch enabling that in hostapd and apparently that requires something that wasn't enabled in wolfssl
<hurricos>
the numbers work. mpc85xx can no longer keep up though :^)
MaxSoniX has quit [Quit: Konversation terminated!]
<pepes>
Why not? In our Turris 1.x it works quite well, but it has 2 GB RAM, though and by last commit a few days ago, it might be able to use even 4 GB RAM.
SlimeyX has quit [Read error: Connection reset by peer]