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
<icecream95> It seems that reading it does do a SCMI call, so I guess the firmware is just pretending throttling isn't happening
<icecream95> Doing this seems to be more accurate: perf stat -e task-clock,cycles timeout 3 openssl speed md5
hexdump0815 has joined #aarch64-laptops
<HdkR> icecream95: Pretty sure. It forces the scmi call so it should be updating unless the firmware actually is lying
hexdump02 has quit [Ping timeout: 480 seconds]
<HdkR> I don't have my X1E laptop in front of me to force it to throttle atm :P
chrisl has joined #aarch64-laptops
todi has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
shoragan has quit [Quit: quit]
shoragan has joined #aarch64-laptops
shoragan has quit [Read error: Network is unreachable]
shoragan has joined #aarch64-laptops
<icecream95> Oh that's fun, using perf I can see that cpu cores are running FASTER than what Linux thinks the frequency is!
<icecream95> Talk about broken firmware...
<icecream95> So the firmware can made core clusters go faster than the frequency set by Linux when thermal throttling! That sure makes a lot of sense.
<HdkR> :thonk:
<icecream95> My guess is that when throttling, frequency is completely firmware-managed, so it ignores anything set by the OS.
hexdump02 has joined #aarch64-laptops
hexdump01 has quit [Ping timeout: 480 seconds]
tobhe has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
tobhe_ has quit [Ping timeout: 480 seconds]
mbuhl has quit [Ping timeout: 480 seconds]
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
mbuhl has joined #aarch64-laptops
jgowdy_ has joined #aarch64-laptops
nios34 has quit [Quit: ZNC 1.8.2+deb2build5 - https://znc.in]
sally_ has joined #aarch64-laptops
nios34 has joined #aarch64-laptops
sibis92 has joined #aarch64-laptops
sally has quit [Read error: Connection reset by peer]
jgowdy has quit [Read error: Connection reset by peer]
sibis9 has quit [Ping timeout: 480 seconds]
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
svarbanov_ has quit [Read error: Connection reset by peer]
svarbanov has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
xbjfk has joined #aarch64-laptops
f_ has quit [Read error: Connection reset by peer]
f_ has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
icecream95 has quit [Ping timeout: 480 seconds]
ungeskriptet has quit [Remote host closed the connection]
ungeskriptet has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
Kelsar has quit [Quit: http://quassel-irc.org - Chat comfortably. Anywhere.]
Kelsar has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
<bryanodonoghue> kuruczgy[m] dmesg | grep ov02c
<macc24> so, does anyone have external display working on slim7x?
<JensGlathe[m]> anthony25: ^^
<kuruczgy[m]> macc24: me, but it's a coinflip whether the link training likes a particular adapter/monitor
<macc24> okay, thanks, is everything required on your github?
<kuruczgy[m]> [ 10.291274] ov02c10 11-0036: Error reading reg 0x300a: -6
<kuruczgy[m]> [ 10.291279] ov02c10 11-0036: failed to find sensor: -6
<kuruczgy[m]> bryanodonoghue: ^
<kuruczgy[m]> macc24: yep, this is the kernel package definition: https://github.com/kuruczgy/x1e-nixos-config/blob/main/packages/x1e80100-linux.nix
<bryanodonoghue> kuruczgy[m] could i trouble you for your latest full dmesg ?
<bryanodonoghue> and your kconfig ?
<macc24> kuruczgy: thanks i'll check it out. broke the internal display and i need some files from it before the lenovo folks can repair it :/
<kuruczgy[m]> bryanodonoghue: updated the above gist with the output of `cat /proc/config.gz | gunzip`
<kuruczgy[m]> macc24: Oh :/ Was it mechanical damage?
<macc24> yeah
<kuruczgy[m]> (Though for data recovery IMO either SSH or removing the NVMe drive would be simpler than getting dp altmode to work.)
<macc24> might as well get usb-dp working in cadmium while i'm at it
chrisl has joined #aarch64-laptops
krei-se has quit [Read error: Connection reset by peer]
chrisl has quit [Ping timeout: 480 seconds]
krei-se has joined #aarch64-laptops
jhovold has joined #aarch64-laptops
<anthony25> macc24: it worked for me, but only one port can push 4K 60hz
<anthony25> And the right port doesn't work for display port
<anthony25> It's also the case on windows, but I haven't tested the last BIOS update
<anthony25> (for windows, I mean dp-alt also doesn't work on the port on the right)
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
ranxlus has joined #aarch64-laptops
ranxlus has quit []
svarbanov has quit [Ping timeout: 480 seconds]
krei-se has quit [Ping timeout: 480 seconds]
krei-se has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
<bryanodonoghue> kuryczgy[m] and anthony25
<bryanodonoghue> kyruczgy[m]
<bryanodonoghue> could you guys try to confirm the sensors
<bryanodonoghue> on your windows partition
<bryanodonoghue> find . -name "*sensor*" -print | grep camera
<anthony25> I'll tell you that in a few hours
<bryanodonoghue> you can see dell ships ov02c10 and ov02e10
<bryanodonoghue> I experimented with getting the ov02c10 sensor to talk to my ov02e hardware
<bryanodonoghue> mostly to confirm the sensor driver works, powers on, gpios if correct will switch on the sensor
<bryanodonoghue> you can see with the diff
<bryanodonoghue> switch the CHIP_ID reg to 0
<bryanodonoghue> change the compat string
<bryanodonoghue> and the ov02c10 driver chokes on the returned ov02e CHIP_ID
<bryanodonoghue> which means the dtsi and sensor driver together do work
<bryanodonoghue> so I'm thinking perhaps slim7x doesn't have ov02c10
<bryanodonoghue> in my repo is v9 of ov02c10
<bryanodonoghue> v7 works with the dell xps
<bryanodonoghue> so...
<bryanodonoghue> when i run
<bryanodonoghue> find . -name "*sensor*" -print | grep cam
<bryanodonoghue> ./Windows/System32/DriverStore/FileRepository/qccamfrontsensor_extension8380.inf_arm64_6d0b43623cc44436/com.qti.sensormodule.ov02e10.bin
<bryanodonoghue> ./Windows/System32/DriverStore/FileRepository/qccamauxsensor_extension8380.inf_arm64_ed9e57b0ae5c35ca/com.qti.sensormodule.hm1092.bin
<bryanodonoghue> so the RGB and B+W sensors enabled ov02e10 and hm1092 are clear
<bryanodonoghue> need to see that output on slim7x to be sure we are trying to enable the right sensor ;)
<jhovold> steev: sounds good, thanks
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
<kuruczgy[m]> bryanodonoghue: ^
<kuruczgy[m]> I see ov02c10 and ov08x here
<kuruczgy[m]> According to the Omnivision website the ov02c10 is the one with the right res (1920 x 1080), the ov08x is bigger (3840 x 2400).
<kuruczgy[m]> slim7x datasheet claims it has a "FHD 1080p (2.0MP)" camera, so that matches up with the ov02c10
<anonymix007[m]> bryanodonoghue: doesn't seem to be working on T14s either, though the error is -110 here.... (full message at <https://matrix.org/oftc/media/v1/media/download/AeKW0J_-EDka3cTBxI_r8UgnxwBldGejt_9arCFePLmHVVGliGRwOb0L2Qherr8JkDIkYs0qHFsLn2PJGe0IWUNCeV58aQ4AAG1hdHJpeC5vcmcvVEpnalVWYVJwUVhKeXNxcHNNeE1NaGlD>)
pbsds has quit [Quit: The Lounge - https://thelounge.chat]
pbsds has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
jhovold has quit [Ping timeout: 480 seconds]
chrisl has quit [Ping timeout: 480 seconds]
svarbanov has joined #aarch64-laptops
<steev> jhovold: at this point it is 1 day 8 hours without
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
<bryanodonoghue> ok thanks let me check with the Dell XPS guy if the v9 ov02c10 still works for him
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
sally_ is now known as sally
bibikski has quit [Read error: Connection reset by peer]