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]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
tobhe_ has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
tobhe has quit [Ping timeout: 480 seconds]
chrisl has quit [Ping timeout: 480 seconds]
Allan has joined #aarch64-laptops
Allan has quit []
tobhe has joined #aarch64-laptops
hexdump0815 has joined #aarch64-laptops
tobhe_ has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
<kuruczgy[m]>
Good to hear that there are now working camera patches for the slim7x.
<kuruczgy[m]>
Hopefully will have time to also test it out in a couple days.
<kuruczgy[m]>
In the meantime, what's the deal with the green camera images? I read that this is an issue with debayering, correct?
<kuruczgy[m]>
I don't get how that works. If the camera is sending raw sensor information, every pixel is just a raw scalar value at that point, and the concept of color shouldn't even exist at that point?
<kuruczgy[m]>
The image being "green" sound more like some broken debayering to me. Where in the stack is debayering supposed to happen?
chrisl has joined #aarch64-laptops
eluks has quit [Remote host closed the connection]
eluks has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
etehtsea has quit [Read error: Connection reset by peer]
etehtsea has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
<JosDehaes[m]>
Jens Glathe: external screen also works. Tested at home with 1440p60 screen, working fine and mouse/kb pass through same cable. External screen is not scaled correctly though (this may be a GNOME issue?). At work, I could drive 2 1440p60 screens but also here the external screens are scaled like 150% or even 200% even though they are set to 100% in GNOME settings. Changing scaling and applying locks up GNOME settings, and the
<JosDehaes[m]>
scaling is not applied
<JensGlathe[m]>
I see similar issues here if I try to go for fractional scaling.
<JosDehaes[m]>
is it a driver issue you think?
<JensGlathe[m]>
Not sure.
<alexVinarskis[m]>
Fractional scaling works very well here (150% on internal screen, 100% external), but im using Wayland on Gnome with Ubuntu 24.10, 25.04 concept.
<JosDehaes[m]>
I'm also using GNOME on wayland. Arch linux though (but that should not matter)
chrisl has joined #aarch64-laptops
ravikant_ has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
davidinux has joined #aarch64-laptops
jhovold has joined #aarch64-laptops
<Pengyu[m]>
alexVinarskis: I saw your aeob helper occasionally, good jobs. Some suggestions. Actually, there are several aeob blocks in qcdx ext drivers, you can decompile it, it is important for panel bringup. I think these laptops are QRD based, so mtp things can be dropped.
ravikant__ has joined #aarch64-laptops
ravikant_ has quit [Ping timeout: 480 seconds]
<JeromedeBretagne[m]>
Panel bring-up, I am interested (still for the Surface Pro 9 5G)! Any checks / instructions to run?
chrisl has joined #aarch64-laptops
<alexVinarskis[m]>
Pengyu: indeed, these are QRD based. Thought to keep everything though just in case. By several blocks ,you mean additional ones that are not yet in the repo? Do you have sample names? Else I could try to decompile every .bin there is haha
ravikant__ has quit [Ping timeout: 480 seconds]
<alexVinarskis[m]>
jdb: yes, its the thing i mentioned to you before, check out readme https://github.com/alexVinarskis/qcom-aeob-dumps. If you can open PR with decompiled files, I could help analyze them.
chrisl has quit [Ping timeout: 480 seconds]
hwpplayer1 has joined #aarch64-laptops
<Pengyu[m]>
<JeromedeBretagne[m]> "Panel bring-up, I am interested..." <- for sc8280xp, check qcdxkmext8280_qrd.bin, splitting it, every block starts with AeoB headers. I can't get a computer nowadays. So you are on your own.
<Pengyu[m]>
After splitting, use tools from gus
<Pengyu[m]>
alexVinarskis: may be qcdxkmext8380_qrd.bin
<Pengyu[m]>
I never checked all binary files. But there may be other grouped AeoB files,
<alexVinarskis[m]>
ohh thats a great tip, thanks. Didn't realize they could combine multiple AeoBs together. Will check that over the weekends.
<Pengyu[m]>
Thanks. Nowadays, I am busy with real life things. Then I am counting on you.☺️
ravikant_ has joined #aarch64-laptops
davidinux has quit [Ping timeout: 480 seconds]
hwpplayer1 has quit [Remote host closed the connection]
hogliux has joined #aarch64-laptops
ravikant_ has quit [Ping timeout: 480 seconds]
hogliux_ has joined #aarch64-laptops
Caterpillar has quit [Quit: Konversation terminated!]
hogliux has quit [Ping timeout: 480 seconds]
svarbanov_ has quit [Remote host closed the connection]
enyalios_ has joined #aarch64-laptops
enyalios has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
<JeromedeBretagne[m]>
<alexVinarskis[m]> "weird thing is that one of the..." <- alexVinarskis: I can confirm that backlight is still working with a more minimalist patch, when removing the nodes mentioning GPIO 9 (as you had shared on pastebin), good point. I will clean up and simplify my earlier commit
<JeromedeBretagne[m]>
<alexVinarskis[m]> "jdb: yes, its the thing i..." <- I will have a look!
hogliux_ has quit [Quit: Leaving]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
ravikant_ has joined #aarch64-laptops
ravikant_ has quit [Remote host closed the connection]
<efenex>
work. The ubuntu post indicates livefs-editor should work, but I'm not sure what I need to replace where in order to get the custom kernel to be used. Anyone who's done this before has some pointers or some livefs-editor commands in their history that they can share? :)
<alexVinarskis[m]>
jdb: could you share every .bin file from windows in dm? I can go over the weekends to decompile known AeoB files but also try to get combo AeoB as per Pengyu suggestions.
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
ektor52 has joined #aarch64-laptops
<JeromedeBretagne[m]>
yes, I was looking at the README.md at the moment to extract the files, I was wondering where they are located on the Windows partition
ektor5 has quit [Ping timeout: 480 seconds]
<JeromedeBretagne[m]>
I have seen some examples of files mentioned here so I will try to find the base directory:
<alexVinarskis[m]>
C:\Windows\System32\ is a good start. You can search for all .bin files, and then just copy them out to different folders. If i understood correctly, the tool mentioned will fail with combo AeoB files... so ill likely have to ask you to partially re-do this in a few days. But even the files already in the repo are a good start!
<exeat>
craftyguy: steev: Do I understand correctly that you have successfully updated the x13s bios with fwupdtool?
<steev>
exeat: si
chrisl has joined #aarch64-laptops
<exeat>
Nice :)
ektor5 has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
ektor52 has quit [Ping timeout: 480 seconds]
<steev>
it is quite nice, though i did not check what is actually new in it
<Pengyu[m]>
alexVinarskis: jdb Take x13s as an example, G0MD from qcdx ext binary.
<alexVinarskis[m]>
pengyu: will add to my repo if I find a better way to do this. If x13s's AeoBs aren't shared yet, mind opening PR to my repo? Would be nice to keep things in one place
<jhovold>
craftyguy: no news about x13s venus fw, I remind them every now and then
<Pengyu[m]>
alexVinarskis: Actually, I don't own a x13s, I downloaded x13s from Lenovo(because it can be compared to the mainline power sequence). You can download it, then extract it with innoextract.
<alexVinarskis[m]>
ahhh, though you did you for your machine. thanks. you can actually simply 7zip -e filename.exe to extract and flatten on linux directly.
<Pengyu[m]>
Got it👍
<JeromedeBretagne[m]>
alexVinarskis: Here is my pull request :-)
<JeromedeBretagne[m]>
ok, so 0x24 for gpio36, got it !
<alexVinarskis[m]>
actually you need 2nd instance of that gpio, 1st instance is the off state (LDOs are at 0, gpio at 0), next one LDOs have values, and gpio is 1, so its an active high. yes its just hex->dec.
<alexVinarskis[m]>
<Pengyu[m]> "1000078838.png" <- here Pengyu has very nice comments
<JeromedeBretagne[m]>
indeed, I had missed the comments in this picture, I'll need to read quietly tomorrow to see how it transforms into .dts nodes:
<JeromedeBretagne[m]>
s/:/!/
<JeromedeBretagne[m]>
Funny how it corresponds to the dsdt somehow but with some additional info in these files. I guess on Windows, using the .bin files takes precedence over the acpi tables as they are more detailed
<JeromedeBretagne[m]>
Next I need to see how to create 2 instances of the same gpio for the on and off states ("EXIT" and "ENTER"). Need to get some sleep for today. Thanks so much alexVinarskis !