Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754895AbbK0Pki (ORCPT ); Fri, 27 Nov 2015 10:40:38 -0500 Received: from mail-io0-f175.google.com ([209.85.223.175]:34278 "EHLO mail-io0-f175.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754250AbbK0Pkd (ORCPT ); Fri, 27 Nov 2015 10:40:33 -0500 MIME-Version: 1.0 In-Reply-To: <1448637005-3847-2-git-send-email-daniel.vetter@ffwll.ch> References: <1448637005-3847-1-git-send-email-daniel.vetter@ffwll.ch> <1448637005-3847-2-git-send-email-daniel.vetter@ffwll.ch> Date: Fri, 27 Nov 2015 15:40:32 +0000 Message-ID: Subject: Re: [PATCH RESEND 2/2] drm/i915: prevent the vgacon from ever reloading From: Emil Velikov To: Daniel Vetter Cc: Intel Graphics Development , LKML , DRI Development , Greg Kroah-Hartman , Andrew Morton Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1426 Lines: 33 On 27 November 2015 at 15:10, Daniel Vetter wrote: > It only leads to bloodshed and tears - we don't bother to restore a > working legacy vga hw setup. > > On haswell with the new dynamic power well code this leads to even > more hilarity since for some configurations the hardware is simply no > longer there. > > The actual implementation is a bit a hack - we realy on fbcon to kick > out the vgacon. To make this also work with I915_FBDEV=n (or FBCON=n) > and VGA_CONSOLE=y i915 already unregisters the vga console manually > early in the driver load sequence. > Interesting... nv50 and later GPUs are in a roughly similar shame afaict. They lack the dedicated hardware and no one really bothered figuring out how to restore things to a working shape [1]. Then again, upon sequential load of the nouveau module the GPU gets initialised properly, where you can get X (weston?) up and running without issues. Am I thinking about a different thing ? I take it that you guys do less of the (re)initialisation dance, to ensure faster boot times ? Thanks, Emil [1] http://nouveau.freedesktop.org/wiki/KernelModeSetting/#deactivatingkmsandunloadingnouveau -- 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/