commit | 5180a5cae9543194c95b23616bec97134f634bd4 | [log] [tgz] |
---|---|---|
author | Nico Huber <nico.h@gmx.de> | Sat Jul 15 18:39:01 2023 |
committer | Chromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Aug 02 02:47:34 2023 |
tree | de36a956747594514693a06c90bf5339a6c24160 | |
parent | a091694ff8cf49c6d387d2d3a7909f59a0c0259b [diff] |
Avoid warning '"Pos32" is already use-visible' Ensures compatibility with GCC 13. (cherry picked from commit a4be8a21b0e2c752da0042c79aae5942418f53e2) Original-Change-Id: Ic41a20167b88b5952642cc59e80315c5d2fd98b0 Original-Signed-off-by: Nico Huber <nico.h@gmx.de> Original-Reviewed-on: https://review.coreboot.org/c/libgfxinit/+/76491 Original-Reviewed-by: Paul Menzel <paulepanter@mailbox.org> Original-Reviewed-by: Elyes Haouas <ehaouas@noos.fr> GitOrigin-RevId: a4be8a21b0e2c752da0042c79aae5942418f53e2 Change-Id: I7290ecaa1645e0dab1b62b908f57648af762c671 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/coreboot/libgfxinit/+/4738171 Reviewed-by: Kangheui Won <khwon@chromium.org> Commit-Queue: Kangheui Won <khwon@chromium.org> Tested-by: ChromeOS Prod (Robot) <chromeos-ci-prod@chromeos-bot.iam.gserviceaccount.com>
libgfxinit is a graphics initialization (aka modesetting) library for embedded environments. It currently supports only Intel hardware, more specifically the Intel Core processor line.
It can query and set up most kinds of displays based on their EDID information. You can, however, also specify particular mode lines.
libgfxinit is written in SPARK, an Ada subset with formal verification aspects. Absence of runtime errors can be proved automatically with SPARK GPL 2016.
For compilation, the GNAT Ada compiler is required. Usual package names in Linux distributions are gcc-ada
and gnat
.
You'll need libhwbase and libgfxinit. Best is to clone the repositories into a common parent directory (this way libgfxinit will know where to find libhwbase).
$ mkdir gfxfun && cd gfxfun $ git clone https://review.coreboot.org/p/libhwbase.git $ git clone https://review.coreboot.org/p/libgfxinit.git
Both libraries are currently configured by hand-written config files. You can either write your own .config
, link one of the shipped files in configs/
, e.g.:
$ ln -s configs/linux libhwbase/.config
or overwrite the config filename by specifying cnf=<configfile>
on the make command line.
By default most debug messages won't be compiled into the binary. To include them into the build, set DEBUG=1
on the command line or in your .config
.
Let‘s install libhwbase. We’ll need configs/linux
to build regular Linux executables:
$ cd libhwbase $ make DEBUG=1 cnf=configs/linux install
By default this installs into a new subdirectory dest
. You can however overwrite this decision by specifying DESTDIR=
.
gfx_test
libgfxinit is configured and installed in the same manner as described above. You will have to select a configuration matching your hardware.
The makefile knows an additional target gfx_test
to build a small Linux test application:
$ cd ../libgfxinit $ make DEBUG=1 cnf=configs/sandybridge gfx_test
The resulting binary is build/gfx_test
.
gfx_test
sets up its own framebuffer in the stolen memory. It backs any current framebuffer mapping and contents up first and restores it before exiting. This works somehow even while the i915 driver is running. A wrapper script gfxtest/gfx_test.sh
is provided to help with the setup. It switches to a text console first and tries to unload the i915 driver. But ignores failures to do so (it won't work if you still have any application running that uses the gfx driver, e.g. an X server).
# gfxtest/gfx_test.sh
If you chose the right config above, you should be presented with a nice test image. But please be prepared that your console might be stuck in that state afterwards. You can try to run it with i915 deactivated then (e.g. when booting with nomodeset
in the kernel command line or with i915 blacklisted) and loading it afterwards.