intel_gpu

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
intel_gpu [2012/06/17 02:44] – Add comment about WITH_KMS option needed by libdrm EdMasteintel_gpu [2013/03/27 18:15] (current) – Remove no-longer-relevant items, now that this is in HEAD EdMaste
Line 1: Line 1:
-All enabling patches were committed to HEAD as of r235859 and to RELENG_9 as of r236969.+NOTE: All enabling patches were committed to HEAD as of r235859 and to RELENG_9 as of r236969.
  
 **What is this ?** The required kernel-mode support to run the recent usermode ddx and mesa drivers for Intel GPUs. Initial goal is to have gen4-gen6 **What is this ?** The required kernel-mode support to run the recent usermode ddx and mesa drivers for Intel GPUs. Initial goal is to have gen4-gen6
Line 26: Line 26:
 Obviously, you need to have textproc/flex and devel/bison installed, flex from the base would not work. Obviously, you need to have textproc/flex and devel/bison installed, flex from the base would not work.
  
-The driver is loaded by the ''%%kldload i915kms%%'' command. ddx driver in the tree auto-loads 'i915.ko', which is old (DRI1). Since the syscons +Since the syscons is not integrated with KMS, screen goes blank after i915kms is loaded. 
-is not integrated with KMS, screen goes blank after i915kms is loaded. Use the command sequence ''%%sudo kldload i915kms && startx%%'' to start X +Use ''%%startx%%'' to let ddx driver load the right kernel module. 
-session from VT console. Set ''%%sysctl hw.dri.debug=0%%'' to reduce verbosity of the driver at runtime.+Set ''%%sysctl hw.dri.debug=0%%'' to reduce verbosity of the driver at runtime.
  
 You must have the serial console to catch debugging output and panics. You must have the serial console to catch debugging output and panics.
Line 51: Line 51:
  
 ==== FAQ (yes, I already tired of some questions) ==== ==== FAQ (yes, I already tired of some questions) ====
- 
-  - I have the problem .... 
- 
-**Do not mail me in private. Use mailing lists, x11@ is probably right one.** 
  
   - Do you plan to port TTM ?   - Do you plan to port TTM ?
  
-Not in the scope of this project. After the project is finished, I might look at TTM and execution managers for non-Intel cards, +Not in the scope of this project, but see [[AMD_GPU]]
-in particular, ATI/AMD. +
-Apparently, KMS bits are not much interesting to me. +
- +
-  - I want to test ! +
- +
-Great. Why do you think that I need to know about it ? +
-Bug fixes and reviews are welcome.+
  
   - Does KMS work will ease the future porting of the KMS code for non-Intel drivers ?   - Does KMS work will ease the future porting of the KMS code for non-Intel drivers ?
  • intel_gpu.1339901077.txt.gz
  • Last modified: 2012/06/17 02:44
  • by EdMaste