nbd: from your mail it's not clear which wolfssl version bump breaked the ABI, was it the latest 4.5.0 -> 4.6.0 ?
nbd: you might be right about there still being issues with MT7613 and radar detection, it seems one of my APs is now seeing radar events on channel 36 (5180 MHz). I guess it's seeing neighbouring APs and wrongfully thinks that's radar stuff? https://paste.debian.net/1184504/ - the weird thing is the other test AP is on channel 36 as well and no DFS error messages like these there yet. that one
has been brought up earlier though. I've seen it complain about possible radars on channel 52 as well yesterday, which other APs are using, and they just stay on that channel without radar reports.
i'm doing some debugging for a spi-nor flash chip. is there a good way to send and recieve raw commands to/from it from inside openwrt? or will i need to hook it up to an external device eg a raspberry pi and do it from there? Thanks
gromero__ has joined #openwrt-devel
figgyc: it's probably easier to connect it to rpi and use flashrom to check if the chip is good, what ID it has etc.
figgyc: depends on what kind of debugging you're doing of course, and what does the kernel spinor driver prints you currently.
CrazyMelon is now known as CrazyLemon
Borromini: it shouldn't even be running the radar detector on channel 36
since it's not a DFS channel
figgyc: spi is not really command-oriented protocol, but you can write a simple userspace application using spidev to transmit/receive whatever you want. Shouldn't be needed with a regular m25p80 device.
yea I'm aware - not planning on looking at data, specifically just some obscure technical details about manufacturer ID's and stuff
csrf has joined #openwrt-devel
gromero__ is now known as gromero
figgyc: flashrom also supports jlink, ft232 and ch341 devices for that purpose, if you have one handy probably that'd be faster.
ynezz: in general, even if wolfssl aims to remain ABI compatible, i'm still worried about the failure case if an ABI change is missed
hard to debug segfaults or data corruption is so much worse than some extra churn on the buildbots
nbd: I've nothing against your proposal
it doesn't matter if it's wolfssl, openssl or mbedtls
carlomaragno has quit [Read error: Connection reset by peer]
HeN has quit [Ping timeout: 246 seconds]
Protagonistics__ has quit [Read error: Connection reset by peer]
novski has quit [Read error: Connection reset by peer]
nejon has quit [Ping timeout: 240 seconds]
feepo has quit [Ping timeout: 265 seconds]
arnd has quit [Read error: Connection reset by peer]
Tsesarevich has quit [Write error: Connection reset by peer]
carlomaragno has joined #openwrt-devel
novski has joined #openwrt-devel
Protagonistics__ has joined #openwrt-devel
arnd has joined #openwrt-devel
Tsesarevich has joined #openwrt-devel
HeN has joined #openwrt-devel
feepo has joined #openwrt-devel
nejon has joined #openwrt-devel
matteo has joined #openwrt-devel
matteo is now known as Guest18038
valku has joined #openwrt-devel
victhor has joined #openwrt-devel
nitroshift has quit [Quit: Gone that way --->]
nbd: i removed the if clause and now 36 isn't scanned for radar signals anymore. still seems to mistake other APs for radars, from what I can tell though. when you got time to have me test stuff or anything, let me know.
dorf has quit [Ping timeout: 264 seconds]
Borromini has quit [Quit: Lost terminal]
blb4393 has joined #openwrt-devel
koniu has quit [Remote host closed the connection]