Commit 90a04c2d authored by Vincent Wei's avatar Vincent Wei

tune words

parent 5eac88e0
......@@ -32,6 +32,8 @@ We call these documents "MiniGUI Supplementary Documents".
* [Release Notes for MiniGUI 5.0](Release-Notes-for-MiniGUI-5.0.md) -
Enhancements and changes of MiniGUI 5.0.x.
* [Write DRM Engine Driver for Your GPU](Writing-DRM-Engine-Driver-for-Your-GPU.md) -
Write a DRM engine driver to exploit the hardware accelerating functions of your GPU.
* [Using Compositing Schema](Using-Compositing-Schema.md) -
How to use compositing schema, and write a customized compositor.
* [Using Main Window Levels](Using-Main-Window-Levels.md) -
......
......@@ -379,7 +379,7 @@ chard in `mg-tests/drm-engine/`. Please refer to `mg-tests` repository:
## DRM Drivers for HybridOS
[HybridOS](https://hybridos.fmsoft.cn) uses MiniGUI as the
underlying windowing system. So the HybridOS project maintains the
underlying windowing system. The HybridOS project maintains the
DRM drivers for MiniGUI in the following repo (`hiDRMDrivers`):
<https://github.com/FMSoftCN/hidrmdrivers>
......@@ -401,8 +401,8 @@ the MiniGUI-Processes runtime mode. However, you need to pay attention
for the following matter:
The server (`mginit`) needs the root privilege to call `drmSetMaster` to act
as the master process of Linux DRI. Only after the client was authenticated
through the server (`mginit`), the client can get the rights to allocate buffer
as the master process of Linux DRI. Only after a client was authenticated
through the server (`mginit`), the client can get the rights to allocate buffers
from the GPU. Otherwise, the client processes will failed to initialize the
hardware accelerated DRM engine driver.
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment