From: Thomas Hellstrom Subject: [PATCH 0/4] Urgent vmwgfx fixes. Date: Fri, 1 Oct 2010 10:21:47 +0200 Message-ID: <1285921312-10159-1-git-send-email-thellstrom@vmware.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from smtp-outbound-1.vmware.com (smtp-outbound-1.vmware.com [65.115.85.69]) by gabe.freedesktop.org (Postfix) with ESMTP id C37949E7B8 for ; Fri, 1 Oct 2010 01:21:41 -0700 (PDT) List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org Errors-To: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org To: airlied@redhat.com Cc: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org These are fixes that should, if at all possible, make it into 2.6.36. They are extracted from the previous patch series, "vmwgfx updates". I will respin the rest of the patches for possible inclusion into drm-next. I've renamed some patches and added some comment to emphasise the fixes in them rather than what's actually being done with the code. Patch 1 fixes vt switching while 3D objects are active. Previously the device lost all state at that point. Patch 2 enables the vblank system and avoids a lot of uninitialized calls (kernel crashes) Patch 3 removes a workaround for dev::devname the current code caused a kernel crash at module unload then dev::devname was beeing kfreed when it was actually static. Patch 4 Fixes a bo pinning error causing severe rendering corruption. Thanks, Thomas