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
<Jasper[m]> In addition to issues with wifi disconnecting after sleep, it's also having trouble going to sleep
<Jasper[m]> on 6.8.0-rc5
<steev> what, if anything, do you have plugged in to the usb?
<Jasper[m]> Nothing, at least at the end there
<Jasper[m]> It was charging, but not sure if that counts
KREYREN_ has quit []
KREYREN_oftc has joined #aarch64-laptops
<steev> shouldn't, no
xnox1 has quit []
xnox has joined #aarch64-laptops
sally[m]1234 has joined #aarch64-laptops
hexdump01 has joined #aarch64-laptops
hexdump0815 has quit [Ping timeout: 480 seconds]
paddymahoney has joined #aarch64-laptops
jglathe_volterra has joined #aarch64-laptops
Kelsar has quit [Quit: http://quassel-irc.org - Chat comfortably. Anywhere.]
Kelsar has joined #aarch64-laptops
jglathe_volterra has quit [Remote host closed the connection]
<jglathe__> once you do it right, it suddenly works
nick1343[m] has joined #aarch64-laptops
f_ is now known as funderscore
funderscore is now known as f_
pundir_ is now known as pundir
KREYREN_oftc has quit [Remote host closed the connection]
KREYREN_oftc has joined #aarch64-laptops
craftyguy has quit [Remote host closed the connection]
craftyguy has joined #aarch64-laptops
craftyguy has quit [Remote host closed the connection]
Erisa has quit [Read error: No route to host]
craftyguy has joined #aarch64-laptops
Erisa has joined #aarch64-laptops
Vectorboost has joined #aarch64-laptops
Vectorboost has quit [Remote host closed the connection]
Vectorboost has joined #aarch64-laptops
Vectorboost has quit [Ping timeout: 480 seconds]
<steev> what is it?
<jglathe__> my bootable image for Volterra... took me a few days to debug this for a new release
<jglathe__> can be made to also boot to X13s, and (hopefully) Surface Pro 9 5G
f_ is now known as funderscore
<steev> ah
funderscore is now known as f_
<jglathe__> systemd and snap black magic
<Jasper[m]> Currently trying to figure out getting hid over i2c to work on the samsung. Anyone have an idea how I can decipher the interrupt pin for that from the ACPI table I have?
<Jasper[m]> I tried working backwards on an existing example (specifically the aspire 1), but I can't find the interrupt pin there either
<Jasper[m]> I guess I'm kind of spoiled with the downstream kernel sources since they are infinitely more readable than the ACPI tables for this device. Especially unfun if you have no schematics
Vectorboost has joined #aarch64-laptops
Vectorboost has quit [Remote host closed the connection]
<jglathe__> would i2c generate interrupts if hid is triggered? Or would it just not get through
<Jasper[m]> They tend to be routed over different pins, I know that
<jglathe__> hmm show spurious interrupts?
<jglathe__> do you have an acpi name for the device?
<Jasper[m]> jglathe__: Not sure what you mean by that
<Jasper[m]> jglathe__: For the keyboard?
<Jasper[m]> eckb should get you to it
<Jasper[m]> <jglathe__> "sounds too easy, but: https://..." <- Well yeah, but how would you read the pin from that
<Jasper[m]> I'm guessing you can find something like a definition for SB.GIO0 or something
<Jasper[m]> but a quick ctrl-f returns me nothing
<jglathe__> Experience with arm-smmuv3 interrupts last week with was that this is the interrupt pin
<jglathe__> travmurav explained that they are hard wired on chip
<jglathe__> DSDT.dsl
KREYREN_oftc has quit [Remote host closed the connection]
KREYREN_oftc has joined #aarch64-laptops
echanude has quit [Quit: WeeChat 4.2.1]
echanude has joined #aarch64-laptops
echanude has quit [Ping timeout: 480 seconds]
hexdump01 has quit []
hexdump0815 has joined #aarch64-laptops
<hexdump0815> Jasper[m]: maybe compare the dsdt.dsl for certain devices to the one from the galaxy book go - if there are similarities, maybe you can take some things from https://github.com/hexdump0815/linux-mainline-qcom-kernel/blob/main/misc.qc7/misc/sc7180-samsung-galaxy-book-go.draft
<hexdump0815> the galaxy book go acpi tables are also there on the same repo you uploaded yours to, either directly or in a pr
<hexdump0815> sadly the keyboard is also not working properly (but mostly) as the right interrupt for it has not been found yet
<hexdump0815> there was also someone who already started working on a galaxy book 2 dts i think, but afair they di not really get very far so far - i can look that one up for you tomorrow
<Jasper[m]> Will check it all out! Though do realise there's a difference between the book2 and the book2 go
bluerise_ has joined #aarch64-laptops
bluerise has quit [Ping timeout: 480 seconds]