ChanServ changed the topic of #aarch64-laptops to: Linux support for AArch64 Laptops (Chrome OS Trogdor Devices - Asus NovaGo TP370QL - HP Envy x2 - Lenovo Mixx 630 - Lenovo Yoga C630 - Lenovo ThinkPad X13s - and various other snapdragon laptops) - https://oftc.irclog.whitequark.org/aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
<deathmist>
JensGlathe[m]: thanks for the https://github.com/jglathe/linux_ms_dev_kit/tree/jg/ubuntu-qcom-x1e-6.15rc tree btw, I have "fully" working DP alt mode on all 3 ports (any orientation) now ofc with 2-lane bw limit for now. with two docks on different ports I now have two 1080p displays @ 120 Hz going :D
chrisl has joined #aarch64-laptops
shoragan_ has quit []
chrisl has quit [Ping timeout: 480 seconds]
shoragan has joined #aarch64-laptops
fantom has joined #aarch64-laptops
Core2298 has joined #aarch64-laptops
tstachecki has quit [Ping timeout: 480 seconds]
Core2298 has quit [Read error: Connection reset by peer]
tstachecki has joined #aarch64-laptops
xbjfk has quit [Read error: Connection reset by peer]
xbjfk has joined #aarch64-laptops
xbjfk_ has joined #aarch64-laptops
xbjfk has quit [Ping timeout: 480 seconds]
xbjfk_ is now known as xbjfk
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
hexdump0815 has joined #aarch64-laptops
hexdump01 has quit [Ping timeout: 480 seconds]
jglathe_angrybox has quit [Read error: Connection reset by peer]
tobhe_ has joined #aarch64-laptops
tobhe has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
<JensGlathe[m]>
That would be good, finally GPU acceleration on this one
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
xroumegue has quit [Ping timeout: 480 seconds]
xroumegue has joined #aarch64-laptops
xbjfk_ has joined #aarch64-laptops
xbjfk has quit [Ping timeout: 480 seconds]
xbjfk_ is now known as xbjfk
chrisl has joined #aarch64-laptops
erebion has left #aarch64-laptops [Disconnected: Replaced by new connection]
erebion has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
martiert_work has quit [Quit: WeeChat 4.6.2]
martiert_work has joined #aarch64-laptops
jhovold has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
pabs has quit [Ping timeout: 480 seconds]
<kuruczgy[m]>
tobhe: I just checked and there is still no such option in Lenovo Vantage on the slim7x :/ But that's good to know that at least two laptops offer this, it means the underlying support is there.
<kuruczgy[m]>
The most convenient would be if PMIC GLINK just had an option for this... not sure what the protocol is like, is it hopeless without documentation, or are there any ways to discover GLINK interfaces?
chrisl has quit [Ping timeout: 480 seconds]
ravikant_ has joined #aarch64-laptops
sgerhold has joined #aarch64-laptops
icecream95 has joined #aarch64-laptops
SpieringsAE has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
erebion has left #aarch64-laptops [#aarch64-laptops]
erebion has joined #aarch64-laptops
martiert_work has quit [Remote host closed the connection]
martiert_work has joined #aarch64-laptops
pabs has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
pbrobinson has quit [Ping timeout: 480 seconds]
pbrobinson has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
<icecream95>
Heh, today I was on a brand-new bus, in-service since yesterday, and the passenger information display was showing an Android bootloader screen for RK3288.
<icecream95>
Wonder why they used a SoC so old that it's off-topic for this channel (being 32-bit). :)
<icecream95>
Maybe they needed FP64 support in the GPU? /s (Maybe I'll test that on the RK3288 I'm typing this on eventually.)
icecream95 has quit [Ping timeout: 480 seconds]
ravikant__ has joined #aarch64-laptops
ravikant_ has quit [Ping timeout: 480 seconds]
rmsilva- has quit [Ping timeout: 480 seconds]
<JensGlathe[m]>
Probably just embedded tech that works™️ and does the job
ravikant_ has joined #aarch64-laptops
ravikant__ has quit [Ping timeout: 480 seconds]
ravikant_ has quit [Remote host closed the connection]
ravikant_ has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
pbrobinson has quit [Remote host closed the connection]
pbrobinson has joined #aarch64-laptops
pbrobinson has quit [Remote host closed the connection]
pbrobinson has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
Core7377 has joined #aarch64-laptops
tstachecki has quit [Ping timeout: 480 seconds]
ravikant_ has quit [Ping timeout: 480 seconds]
tstachecki has joined #aarch64-laptops
Core7377 has quit [Ping timeout: 480 seconds]
tstachecki has quit [Read error: Connection reset by peer]
ravikant__ has joined #aarch64-laptops
tstachecki has joined #aarch64-laptops
ravikant__ has quit [Ping timeout: 480 seconds]
vanveldt has quit [Quit: IRCNow and Forever!]
chrisl has joined #aarch64-laptops
ravikant_ has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
Core8936 has joined #aarch64-laptops
tstachecki has quit [Ping timeout: 480 seconds]
tstachecki has joined #aarch64-laptops
Core8936 has quit [Read error: Connection reset by peer]
martiert_work has quit [Quit: WeeChat 4.6.2]
pbrobinson_ has joined #aarch64-laptops
pbrobinson has quit [Read error: Connection reset by peer]
martiert_work has joined #aarch64-laptops
Nicholas[m] has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
<jhovold>
Here's an updated wip branch for the X13s:
<JensGlathe[m]>
It has now added EC support for the Yoga Slim 7X, not quite sure about the config (should do though since its Ubuntu X1E config)
<JensGlathe[m]>
Thinkbook 16 has a different panel driver, still working on backlight support
<JensGlathe[m]>
The Samsung panel driver appears to ensure clean suspend/resume, that's something
<JensGlathe[m]>
Oh and all that digging resulted in an entry for the panel (CMN 0x162b, N160JCE-ELL) and an EDID read from the panel (not the one in DSDT)
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
Caterpillar has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
<steveej[m]>
is there any chance something in the 6.15-rc line breaks hardware acceleration in firefox or is the issue likely in userland? i can't play any media there unless i disable hw accel
<JensGlathe[m]>
I'm on edge/latest and this happens from time to time
<steveej[m]>
if have /run/opengl-driver/lib/dri/msm_dri.so, though nothing else that has an msm_ prefix in there
chrisl has joined #aarch64-laptops
rmsilva has joined #aarch64-laptops
<robclark>
steveej[m]: hw video acceleration is not based on mesa... it is not part of the GPU
<robclark>
so vainfo won't find anything ;-)
<robclark>
but maybe firefox supports v4l2 directly or indirectly)?
chrisl has quit [Ping timeout: 480 seconds]
jhovold has quit [Ping timeout: 480 seconds]
<anthony25>
steveej[m]: I think it's userland, I didn't have the problem
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
tstachecki has quit [Ping timeout: 480 seconds]
<kuruczgy[m]>
I am seeing an issue where after exiting initrd, only one of two connected displays probes properly (replugging fixes). I assume the GMU and SQE firmwares are deps for dp altmode so that's fine, but there is some weirdness when displays are probed right after mounting the root partition and loading the FWs.
<kuruczgy[m]>
In EL2 I get "[drm:msm_dp_bridge_get_modes [msm]] ERROR failed to get DP sink modes, rc=0" (the display lights up but with a really low res mode)
<kuruczgy[m]>
In EL1 I get a link training error and it doesn't light up at all
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
<robclark>
kuruczgy[m]: gmu/SQE/zap fws are not required for display.. but adsp is involved somehow
<kuruczgy[m]>
robclark: Hm... then maybe `drm_dp_aux_bus` is the difference between initramfs and non-initramfs? I don't have that module in the initramfs. (It can't be adsp since in EL2 no adsp fw loading should be happening anyway.)
<kuruczgy[m]>
But either way, I don't necessarily want dp altmode in initramfs, I just want the displays to come up properly after initramfs. (Obviously this is a very minor issue in the grand scheme of things, I just wanted to mention it.)
<robclark>
so any module the driver depends on would prevent probing, implying that the driver probably doesn't probe successfully until after initrd and before that you are getting efifb
mbuhl has quit [Remote host closed the connection]