“Linux Display study”的版本间的差异

来自个人维基
跳转至: 导航搜索
第30行: 第30行:
  
 
Types of operation:
 
Types of operation:
# 有序列表项
+
# Memory allocation and freeing
Memory allocation and freeing
+
# Command execution
Command execution
+
# Aperture management at command execution time
Aperture management at command execution time
+
  
 
https://blog.csdn.net/yangkuanqaz85988/article/details/48689521
 
https://blog.csdn.net/yangkuanqaz85988/article/details/48689521
 
DRM
 
DRM
 
[[image:DRM.png]]
 
[[image:DRM.png]]

2019年11月1日 (五) 12:04的版本

Linux DRM Developer's Guide


The Direct Rendering Manager (DRM) is a subsystem of the Linux kernel responsible for
interfacing with GPUs of modern video cards. DRM exposes an API that user space programs
can use to send commands and data to the GPU, and perform operations such as configuring
the mode setting of the display. DRM was first developed as the kernel space component of
the X Server's Direct Rendering Infrastructure, but since then it has been used by other
graphic stack alternatives such as Wayland.

Ap -> [DRM API] -> libDrm -> [ioctls ]-> DRM driver
libDrm:

vblank event handling, 
memory management,
output management,
framebuffer management,
command submission & fencing,
suspend/resume support,
DMA services. 

DRM driver:
drm_driver structure

u32 driver_features; //use AGP,use GEM mem manager, support KMS interfaces, DRM prime buffer sharing, 
int (*load) (struct drm_device *, unsigned long flags); //driver and device initialization entry point.

Memory management
DRM currently contains two memory managers, the Translation Table Manager (TTM) and the Graphics Execution Manager (GEM).

GEM exposes a set of standard memory-related operations to userspace and a set of helper functions to drivers, and let drivers implement hardware-specific operations with their own private API.

Types of operation:

  1. Memory allocation and freeing
  2. Command execution
  3. Aperture management at command execution time

https://blog.csdn.net/yangkuanqaz85988/article/details/48689521
DRM
DRM.png