Received: by 10.223.164.202 with SMTP id h10csp1221348wrb; Fri, 17 Nov 2017 16:32:40 -0800 (PST) X-Google-Smtp-Source: AGs4zMacoIJDMWSEnFnElWHXQ9GC45LCA+0A5k3GSOfwwij0z3eZRvE4i6YTuu+3smJs7/BiQaeR X-Received: by 10.98.36.199 with SMTP id k68mr3744792pfk.236.1510965160380; Fri, 17 Nov 2017 16:32:40 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1510965160; cv=none; d=google.com; s=arc-20160816; b=jvXysQarQH5naHJnoMuKrsYAs3kGoiusiWsKL28w6rPvnd3DlWQ7r5F7+NVgszJye+ MVpveVoWgKoNXqkQVS5fFkVsDCKRWBF2gIhxsVO7rrq+9kbdJdaDSwFq+QT+qyKGK5gK 57iNGBNsvAUVpmdHNeU69GEJIuxZsMapyQc8P5Aslh5xjOdvKdWzrOvE5S8akql9Eeo7 ZDDoQQK5FvPIjRZUv5eziJo0JBi81mGzTO3bKZ674Nq9Pm4MCOBCZIjlRSQg1cNIXxVI +xknpzjtwx22kl5ecd2iQIOlETMflEcyL9DHIrzNpOtjs1u3EECPUTpwXJYTUgCuXTMb MVXw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:message-id:content-disposition :content-transfer-encoding:mime-version:in-reply-to:references:cc :user-agent:date:subject:to:from:dkim-signature :arc-authentication-results; bh=yRSdf0iKdBlJskbIJZ2B2OSTZuINfLlU0TAI/OOcO9w=; b=Ke2LmrljdlbtzDeiC6JPYoA0CYsPuapMtBd9aIPMjqwp6CjBsaWzaqSjPPIBo5Jr8K DZ4uh2FtCvvvPq7XcMBZ1ioQHMu2sY18JJiGMJuC9GeU5/9cxSUJFmZPfqBu6dpncV6S xlgB5df6kYuITFQPGhhdQCcJ27YAOR+n6UlNV+YV0YAjle7zQCbxPUnnk0o/D07KZPOR xD9f95JqAXHEzMuISQhHLRSaoboDnCogCa0hAXECay+W5dCvqYLnT4rgTa6IqiPvqiE9 GdZpsSzEBF4g1EZociV4UnXYifiJWwTh3D30LEiVQmTVy6t61qdrarl5iInuTV3stDzJ ygfA== ARC-Authentication-Results: i=1; mx.google.com; dkim=temperror (no key for signature) header.i=@rainbow-software.org header.s=atlsmtp header.b=STffsTO5; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id bi5si3574590plb.240.2017.11.17.16.32.26; Fri, 17 Nov 2017 16:32:40 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=temperror (no key for signature) header.i=@rainbow-software.org header.s=atlsmtp header.b=STffsTO5; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754986AbdKQT1A (ORCPT + 93 others); Fri, 17 Nov 2017 14:27:00 -0500 Received: from smtp-1b.atlantis.sk ([80.94.52.26]:53755 "EHLO smtp-1b.atlantis.sk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757171AbdKQT01 (ORCPT ); Fri, 17 Nov 2017 14:26:27 -0500 Received: from [192.168.0.2] (188-167-69-119.dynamic.chello.sk [188.167.69.119]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp-1b.atlantis.sk (Postfix) with ESMTPSA id 2F88683449E3; Fri, 17 Nov 2017 20:26:25 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=rainbow-software.org; s=atlsmtp; t=1510946785; bh=9YqcabVGWcQv+HDZLciM2/nTc5NgyGJZhyOZV0wMl8E=; h=From:To:Subject:Date:Cc:References:In-Reply-To; b=STffsTO5AtqjWn31cv4gZKIka1JwdDm/Cl+S6eTGqrwrcuLvXmbT4Nau+jKDQKlk/ LauOAtfQ8bvER1/ndfgK9E1zVV+HV6QzQOmqN6GQNqQiuWOwxOG/0nqI+7NAL/2JAn +ZO+05P6cBvx1LByhz0z3sIj1poq+LduMJvmtvJ0= From: Ondrej Zary To: Ilia Mirkin Subject: Re: Blank console but X11 works on MCP79 - old regression since 3.8 Date: Fri, 17 Nov 2017 20:25:14 +0100 User-Agent: KMail/1.9.10 (enterprise35 0.20100827.1168748) Cc: Ben Skeggs , "nouveau@lists.freedesktop.org" , "linux-kernel@vger.kernel.org" References: <201711171526.01053.linux@rainbow-software.org> <201711171833.52855.linux@rainbow-software.org> In-Reply-To: X-KMail-QuotePrefix: > MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <201711172025.15121.linux@rainbow-software.org> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Friday 17 November 2017 18:41:17 Ilia Mirkin wrote: > On Fri, Nov 17, 2017 at 12:33 PM, Ondrej Zary > > wrote: > > @@ -483,8 +483,8 @@ > > nouveau 0000:02:00.0: disp: 0860: 00000000 -> 00000500 > > nouveau 0000:02:00.0: disp: 0864: 00000000 > > nouveau 0000:02:00.0: disp: 0868: 00000000 -> 04000500 > > -nouveau 0000:02:00.0: disp: 086c: 00000000 -> 00100500 > > -nouveau 0000:02:00.0: disp: 0870: 0000e900 -> 00001e00 > > +nouveau 0000:02:00.0: disp: 086c: 00000000 -> 00100a00 > > +nouveau 0000:02:00.0: disp: 0870: 0000e900 -> 0000e800 > > nouveau 0000:02:00.0: disp: 0874: 00000000 -> ffff0000 > > nouveau 0000:02:00.0: disp: 0878: 00000000 > > nouveau 0000:02:00.0: disp: 0880: 05000000 > > > > Looks like it's using 8bpp (0x1e00) in 32MB case but 16bpp (0xe800) in > > 64MB case. Why? > > > > I get blank screen even with 64MB with video=1280x1024-8 kernel > > parameter. Console works with video=1280x1024-16 even with 32MB stolen > > memory. > > > > Conclusions: 8-bit support is broken and bpp reduction is weird. > > OK, well that makes a *ton* of sense (8bpp being broken). > > I think the idea of bpp reduction is that when you're on your shiny > new Riva TNT with 16MB of VRAM, you don't want to go crazy allocating > all that to a pinned fbcon - almost half of that would go to a single > 32bpp 1600x1200 buffer, more for 1920x1200. You want to be able to > have at least a few fb-sized buffers for backbuffer rendering, etc. > > The specific limits could probably use tweaking - I think they only > consider VRAM size, not the fb size. > > I guess 8bpp worked prior to the change you bisected though, so we > should figure out what we did wrong in the new code. Yes, booted 3.7 (last working kernel) and it's running in 8bpp. I guess that nv50_head_gamma_set() is missing something like this (from nv_crtc_gamma_set()): /* We need to know the depth before we upload, but it's possible to * get called before a framebuffer is bound. If this is the case, * mark the lut values as dirty by setting depth==0, and it'll be * uploaded on the first mode_set_base() */ if (!nv_crtc->base.primary->fb) { nv_crtc->lut.depth = 0; return 0; } That's easy to add but there's no mode_set_base() for nv50 so there's no place to add code like this: if (nv_crtc->lut.depth != drm_fb->format->depth) { nv_crtc->lut.depth = drm_fb->format->depth; nv_crtc_gamma_load(crtc); } -- Ondrej Zary From 1584358738267792301@xxx Fri Nov 17 23:43:56 +0000 2017 X-GM-THRID: 1584342040192660961 X-Gmail-Labels: Inbox,Category Forums,HistoricalUnread