- Describing on which device the buffer has been allocated on is not enough: on some setups the buffer may have been allocated on one device but may still be directly accessible without any move on another device. For instance, on a split render/display system, a buffer allocated on the display device can be directly rendered to from the render device.
Luc Ma lucmann
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| SRCS := $(wildcard *.json) | |
| OBJS := $(patsubst %.json,%.svg, $(SRCS)) | |
| all: $(OBJS) | |
| $(OBJS): %.svg: %.json | |
| npx bit-field --hspace 1800 --lanes $(shell echo $< | grep -o -E '[0-9]*') --vflip --hflip -i $< > $@ | |
| clean: | |
| rm -f $(OBJS) |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| fails=(); for i in `seq 1 8`; do fails+=("$i"); done; echo "${fails[@]}" |
- 默认输出是 stderr, 而不是 stdout
-o 1.log -ff每个进程生成单独的文件，后缀是 $PID
- Interact Methods (open/close, ioctls, mmap)
- DMABUF (V4L2 Streaming I/O)
- Image Formats
- v4l2_pix_format vs drm_format (V4L2_PIX_FMT_ in videodev2.h vs DRM_FORMAT_ in drm_fourcc.h)
- FourCC (Four Character Codes)
- ColorSpaces
- Depth Format (V4L2_PIX_FMT_Z16 vs DRM 没有 Depth Format)
- Popular Data Formats
- RGB565
- Platform-specific Device Support
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Node: /dev/dri/card0 | |
| ├───Driver: vkms (Virtual Kernel Mode Setting) version 1.0.0 (20180514) | |
| │ ├───DRM_CLIENT_CAP_STEREO_3D supported | |
| │ ├───DRM_CLIENT_CAP_UNIVERSAL_PLANES supported | |
| │ ├───DRM_CLIENT_CAP_ATOMIC supported | |
| │ ├───DRM_CLIENT_CAP_ASPECT_RATIO supported | |
| │ ├───DRM_CLIENT_CAP_WRITEBACK_CONNECTORS supported | |
| │ ├───DRM_CLIENT_CAP_CURSOR_PLANE_HOTSPOT not supported | |
| │ ├───DRM_CAP_DUMB_BUFFER = 1 | |
| │ ├───DRM_CAP_VBLANK_HIGH_CRTC = 1 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| /* | |
| * This file generated automatically from dri3.xml by c_client.py. | |
| * Edit at your peril. | |
| */ | |
| #ifdef HAVE_CONFIG_H | |
| #include "config.h" | |
| #endif | |
| #include <stdlib.h> | |
| #include <string.h> |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| dd if=/dev/zero of=/tmp/sock-ghost bs=1K seek=1 count=0 | |
| dd if=/dev/zero of=/tmp/sock-solid bs=1K count=1 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| AFAICT | As far as I can tell | 个人认为 | |
|---|---|---|---|
| AFAIK | As far as I know | 据我了解 | |
| AFAIU | As far as I understand | 按我理解 | |
| BTW | By the way | 顺便 | |
| FWIW | For what it's worth | 陈述见解或建议的谦逊说法，比如我觉得这是有用的信息，但是从听者的角度未必也是 | |
| FYI | For your information | 供您参考 | |
| HTH | Hope this helps | 希望奏效 | |
| IDK | I don't know | 我不知道 | |
| IIRC | If I recall correctly / If I remember correctly | 如果我没有记错 | |
| IMHO | In my humble opinion | 在下愚见 |