ChanServ changed the topic of #aarch64-laptops to: Linux support for AArch64 Laptops (Asus NovaGo TP370QL - HP Envy x2 - Lenovo Mixx 630 - Lenovo Yoga C630)
<bamse>
steev: it used to be that you had to reconnect your external monitor 100% of the time...but i reduced the timout for how long the dp controller should wait before intiializing...so now it works sometime
<steev>
it works in next for me... which apparently does not have the data lanes patch, and it does not work for me when the data lanes patch is added in 6.2
<steev>
but it's SEEING it, just not... enabling?
<bamse>
steev: e.g. my tv always seems to work, but my monitor often is black until i start wayland (which does a scan of the hotplug state)
<steev>
i don't care *that* much about it
<clover[m]>
so steev don't rebuild kernel yet?
<steev>
no
<steev>
don't rebuild it yet
<clover[m]>
oki
<steev>
gonna go back to johan's stuff with my config
<bamse>
steev: if reconnect work, then it's in it's best possible working state right now
<bamse>
steev: there's a small window where if we get the hotplug event from usb, before dp controller is initialized, i have to throw the notification away
<bamse>
steev: fixing that will need some surgery on the dp controller...so i started poking at it, but realized that i wanted to see the current stuff really land before attempting anything more
<bamse>
steev: the side effect of such surgery should be that we power the dp controllers down if there's nothing connected on the usb...now they sit there idling, but powered up, always
<bamse>
so it's win-win
<steev>
in my defense... i didn't even notice it was "broken"; so you can see how much i really care
<steev>
i wanted to put out a new installer iso that supports the thinkpad, and the c630 at a minimum (i really need to go back to the flex at some point.... or throw it for sale on the line)
<bamse>
steev: vkoul is refreshing my flex dts patches...so hopefully we'll see that boot in 6.4
<steev>
oh nice
<steev>
i'd still kinda like to know why next works "fine" and 6.2 is iffy, but, tbh, if next works, that means eventually 6.3 will
<steev>
i've been debating that fancy screen they offer, the one that adds 2
<steev>
clover[m]: okay so, pushed out latest stuff, you can test if you want. this adds back the data lane things... and it should work. also the bluetooth regulators should properly... whatever if you reload the module
* clover[m]
rubs hands together
<steev>
tonight i might poke at the stuff that tim did for v2, and just... say fuck it, to our nvm not being found correctly. it works without it
systwi_ has quit [Ping timeout: 480 seconds]
laine has quit [Ping timeout: 480 seconds]
systwi has joined #aarch64-laptops
systwi has quit [Ping timeout: 480 seconds]
systwi has joined #aarch64-laptops
<clover[m]>
i rebuilt and... back to software rendering? trying a reboot
<clover[m]>
bluetooth, sound, external display working
<steev>
hm, shouldn't be
<steev>
dmesg output maybe?
<clover[m]>
[ 4.789721] msm_dpu ae01000.display-controller: Direct firmware load for qcom/a660_sqe.fw failed with error -2
<jhovold>
steev: linux-next also sets the data-lanes as the fixup patch does, changes in timing is more likely the reason for any difference you see with respect to the external display
<jhovold>
and if as bamse says, there's still a race wrt to hotplug detect, then such changes in behaviour are almost to be expected
<HdkR>
Wonder if that's why external display didn't come back after waking from sleep
<jhovold>
HdkR: I think I saw an error message in the logs that the drm driver failed to resume when I tried that
<bamse>
but it's really nice to see progress in this area, it's something that has been on the table for so many years now
svarbanov has quit [Ping timeout: 480 seconds]
<ajhalaney[m]>
bamse don't we all wish our problems would go away :P . But in all seriousness it is good to see it being discussed at least despite there being no clear solution going forward as far as I can tell
<bamse>
i agree, and while there's doesn't seem to be a clear solution, getting a good enough solution in place will be a good step forward
iivanov has joined #aarch64-laptops
<steev>
clover[m]: that's while you were actively using the bluetooth? e.g. sending some audio over it or movng the mouse around