05:04 <travmurav[m]> I wonder if one could write a little gpiod program that would subscribe to all interrupts on all gpio lines, then filter the ones that fire rapidly to only find these, fired by the user action (touched tp or pressed kb)

05:07 <travmurav[m]> hexdump0815: in fact there are some examples on the net that track single hardcoded line so maybe if you feel adventurous, can try to go through all of the gpios manually xD

05:07 <travmurav[m]> this is more of a "brute force" approach of course

05:37 <amstan> travmurav: you can subscribe to pin interrupts via gpiod? TIL

05:37 <amstan> does that do a select or something?

05:38 <travmurav[m]> well a quick search suggests that it can do an event on the interrupt at least

05:39 <travmurav[m]> https://github.com/starnight/libgpiod-example/blob/master/libgpiod-event/main.c

05:41 <travmurav[m]> ah apparently gpiomon can be set to monitor these even

13:49 <_`[m]1> hello all

13:50 <_`[m]1> who's running x13s?

14:18 <clover[m]> Me

14:24 <_`[m]1> did you manage to install linux yet?

14:25 <_`[m]1> I've been at it for a while now

14:26 <_`[m]1> > #5 56.91 E: Package 'gcc-aarch64-linux-gnu' has no installation candidate

14:56 <gachikuk1> Hello guys has anyone tried writing assembly targeting x86, on aarch64?

15:00 <_`[m]1> or I get /boot/laptop.dtb not fou d

15:00 <_`[m]1> s/fou d/found/

15:09 <HdkR> gachikuk1: Yes

15:10 <gachikuk1> HdkR: could you tell me what you did please? I've been banging my head on it for the past 2 days already

15:11 <HdkR> Install gcc-x86-64-linux-gnu and g++-x86-64-linux-gnu and then use the installed `x86_64-linux-gnu-g++` binary to compile, which should include a linker for you. Alternatively install clang and lld and that supports cross-compiling if you pass in the target triple correctly.

15:13 <HdkR> `clang++ -target x86_64-linux-gnu -fuse-ld=lld -O2 a.cpp` or `x86_64-linux-gnu-g++ -O2 a.cpp`

15:14 <HdkR> Package managers tend to include libc and libstdc++ for other architectures to make cross-compiling easier

15:15 <_`[m]1> but it's trying to run in a container to build a custom image

15:15 <_`[m]1> I'm running on mac

15:16 <gachikuk1> HdkR thank you so so much, I had no idea, I tried using *nasm* and *ld* with no luck. I'll give your solution a try later on _`[m]1: I'm on mac as well running asahi.

15:20 <HdkR> Not sure if ALARM offers other architecture library files due to lack of multiarch support. Might need an additional x86 sysroot

15:28 <_`[m]1> yeah lol but with the docker container way, it shouldn't need me installing anything locally?

15:29 <_`[m]1> I don't understand why the package is unavailable

17:23 <steev> because it's native when on arm64 already?

17:23 <steev> you don't install gcc-x86_64-linux-gnu when on an intel system, you just install gcc

17:50 <init> fun factoid of the day. I sent my missing-keys-too-often X13s under warranty. Lenovo took it back, and tried to repair it, then i got a message stating that parts were ordered, then i got a mail saying that my warranty was extended due to the delay it would take to repair it.

17:50 <init> getting some arm love.

17:57 <steev> nice

18:51 <HdkR> Oop, accidentally ordered two Honeycomb LX2K boards instead of one. Dang flakey order page

19:12 <steev> oops

20:03 <_`[m]1> damn well played lenovo

20:55 <leezu> https://lore.kernel.org/lkml/20230207102254.1446461-1-javierm@redhat.com/ revert didn't make it to v6.2.y, breaking suspend on sc7180 sc7280.

20:56 <leezu> I sent a response to the thread, hopefully the revert can be included for 6.2.10

23:25 <_`[m]1> installing arch finality

23:25 <_`[m]1> you can't yolo install latest kernel?

23:26 <_`[m]1> I think I've managed to set up crypysetup with lvm

23:35 <steev> you can, but not everything is in the latest kernel

23:36 <steev> pretty sure clover[m] has all the arch stuff for the x13s somewhere

23:42 <_`[m]1> I found this repo

23:42 <_`[m]1> https://github.com/ironrobin/archiso-x13s

23:42 <_`[m]1> or rather it mentions a repo

23:42 <steev> yeah, that's clover[m]