PowerVR userspace: GLES on fbdev, then buffer sharing with sun4i-drm #60
Labels
No labels
blocked-physical
cleanup
hardware
infra
kernel
P1-critical
P2-high
P3-normal
P4-later
reliability
security
upstream
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
tiagoagueda/a80#60
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Part of #55, and the last phase. Assumes the firmware boots.
Window system, in order of preference
sun4i-drmalready provides/dev/fb0through fbdev emulation. Goal: one GLES triangle, no compositor.libpvr_dri_if.so,which implies this path.
The part that will cost time
PVR services allocate GPU memory; scanout belongs to
sun4i-drm. That needs dma-buf export fromPVR and import into the display driver. DDK 1.x has dma-buf support, but this is the most likely
place to lose days. If it resists, fall back to an fbdev blit - correctness before speed.
Done when
An
es2gears-class test renders on the TV.The userspace this uses depends entirely on how #56 resolves: DDK 1.4 glibc
(native Debian) or DDK 1.3 Android via libhybris.