<Mangix> 257 open PRs to 204
<Mangix> someone's not merging
parazyd has joined #openwrt-devel
tSYS has quit [Quit: *squeak*]
tSYS has joined #openwrt-devel
gch981213 has joined #openwrt-devel
rua has quit [Quit: Leaving.]
minimal has quit [Quit: Leaving]
floof58 has quit [Ping timeout: 480 seconds]
floof58 has joined #openwrt-devel
bookworm has quit []
bookworm has joined #openwrt-devel
floof58 has quit [Ping timeout: 480 seconds]
floof58 has joined #openwrt-devel
goliath has joined #openwrt-devel
ynezz has joined #openwrt-devel
robimarko has joined #openwrt-devel
xback has joined #openwrt-devel
Mangix has quit [Read error: Connection reset by peer]
rua has joined #openwrt-devel
swalker has quit [Read error: No route to host]
swalker has joined #openwrt-devel
mrkiko has quit [Quit: leaving]
mrkiko has joined #openwrt-devel
bluew has quit [Ping timeout: 480 seconds]
xback has quit [Ping timeout: 480 seconds]
<Ansuel> robimarko
<Ansuel> realtek fails to build
<robimarko> Ansuel: Yeah
<Ansuel> (not a surprise as always on each update)
<robimarko> Header is misisng
<robimarko> I abused the CI to find what fails
<Ansuel> correct usage of CI
<robimarko> Ansuel: Should be sorted now, I built localy for malta/be and all mac80211 kmods
<slh> semi-related, realtek as the SOCs we know so far can't do wireless anyways (no USB either) - and last I checked, hostapd fails to build as well
<Ansuel> btw robimarko if you have time can you check why the hell the zyxel doesn't have leds node??? i'm very confused by that
<robimarko> Ansuel: Which board?
<robimarko> Its Dynalink
<robimarko> Indeed its rather weird that the PHY LED-s are not visible in /sys/class/leds
<rmilecki> if anyone can help with downloading binary from a non-friendly git server, help is welcome
<rmilecki> see: [PATCH RFC] aquantia-firmware: package MediaTek's Aquantia AQR113C firmware
* rmilecki is running afk
<Ansuel> wth Public git server doesn't support git protocol (and so git archive)
<Ansuel> an idea might have been sparse-checkout with cone-mode disabled (to download the single file)
<robimarko> Ansuel: I have an idea why Dynalink LED-s are broken
<robimarko> There are 2 LED-s with function = "wan"
<robimarko> And no enumerator
<Ansuel> we should have some warning for the same name and led core appending stuff to it automatically
<Ansuel> to me it seems somehow led probing is failing? or even the general probe of the phy???
<robimarko> PHY is fully probed and the driver is attached
<Ansuel> do you have that device by chance?
<robimarko> Yeah
<robimarko> I am looking live
<Ansuel> oh! thank god... then if you have time one first test would be comment one of the 2 led and see if one magically appear
<robimarko> Just working on it
<Ansuel> thanks
<robimarko> And nope, removed the second LED and still none were registered
<robimarko> What code registers the LED-s?
<robimarko> Ok, its of_phy_leds
<Ansuel> hoped it was a node problem... well the next guess is that of_phy_leds is returning error
<Ansuel> (or not getting called at all)
xback has joined #openwrt-devel
<robimarko> Ansuel: Its not getting called at all
<robimarko> Because: # CONFIG_PHYLIB_LEDS is not set
<robimarko> Yeah, once I enabled it LED got registered
<Ansuel> o.O
<Ansuel> that is optional?
<robimarko> Its not
<robimarko> of_phy_leds is guarded by if (IS_ENABLED(CONFIG_PHYLIB_LEDS))
<robimarko> And CONFIG_PHYLIB_LEDS is disabled in the generic config
<robimarko> Only Filogic enables it
<Ansuel> no i mean we are not enabling CONFIG_PHYLIB_LEDS by default?
<robimarko> No
<Ansuel> oh... ok we disable it by default
<Ansuel> easy fix i guess
<robimarko> Yeah, already making a PR
<Ansuel> but i'm tempted to enable it globally
<robimarko> Does it depend on CONFIG_LEDS_CLASS?
<robimarko> CONFIG_PHYLIB is not globaly enabled
<robimarko> So you cant enable CONFIG_PHYLIB_LEDS
<Ansuel> depends on LEDS_CLASS=y || LEDS_CLASS=PHYLIB
<Ansuel> if we don't have phylib enabled than no go for generic...
<robimarko> Yes, its disabled in generic ofnig
<Ansuel> (we can still enable it globally as it would be dropped later but it would be something that will be dropped on the next guy that refresh the generic kernel config)
<Ansuel> so yes enable it only for qualcommax
<robimarko> Yes, it would get drop silently and then we are back at square one
<Ansuel> mh ? CONFIG_QCOM_NET_PHYLIB
<robimarko> No idea, that automagically appeared
<Ansuel> oh right the library
<Ansuel> gets selected automatically
<robimarko> Yeah, that is from the QCA PHY split
<Ansuel> meanwhile i feel i have some kind of curse in getting reviwers fight on each other everytime i send a patch ahahahah
<robimarko> Well, that tends to happen when everybody is looking at it from their subsystem point of view
minimal has joined #openwrt-devel
xback has quit [Ping timeout: 480 seconds]
xback has joined #openwrt-devel
rua has quit [Remote host closed the connection]
rua has joined #openwrt-devel
<xback> robimarko: I wonder if your mac80211 bump would fix the wifi 6E connection issues i'm seeing :-) giving it a try ..
<KanjiMonster> PHYLIB_LEDS isn't a user selectable symbol, so it doesn't matter if you set it in the linux config or not, its value will always be autocalculated on build
goliath has quit [Quit: SIGSEGV]
<robimarko> KanjiMonster, its definitively user selectable
<robimarko> I selected it via kernel_menuconfig
<robimarko> But you are right, upstream version is not user selectable
<robimarko> Which we dont have
<robimarko> xback: Any runtime testing would be great
<KanjiMonster> robimarko: ah, I only checked upstream. Didn't consider it might have been different previously
<Ansuel> the leds phy kconfig situation was a disaster... even reviwers had some problem in fixing the circular dependency
bbezak has quit [Quit: The Lounge - https://thelounge.chat]
bbezak has joined #openwrt-devel
h01ger has quit [Ping timeout: 480 seconds]
<robimarko> Ansuel: We should probably backport that commit in order to avoid having to enable the symbol per target
<Ansuel> will do
<Ansuel> easy enough
<Ansuel> btw i sent v6 just now
<robimarko> Yeah, just got the email
<Ansuel> if you want to take a look
<robimarko> Yeah, I will wait until patchwork indexes them, that is easier to look at
h01ger has joined #openwrt-devel
goliath has joined #openwrt-devel
<owrt-images-builds> Build [#52](https://buildbot.openwrt.org/images/#/builders/219/builds/52) of `master_ath79/generic` failed.
schmars[m] has joined #openwrt-devel
<hurricos> blocktrron: horrifying. Calendar set. Thanks.
Borromini has joined #openwrt-devel
<stintel> dhewg: it works for me, but otbr needs to be running, and for this you need to config it in /etc/network/interfaces
torv has quit [Remote host closed the connection]
torv has joined #openwrt-devel
torv has quit [Remote host closed the connection]
<Ansuel> rmilecki interesting to use mediatek to see if we can sort the aqr firmware licensing problem
torv has joined #openwrt-devel
<Ansuel> if they can sort that then we can also start producing working image for ipq related stuff
<rmilecki> Ansuel: i don't have high hopes
<rmilecki> Ansuel: i have bad experience with communication with MediaTek so far
<rmilecki> Ansuel: i was about upstreaming DT changes so far
<rmilecki> they ignore patches for months
<Ansuel> well the fact that they never provide a license or something like that makes me thing they just dropped the fw
<Ansuel> makes me think *
<rmilecki> Ansuel: does PHY have some EEPROM attached to it?
<rmilecki> AQR113C PHY I mean
<Ansuel> in ipq we always had the thing embedded in the firmware or present in a specific partition on the nand/spi
<rmilecki> I'm trying to understand Daniel's response
<rmilecki> Ansuel: i was aware of nand/spi flash
<Ansuel> afaik every aqr phy CAN have an attached spi to load the fw from
<rmilecki> i didn't know there is'may be EEPROM attached to PHY
<rmilecki> oh
<Ansuel> yes it can, but it's extra cost for the oem so it's not that common
<rmilecki> I guess it's unlikely in my board case then
<Ansuel> if the eeprom is attached to the phy then now fw needs to be loaded as it all works like magic (with strapping ping and all)
<Ansuel> no fw needs to be ...*
<rmilecki> oh, nice
<rmilecki> so it's even more unlikely
<Ansuel> OH GOD THE AMOUNT OF TYPO FK HELL
<Ansuel> yes it's the most simple configuration and the most sane one but it's not common
<Ansuel> they are probably used to see aqr mounted on servers or more premium switch
<Ansuel> and not on consumer router
<robimarko> I dont think that EEPROM is possible, but there could be an SPI-NOR
<robimarko> However in that case AQR would have loaded the FW automatically of it
<robimarko> But its commonly left out to save money
noltari has joined #openwrt-devel
nixuser has quit [Ping timeout: 480 seconds]
nixuser has joined #openwrt-devel
robimarko has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
Mangix has joined #openwrt-devel
filimonic has joined #openwrt-devel
bluew has joined #openwrt-devel
gch981213 has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
fakuivan has quit [Remote host closed the connection]
fakuivan has joined #openwrt-devel
FLD is now known as Guest1754
FLD has joined #openwrt-devel
Guest1754 has quit [Ping timeout: 480 seconds]
goliath has quit [Quit: SIGSEGV]
<Slimey> meh