Messages in this thread | | | Date | Mon, 30 Jun 2014 15:22:26 +0200 | From | Thomas Hellstrom <> | Subject | Re: [PATCH 1/1] drm/vmwgfx: correct fb_fix_screeninfo.line_length |
| |
On 06/30/2014 03:18 PM, Christopher Friedt wrote: > On Mon, Jun 30, 2014 at 8:49 AM, Christopher Friedt > <chrisfriedt@gmail.com> wrote: >> That sounds a bit more accurate. Should kms and fbdev be setting both >> registers then? > I wonder if fbdev can use PITCHLOCK as well, rather than > BYTES_PER_LINE. I will only be able to run both kms and fbdev > functional tests about 9 hours from now, so any discussion until then > is welcome
Please see the previous message I sent. If you just remove the line that sets BYTES_PER_LINE, fbdev will have called into the kms code to set PITCHLOCK correctly.
/Thomas
| |