Summary: | One pixel column that belongs in one monitor shows up in the other instead | ||
---|---|---|---|
Product: | DRI | Reporter: | shankao <shankao> |
Component: | DRM/Radeon | Assignee: | Default DRI bug account <dri-devel> |
Status: | RESOLVED MOVED | QA Contact: | |
Severity: | minor | ||
Priority: | medium | CC: | grumpyrogue, hill-robert |
Version: | unspecified | ||
Hardware: | x86-64 (AMD64) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
shankao
2012-12-22 16:02:24 UTC
This is a limitation due to the way xrandr works. It uses a single surface for all enabled displays rather than one surface per display. The display hardware has alignment requirements that can cause this situation since we align the start address down. The per-crtc pixmaps work should fix the issue when it finally goes into the xserver. Ok thanks. Any idea when that's planned for? :) This is still an existing problem since a couple of years in my setup, so I'll try to move it a bit to get it solved: I wonder if there's any way on which this alignment could be off-by-one in the xrandr code for this specific case. Is there any way or place where I could have a look and try? Thanks. (In reply to comment #3) > This is still an existing problem since a couple of years in my setup, so > I'll try to move it a bit to get it solved: > > I wonder if there's any way on which this alignment could be off-by-one in > the xrandr code for this specific case. Is there any way or place where I > could have a look and try? It's a radeon display hardware alignment requirement. *** Bug 63900 has been marked as a duplicate of this bug. *** -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/315. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.