Using the new driver build actions in X11Libre/actions-build-driver repo,
instead of having lots of duplicated pipeline and script in all the
individual driver repos.
Signed-off-by: Enrico Weigelt, metux IT consult <info@metux.net>
The Xserver's PCI handling as long moved to libpciaccess decades ago.
Cleanup up those code pathes which were only meant for really ancient
xserver versions that we really don't support anymore.
Signed-off-by: Enrico Weigelt, metux IT consult <info@metux.net>
The module directory has changed to a per ABI folder in the xlibre-xserver.
Now the default value of `xorg-module-dir` will be detected from the `moduledir` variable in xorg-server.pc.
Signed-off-by: b-aaz <b-aazbsd.proton.me>
This pipeline builds the driver against the latest Xserver stable
release as well as current master.
Signed-off-by: Enrico Weigelt, metux IT consult <info@metux.net>
Add the following forms for issue creation:
* Bug report
* Feature request
* Code change
* Documentation update
* Organizational task
* add issue type selection page on "New Issue" call
* mention Github Discussions and the mailing list where appropriate
Part-of: X11Libre/misc#156
Signed-off-by: callmetango <callmetango@users.noreply.github.com>
Adding a gitlab pipeline building this driver against Xserver major releases
since 1.18, including current master branch, on Debian as well as FreeBSD.
Signed-off-by: Enrico Weigelt, metux IT consult <info@metux.net>
Adding a bunch of common scripts for building xorg drivers on different
platforms (for now Debian and FreeBSD) against different server versions.
Also designed to be executed locally (eg. within a VM), so one doesn't
always have to employ f.d.o gitlab.
For now, these are synced manually across various driver repos, until we've
found a viable solution for a central place.
Signed-off-by: Enrico Weigelt, metux IT consult <info@metux.net>
This release is the result of an extensive code cleanup by
Connor Behan and Enrico Weigelt. Most noticable changes:
* The supported Xserver version is bumped to 1.18.x minimum.
* The GX component no longer supports XAA. Only EXA remains.
* The LX component now uses the default Xserver pixel depth.
VALIDATION PLATFORMS
* Debian (Xserver 1.18.4) on ARTEC DBE61 (Geode LX700).
* Debian (Xserver 1.18.4) on FIC ION603A (Geode LX800).
* Debian (Xserver 21.1.7) on FIC ION603A (Geode LX800).
Signed-off-by: Martin-Éric Racine <martin-eric.racine@iki.fi>
A few other variables are unused but they are setting using register
reads so I am afraid to touch them.
Signed-off-by: Connor Behan <connor.behan@gmail.com>
On 64bit the long int type is 64 bit, but the MSR operations still
are 32bit, thus we need to use uint32_t. Also need slighty modified
versions of the inline asm code, since on 64bit machines, the 32bit
(pseudo-)registers can't be used on push/pop.
This patch is mostly for CI purpose, since there isn't any known version
of this graphics device on a 64 bit machine.
Signed-off-by: Enrico Weigelt, metux IT consult <info@metux.net>
In addition to removing some more dead code, this warns the user that
OSMImageBuffers now does nothing. The similar option OSMColorExpBuffers
is still used by EXA so there is no warning for this.
Signed-off-by: Connor Behan <connor.behan@gmail.com>
One of the checks for HAVE_GX appeared to be in the wrong place. Once it
is in the right place, a configure option can be used to not set HAVE_GX
and avoid compiling the associated files.
Signed-off-by: Connor Behan <connor.behan@gmail.com>
When the minimum Xserver version was recently bumped to 1.18, the
ability to enable XAA was removed accordingly. But plenty of XAA hooks
were left in. Removing these will lighten the code and get rid of some
more compiler warnings.
Signed-off-by: Connor Behan <connor.behan@gmail.com>
Long ago, xf86_reload_cursors() was turned into a noop. And we were not
using anything specific from xf86PciInfo.h.
Signed-off-by: Connor Behan <connor.behan@gmail.com>
This applies some obvious changes to stop gcc from complaining about
dead code, shadow declarations, differing signedness and sections that
mix declarations with code.
The warning about discarding const qualifiers is more annoying because
we pass string literals to some functions which accept non-const
pointers. Currently, this takes the following approach. If the function
*needs* to accept non-const pointers, cast the string literal as char *.
Otherwise, change the function to only accept a const pointer. To
anticipate future use cases though, I could also leave function
definitions as they are and just always cast string literals.
Alternatively, if this is more trouble that it is worth, we could just
put up with the warnings.
Signed-off-by: Connor Behan <connor.behan@gmail.com>
