<dwfreed>
it's at least fully specified, so you could make an ABNF from it
<f00b4r0>
I'm planning on a quick LALR validator, courtesy of flex/bison :)
<dwfreed>
heh
<dwfreed>
there is one thing not noted there; 'package' lines are only useful on import; you wouldn't normally use them in the actual /etc/config files
<f00b4r0>
*nod*
<mrkiko>
Ansuel: thanks a lot for the VDSL fix, I admit i should still understand how the reasoning goes for the macros part... I was worried we lost the VDSL part this time
froztbyte has quit [Remote host closed the connection]
c512l has joined #openwrt-devel
Daaanct12 has joined #openwrt-devel
Daanct12 has quit [Ping timeout: 480 seconds]
rz has joined #openwrt-devel
robimarko has quit [Ping timeout: 480 seconds]
robimarko has joined #openwrt-devel
gromero has joined #openwrt-devel
Daaanct12 has quit [Remote host closed the connection]
cmonroe has quit [Remote host closed the connection]
cmonroe has joined #openwrt-devel
rua has quit [Remote host closed the connection]
rua has joined #openwrt-devel
minimal has joined #openwrt-devel
goliath has quit [Quit: SIGSEGV]
Mangix has quit [Read error: Connection reset by peer]
gromero has quit [Quit: Leaving]
c512l has quit [Quit: c512l]
c512l has joined #openwrt-devel
xes has joined #openwrt-devel
c512l has quit []
c512l has joined #openwrt-devel
<mrnuke>
robimarko: When debugging QCA clock issues, do you have a method to go from dmesg error to the casue of the problem?
rz has quit [Ping timeout: 480 seconds]
<PaulFertser>
mrnuke: what do you mean, what kind of error?
<mrnuke>
PaulFertser: A variety of "status stuck at 'off'", "can't find a configuration for rate 125000000"
<mrnuke>
I should probable mention that I am using a frankenstein tree for IPQ95xx
<PaulFertser>
mrnuke: an obvious first idea would be to: git grep "find a configuration for rate"
<PaulFertser>
mrnuke: and if it's not obvious where it's called from you can add WARN_ON_ONCE(1) to see the backtrace at that moment
<mrnuke>
I get plenty of bactraces. They point to drivers/clk/qcom/clk-rcg2. But that's just a loop parsing the data structures grom other gcc-* and nss-* clock drivers. And I suspect something in those structures might be incorrect
<PaulFertser>
mrnuke: well see drivers/clk/qcom/clk-branch.c:87 and check manually if there's a configuration you need present in the source or wherever it's fetched from.
<PaulFertser>
But this is not missing rate, this is just clock not enabled, it tries to enable the clock but apparently checks and waits and it's still not enabled so "nss_cc_port5_rx_clk status stuck at 'off'"
<mrnuke>
I don't understand the reason for it being or not being enabled. I remember there being a workaround on older IPQ SoC, where .fw_name was used along with .name, but I don't understand that one either
robimarko has quit [Ping timeout: 480 seconds]
<philipp64>
jow: I tried to address your review comments where I understood them, but a couple weren't clear to me. Can you please update https://github.com/openwrt/libubox/pull/6 ?
philipp64 has left #openwrt-devel [#openwrt-devel]