lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Message-ID: <CALxUCwJh3Ki7uSZtcOzHpkPpC8kOdWHoZThr4vRnAuL1D4dD3A@mail.gmail.com>
Date: Wed, 22 Oct 2025 11:38:14 -0700
From: Eersten Keer <eerstenk@...il.com>
To: linux-kernel@...r.kernel.org
Subject: goodix touchscreen drivers compilation fails

Hello, im trying to compile various goodix.c drivers i found in
several places all fail after i set path to include, making me think
these drivers are too unmaintained for newer versions of ubuntu. i
even tried installing ubuntu 13 to compile. this touch panel is in a
tablet from munbyn irt05 or irt08

ive tried this one which doesnt have dependency on old gcc & kernel
goodix.c - drivers/input/touchscreen/goodix.c - Linux source code
v6.17 - Bootlin Elixir Cross Referencer
this fails with
/usr/src/linux-headers-6.11.0-21-generic/include/linux/atomic/atomic-arch-fallback.h:2581:25:
error: unknown type name atomic64_t’
 2581 | raw_atomic64_read(const atomic64_t *v)
      |                         ^~~~~~~~~~
its a looooooooong readout, before i paste that in here just checking
the best spot to get this driver

most common driver i get pointed to in searches is this one
Nicola Landro / Goodix Touchscreen Linux Driver · GitLab
this requires ubuntu 13, simply installing an older version of gcc
compiler didnt work for me.
after diving into the trash for an old pc that would even look at
ubuntu 13, it couldnt find the path so i tried compiling with
gcc -I/usr/src/linux-headers-3.8.0-19-generic/include goodix.c -o goodix
and then i couldnt find asm so i did this ln -s ./asm-generic ./asm
within the include folders

any clue how i can compile this? it seems im solving many dependencies
after another... there are emails circulating on this of ppl having
compiled this in the past. within the last year.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ