forked from illumos/gfx-drm
-
Notifications
You must be signed in to change notification settings - Fork 0
hoewweken/gfx-drm
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Folders and files
Name | Name | Last commit message | Last commit date | |
---|---|---|---|---|
Repository files navigation
This is the "graphics/DRM" gate, in which we build the DRM kernel modules and related DRM libraries. Introduction: DRM stands for Direct Rendering Manager, which is a collection of kernel modules and libraries that allow programs like the Xorg server to operate hardware-accelerated graphics cards. This software currently supports Intel (R) integrated graphics devices with hardware acceleration, video memory management, Graphics Execution Manager (GEM), and kernel modesetting (KMS). How to build: Clone this repo. onto an OpenIndiana or similar build system with the "build-essential" packages installed, then: cd (top of clone) make install make package Overview: The major kernel components are: usr/src/uts/intel/io/i915 i915 driver usr/src/uts/common/io/drm/ DRM "misc" support usr/src/uts/intel/io/agpmaster AGP master support usr/src/uts/intel/io/agpgart AGP GART, AGP target Dependendencies: i915 -> drm drm -> agpmaster, gfx_private The user-level libraries are: usr/src/lib/libdrm/ DRM driver usr/src/lib/libdrm_* H/W-specific DRM support usr/src/lib/libkms Kernel Mode Setting support Note that the source for those libraries is EXTERNAL, and NOT checked into this gate. At build time, the library sources are downloaded from: http://dri.freedesktop.org/libdrm/ and then unpacked and patched under: usr/src/common/libdrm/ That makes this gate a little unusual, sort of a "hybrid" between how illumos-gate does things and how the "userland" gate does things. There are good reasons for this. The kernel code is very much operaging-system-specific, and therefore can not simply track some "upstream" like the user-level library code can. It's also a little tricky to build kernel code "correctly", which is why the kernel build parts of this gate are based on the "ON skeleton" gate: https://github.com/gwr/on-skel The user-level libraries here are built with minimal changes relatative to the upstream, and therefore can use a strategy similar to that in the "userland" gate: https://github.com/OpenIndiana/oi-userland Development and testing: If you find you need to make changes to library code (such as when updating to a new version) the easiest way is to save a copy of the unpacked library source before patching (use "make unpack"), then go ahead and edit files as needed, and once you're happy with the changes use "diff -u saved-lib edited-lib" to update the files in the patches directory. Use: usr/src/common/libdrm/Check-patches to check that your patches are in sync with edits. When doing incremental work in the gate, i.e. fixing compilation errors, it's handy to run an editor in a "bldenv" environment, as follows: ksh93 tools/bldenv -d myenv.sh That gets you a new shell, in which you can run an emacs if you like "meta-x compile", or whatever. Just cd to where the top-level make had problems and run make. Then fix bugs, open pull requests. Please run the tests before submitting pull requests. They're installed as /opt/drm-test/*
About
No description, website, or topics provided.
Resources
Stars
Watchers
Forks
Packages 0
No packages published
Languages
- C 94.4%
- Makefile 3.3%
- Roff 0.8%
- DIGITAL Command Language 0.8%
- Batchfile 0.3%
- Shell 0.2%
- Other 0.2%