mirror of
https://github.com/genodelabs/genode.git
synced 2025-01-19 03:06:39 +00:00
90e151e2c4
This call allows for checking if the given execution buffer has been completed and complements the completion signal. Initially the GPU multiplexer always sent such a signal when the currently scheduled execution buffer has been completed. During enablement of the 'iris' driver it became necessary to properly check of sequence number. In case of the Intel GPU multiplexer the sequence numbers are continous, which prompted the greater-than-or-equal check in the DRM back end. By hidding this implementation detail behind the interface, GPU drivers are free to deal with sequence numbers any way they like and allows for polling in the client, where the completion signal is now more of a progress signal. Issue #4265. |
||
|---|---|---|
| .. | ||
| doc | ||
| include | ||
| lib | ||
| ports | ||
| recipes | ||
| run | ||
| src | ||
| README | ||
This directory contains ports of popular 3rd-party software to Genode. Usage ----- The tool './tool/ports/prepare_port' in the toplevel directory automates the task of downloading and preparing the library source codes. You can select individual packages that have to be prepared by specifying their base names (without the version number) as command-line argument. For example, the following command prepares both the C library and the Freetype library: ! ./tool/ports/prepare_port libc freetype To compile and link against 3rd-party libraries of the 'libports' repository, you have to include the repository into the build process by appending it to the 'REPOSITORIES' declaration of your '<build-dir>/etc/build.conf' file. Under the hood -------------- For each library, there is a file contained in the 'libports/ports/' subdirectory. The file is named after the library and contains the library-specific rules for downloading the source code and installing header files. How does 'libports' relate to the other repositories? ----------------------------------------------------- Most libraries hosted in the 'libports' repository expect a complete C library, which is provided with the 'libc' package. Please do not forget to prepare the libc package when using any of the other libports packages. The libc, in turn, depends on the 'os' repository for its back end. Because the 'os' repository is the home of the dynamic linker, libraries contained in 'libports' are safe to assume the presence of the dynamic linker and, thus, should be built as shared libraries.