robclark 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
rbraley has joined #aarch64-laptops
derzahl has quit [Ping timeout: 480 seconds]
derzahl has joined #aarch64-laptops
rbraley has quit [Ping timeout: 480 seconds]
kuter has quit [Quit: Leaving]
Lucanis has quit [Ping timeout: 480 seconds]
Lucanis has joined #aarch64-laptops
alpernebbi has quit [Ping timeout: 480 seconds]
alpernebbi has joined #aarch64-laptops
possiblemeatball has quit [Remote host closed the connection]
<colemickens> So the DTS patches, they'll get merged to linux-msm, and then later a batch "pull request" will ask that the linux-msm branch be merged into ... linux-next or something?
<colemickens> I assume strongz branch has more kernel goodies for x1e, but for example, the DTSs submitted upstream have better maching identifiers to be able to let Grub do its thing.
<bamse> colemickens: i apply the patches into arm64-for-x.y (or arm32-for-x.y etc...) of https://git.kernel.org/pub/scm/linux/kernel/git/qcom/linux.git/ and each time reset and merge all the *-for-x.y into the for-next branch...linux-next is regenerated a few times a week by merging my for-next with ~300 such branches...as we approach the merge window i tag each branch and send a pull request to soc@kernel.org...where arnd
<colemickens> I think the message is cut off? But I got the gist, thanks.
<bamse> colemickens: i pick patches, linux-next merges a few times a week for integration testing...i then send pull request to arnd, whom send pull request to torvalds
<bamse> colemickens: in other words, get strongz patches posted and reviewed on list and we'll pick them up as soon as we can
phire has quit [Ping timeout: 480 seconds]
phire has joined #aarch64-laptops
alfredo has joined #aarch64-laptops
rbraley has joined #aarch64-laptops
rbraley has quit [Ping timeout: 480 seconds]
alfredo has quit [Ping timeout: 480 seconds]
alfredo has joined #aarch64-laptops
srinik has joined #aarch64-laptops
phire_ has joined #aarch64-laptops
phire is now known as Guest550
phire_ is now known as phire
Guest550 has quit [Ping timeout: 480 seconds]
alfredo has quit [Ping timeout: 480 seconds]
juergh_ is now known as juergh
srinik has quit [Ping timeout: 480 seconds]
srinik has joined #aarch64-laptops
alfredo has joined #aarch64-laptops
kuter has joined #aarch64-laptops
phire has quit [Remote host closed the connection]
Kelsar has quit [Read error: No route to host]
Kelsar has joined #aarch64-laptops
srinik has quit [Ping timeout: 480 seconds]
phire has joined #aarch64-laptops
alfredo1 has joined #aarch64-laptops
alfredo has quit [Ping timeout: 480 seconds]
alfredo has joined #aarch64-laptops
alfredo1 has quit [Ping timeout: 480 seconds]
smpl has joined #aarch64-laptops
phire has quit [Read error: Connection reset by peer]
hightower3 has quit [Ping timeout: 480 seconds]
phire has joined #aarch64-laptops
kuter has quit [Quit: Leaving]
<kalebris> now that my fingerprint reader is working on my x13s with 6.10-rc6, I would need a trigger for when it's in calmshell mode so I can disable/enable it. I understand that acpi based triggers are not going to work. What are the options to trigger action(s) when the laptop lid is opened/closed?
<Jasper[m]> kalebris: The lid switch is connected over a GPIO pin and an input driver is in use
<Jasper[m]> You can get events from uhhh
<Jasper[m]> /dev/input
<Jasper[m]> and one of the devices should be the lid
<kalebris> cool, thanks Jasper[m]
<kalebris> and thanks to everyone who is working on aarch64 for linux
<Jasper[m]> kalebris: Unbound the "go to sleep" action in your DE and cat all devices while putting a magnet over the bottom of the laptop (or close it)
<Jasper[m]> If there's now garbage in the terminal it should have fired an event
<Jasper[m]> then you can use some other tools to script it, I think you can use udev for that? But other people know more about that I think
<kalebris> yeah, once I find something that changes when the lid is closed i can use the `busctl get-property "org.freedesktop.login1" "/org/freedesktop/login1" "org.freedesktop.login1.Manager" "LidClosed"` to get the current status of the lid
phire has quit [Remote host closed the connection]
phire has joined #aarch64-laptops
alfredo has quit [Ping timeout: 480 seconds]
<kalebris> not sure how universal is it but /dev/input/event0 seems to be the one that gets stuff when I open/close my lid, just fyi
Nios34[m] has joined #aarch64-laptops
<Nios34[m]> udev might tell you something about the lid thing
<_`[m]> still no configurable t14s huh grr - I don't think I could live with the missing pg dn pg up buttons 😲 or dedicated mouse buttons
<_`[m]> it's funny how such basic things can e.g. make me not buy superior hardware, like air m3
<_`[m]> did anyone buy a t14s yet?
<_`[m]> I saw it's the x1e 78 cpu - I wouldn't mind getting a higher end cpu in these thinkpads, but maybe it will just generate more heat on normal operation instead of lower ghz
<_`[m]> probably not right?
lollaritits[m] has joined #aarch64-laptops
<lollaritits[m]> <_`[m]> "still no configurable t14s huh..." <- it does have all of that?
<kalebris> _`[m]: well, I'm sticking with lenovo due to trackpoint + 5g modem, but I'm waiting on x13s g2 hopefully that will go fanless as well
<_`[m]> <lollaritits[m]> "it does have all of that?" <- ah yeah that second part is about yoga slim and macbooks
<lollaritits[m]> even tho i really like the size of the X13s
<lollaritits[m]> not sure if/when i will get a t14s
<_`[m]> <kalebris> "\: well, I'm sticking with..." <- do you know if that's on the road map then? my only issue with g1 was the heat with big external screen connected, so with cpu gpu upgrade maybe that'll be less and it's been the best laptop I've touched in a while really
<lollaritits[m]> heat with external monitors?
<_`[m]> lollaritits[m]: same , the fans are scary, though I have sent back a lenovo t14 before exactly for having too loud fans
<lollaritits[m]> im literally playing minecraft with the lid closed
<lollaritits[m]> with an overpowered TB4 Dock
<_`[m]> lollaritits[m]: it's 55 inch or something
<_`[m]> I used it dual screen with internal, had to switch back to the macbook air m1 which barely gives a noticeable heat increase for the same
<lollaritits[m]> i have a 32 inch one
<lollaritits[m]> are you powering the monitor of the laptop?
<lollaritits[m]> im going 50W in total when doing nothing special (including the monitor)
<kalebris> i don't know if it's on the roadmap, more like wishful thinking. based on the messages around x13s lenovo page "available soon" and other similar messages. and the fact that put a Gen1 next to it etc. they are kinda pointing towards a gen2 coming
<kalebris> Nios34[m]: i tried udevadm monitor but opening/closing didn't give me anything
Segfault[m]1 has joined #aarch64-laptops
<Segfault[m]1> HdkR: do you know if anything ended up happening wrt the convert_ubyte fallback on msm? i've run into it in firefox on a much slower 7c g2 tablet and it's making some websites pretty much unusably slow
<robclark> Segfault[m]1: quite a while back I added some missing format that some game wanted (CS:GO?).. unless you are using an ancient mesa you should have that.. but there are a lot of formats in gl, perhaps ffox is using some other non-natively-supported format. The interesting question is _what_ is that format.
<Segfault[m]1> <robclark> "Segfault: quite a while back I..." <- mesa 24.1.1
<_`[m]> <lollaritits[m]> "are you powering the monitor..." <- nah
<Segfault[m]1> it's in a flatpak so figuring out what formats are causing trouble might be a bit more difficult but i can have a look
matthias_bgg has joined #aarch64-laptops
matthias_bgg has quit []
kuter has joined #aarch64-laptops
<Segfault[m]1> <robclark> "Segfault: quite a while back I..." <- ```... (full message at <https://matrix.org/_matrix/media/v3/download/matrix.org/IeKKlHGKGNxKerKROPerMyyH>)
<robclark> Segfault[m]1: got backtrace?
<Segfault[m]1> i'll get it in a sec, gdb is being slow
<robclark> idk if ffox can be convinced to use gles? That would probably avoid it doing silly thing
<Segfault[m]1> not afaict
<Segfault[m]1> <robclark> "idk if ffox can be convinced..." <- what silly thing is it doing?
<robclark> well, using some format that needs conversion... I'll have to switch back to 24.1 to decode the src/dst formats.. I'll do that later
<Segfault[m]1> the same blit transfer patch that worked for gnome on the x13s works here too
kuter has quit [Ping timeout: 480 seconds]
ungeskriptet is now known as Guest602
ungeskriptet has joined #aarch64-laptops
Guest602 has quit [Ping timeout: 480 seconds]
smpl has quit [Ping timeout: 480 seconds]
phire has quit [Read error: Connection reset by peer]
<lollaritits[m]> what exactly did i need for DRM again?
ungeskriptet is now known as Guest607
Guest607 has quit [Ping timeout: 480 seconds]
<Jasper[m]> widevine installer from asahi
ungeskriptet has joined #aarch64-laptops
kuter has joined #aarch64-laptops
kuter has quit [Ping timeout: 480 seconds]
<colemickens> strongtz: is it safe to assume your branch has stuff that's not upstream? are you planning to merge in the DTS that have been sent to lkml?
kuter has joined #aarch64-laptops
kuter has quit [Quit: Leaving]
jhovold has quit [Ping timeout: 480 seconds]
cachoeira has quit [Remote host closed the connection]
cachoeira has joined #aarch64-laptops
derzahl has quit [Ping timeout: 480 seconds]