<robimarko>
rmilecki: Would it be possible to extend the U-Boot NVMEM parser so its able to parse MAC-s from custom variable names as well?
<robimarko>
I am seeing a decent number of devices that have MAC-s stored under non-standard naming so simply matching for "ethaddr" to post-process as its in ASCII is not enough
rua has quit [Quit: Leaving.]
floof58 has joined #openwrt-devel
dgcampea has quit [Remote host closed the connection]
fakuivan has quit [Remote host closed the connection]
fakuivan has joined #openwrt-devel
dgcampea has joined #openwrt-devel
dgcampea is now known as Guest1629
dgcampea has joined #openwrt-devel
Guest1629 has quit [Remote host closed the connection]
<SpectreDev_01>
10.729864] hsl_phy_phydev_get[798]:ERROR:phy_addr 5 phydev is NULL
<SpectreDev_01>
robimarko: I was able to get smem to parser 27 of the partition I gues ubl has to be hardcoded and I labelled ethernet port but only eth0 shows up and none of them seem to work
<SpectreDev_01>
[ 11.779602] hsl_phy_phydev_get[798]:ERROR:phy_addr 5 phydev is NULL
<SpectreDev_01>
[ 12.809616] hsl_phy_phydev_get[798]:ERROR:phy_addr 5 phydev is NULL
<SpectreDev_01>
[ 13.839608] br-lan: port 1(eth0) entered disabled state
<SpectreDev_01>
[ 13.839564] br-lan: port 1(eth0) entered blocking state
<stintel>
documentation is meh. I vaguely remember the scripts help options being more helpful.
<minimal>
I just happened to notice that OpenWRT (23.05.0-rc3) is still using MD5 for passwords and am really surprised. I'd assumed it would be using SHA512.
<SpectreDev_01>
stintel: but there's fw extractor for Ath11k from what I can see
<Znevna>
minimal: I'm really surprised you didn't read the forum topics about this subject
<robimarko>
SpectreDev_01: You dont extract it, you wrap it with the ath11k-bdencoder
<SpectreDev_01>
Oh ok
<minimal>
Znevna: haven't search the forum about it yet
<robimarko>
SpectreDev_01: Easiest way being you take one of the BDF-s from the OpenWrt BDF repo
<robimarko>
Unpack it with the -e option, delete the .bin
<robimarko>
And then modify board-2.json for your board
<robimarko>
Then you can just wrap yours with -c
robimarko has quit [Remote host closed the connection]
<minimal>
Znevna: are you referring to the "Passwd -a sha256|sha512 less secure than def..." discussion? If so well Alpine also used musl, dropbear, openssh, etc and used sha512 by default so they've managed to address an issues. The only different with OpenWRT would likely be luci-related
<SpectreDev_01>
Guys how do I find the board ID etx
rmilecki has quit [Quit: Konversation terminated!]
rmilecki has joined #openwrt-devel
rmilecki has quit []
rmilecki has joined #openwrt-devel
rmilecki has quit []
rmilecki has joined #openwrt-devel
rmilecki has quit []
rmilecki has joined #openwrt-devel
gladiac is now known as Guest1654
gladiac has joined #openwrt-devel
Guest1654 has quit [Ping timeout: 480 seconds]
<SpectreDev_01>
Alright I created board-2.bin how do I turn that into .ipq file
philipp64 has quit [Quit: philipp64]
Lechu has joined #openwrt-devel
filimonic has joined #openwrt-devel
floof58 has quit [Ping timeout: 480 seconds]
philipp64 has joined #openwrt-devel
<Lechu>
Anybody using Debian 12 for builds? I've stumbled upon strange build error with uqmi:
<Lechu>
Back at Debian 11 it seems to have worked. This is using today's main.
floof58 has joined #openwrt-devel
philipp64 has quit [Ping timeout: 480 seconds]
philipp64 has joined #openwrt-devel
<KanjiMonster>
Lechu: are you sure this is related to debian 12? Looks more related to using GCC 11 instead of 12 (the default)
rua has quit [Remote host closed the connection]
rua has joined #openwrt-devel
<SpectreDev_01>
How do I find the Gpio pins used for WiFi
Shados has quit [Ping timeout: 480 seconds]
Shados has joined #openwrt-devel
<SpectreDev_01>
Got WiFi working
<Lechu>
KanjiMonster: tried on another machine, with freshly installed Debian 12 again, and it worked. Did "make distclean" and updated toolchain according to the wiki, let's see now.
<Lechu>
I wonder why gcc-multilib is among the recommended packages, this caused my mips and armhf cros-toolchains to be removed
<slh>
Lechu: you probably won't need it
<slh>
at least my tpyical package set can do easily without multilb
<Lechu>
I'll restore those cross-toolchains then, I actually use them for some stuff on this machine, unlike gcc-multilib.
goliath has quit [Quit: SIGSEGV]
<slh>
unless you need nodejs packages, gcc-multilib won't be necessary
<Lechu>
Gaah, indeed, 'twas the case. GCC 11 selected in .config.
<Lechu>
Not sure how those options snuck into my defconfigs for development builds, but now I nuked them, so this should work again.