-
Notifications
You must be signed in to change notification settings - Fork 181
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Primary render fallback #1680
base: master
Are you sure you want to change the base?
Primary render fallback #1680
Conversation
d2f7e1f
to
4b808ab
Compare
427b2ce
to
05ee0b7
Compare
05ee0b7
to
57aacfc
Compare
57aacfc
to
16c1a0e
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #1680 +/- ##
==========================================
+ Coverage 17.10% 19.14% +2.04%
==========================================
Files 174 174
Lines 28748 28767 +19
==========================================
+ Hits 4916 5508 +592
+ Misses 23832 23259 -573
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
#[cfg(feature = "backend_drm")] | ||
pub fn from_bo(bo: BufferObject<()>, implicit: bool) -> Self { | ||
let drm_node = DrmNode::from_file(bo.device_fd()).ok(); | ||
Self::from_bo_with_node(bo, implicit, drm_node) | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I do not like all those conditional compilation around backend_drm
here. Do we really want to do this or should we just enable backend_drm
for backend_gbm
implicitely?
This adds support for display only nodes by falling back to the primary gpu for rendering.
In addition to the render fallback it also tries to import foreign gbm buffers through dmabuf export/import.
Unfortunately it seems the DisplayLink driver has some issues regarding vsync and will issue a vblank right after
scheduling a page flip. This leads to visual tearing, probably caused by the user-space driver part. As a mitigation this PR also adds a way to throttle vblanks.