Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752315AbaF3NS5 (ORCPT ); Mon, 30 Jun 2014 09:18:57 -0400 Received: from mail-ve0-f181.google.com ([209.85.128.181]:59265 "EHLO mail-ve0-f181.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750831AbaF3NS4 (ORCPT ); Mon, 30 Jun 2014 09:18:56 -0400 MIME-Version: 1.0 In-Reply-To: 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 09:18:35 -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:49 AM, Christopher Friedt 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. -- 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/