Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756592AbaF3MuJ (ORCPT ); Mon, 30 Jun 2014 08:50:09 -0400 Received: from mail-ve0-f175.google.com ([209.85.128.175]:33908 "EHLO mail-ve0-f175.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755407AbaF3MuD (ORCPT ); Mon, 30 Jun 2014 08:50:03 -0400 MIME-Version: 1.0 In-Reply-To: <53B15A94.3010402@vmware.com> References: <1395967502-71219-1-git-send-email-chrisfriedt@gmail.com> <533A8E52.5050304@vmware.com> <53B14E9E.3040505@vmware.com> <53B15A94.3010402@vmware.com> From: Christopher Friedt Date: Mon, 30 Jun 2014 08:49:40 -0400 Message-ID: Subject: Re: [PATCH 1/1] drm/vmwgfx: correct fb_fix_screeninfo.line_length To: Thomas Hellstrom Cc: dri-devel , linux-kernel@vger.kernel.org, Dave Airlie , linux-graphics-maintainer@vmware.com Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Jun 30, 2014 at 8:39 AM, Thomas Hellstrom wrote: > xf86-video-vmware in kms mode uses the kernel driver to set these registers. > FWIW, the modesetting part of the kernel driver uses SVGA_REG_PITCHLOCK > instead of > SVGA_REG_BYTES_PER_LINE to set the pitch. That's probably where the > clash happens. That sounds a bit more accurate. Should kms and fbdev be setting both registers then? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/