Received: by 10.223.164.202 with SMTP id h10csp1382794wrb; Fri, 17 Nov 2017 20:43:45 -0800 (PST) X-Google-Smtp-Source: AGs4zMZf6vlkYNQeTpxsbO7eDHnhIzXB0J2sNGin/8Ari7SaBkJYc8v2BIxldxD+/yIV8hcWBeHk X-Received: by 10.84.216.81 with SMTP id f17mr7344091plj.330.1510980225553; Fri, 17 Nov 2017 20:43:45 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1510980225; cv=none; d=google.com; s=arc-20160816; b=sIDEIwmNwW/+3UYWjJlwpyC0pwUG9B2J7kZ11QuJX0STDPr767I/YZD1E9AYw7psiP C21nayDPmb0Ud0whxIFDlCvv1oqnKlkBT2TJ/pjnIImp1HSFgSptuxSorAgDRNg/Zedv mhQT/qip7hv1k354722kHH+aWE1yfZZRo7khaoWuCGGpbwycbRwPdriX6iUTPb70FBVu lLiXG3+viMmKIiYrQLWuWMW8DXaRvev58Ff5j4miH3fOBXT5jxeC7Nv7FVShqoUHnO3x f3F7kEfKMYseN8Pw45iI0DD8Inf8KQZ8tzjcDuuVmQ56EaCAwW773nayB6NuaDTBa4to RA+g== 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=AszLW4C17UpnYn8rQzlOA0t1hIz/YlcbZV7I+E+jIUo=; b=0btr/XkmFfKxNBxS9Ig5s+uG7z9ONjbSyN34d4k8hbmeawCzSr5zhkrpFgol1JYaAk Vqi01BBj2phdj20SF48Ecj+R8gZeUPuJuLYbgsf01GXlomgRilJaa1Zk5rPoFaqaFA9s zSlG3/f4tLb3RxXBYkAQzmwAd/hAg5Of3gdooTevllIFhESs7agwfNwBdn/r3r9r1Jom 2P9xR/DR0ntdxVVjph9Apvgx86s05Dwnf1FLcW6lnlHCOUICpEA8Gt1RtJGkUwy6ovlZ 61ZGD+zLEbXcSN7ZEOFtgd03getVXZ9aGDlM0HUWbenBnE+572By/qkv6wjjM3x3fluI 4YnQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=temperror (no key for signature) header.i=@rainbow-software.org header.s=atlsmtp header.b=Yakg5Ngz; 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 68si4340591pff.160.2017.11.17.20.43.32; Fri, 17 Nov 2017 20:43:45 -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=Yakg5Ngz; 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 S965924AbdKQUG6 (ORCPT + 93 others); Fri, 17 Nov 2017 15:06:58 -0500 Received: from smtp-1b.atlantis.sk ([80.94.52.26]:43353 "EHLO smtp-1b.atlantis.sk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S965813AbdKQUGW (ORCPT ); Fri, 17 Nov 2017 15:06:22 -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 4A78D83449E3; Fri, 17 Nov 2017 21:06:18 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=rainbow-software.org; s=atlsmtp; t=1510949178; bh=GT61VDQfHiE6TwiiwCNAEgFFB8g+60xd7oHgSCbPi9I=; h=From:To:Subject:Date:Cc:References:In-Reply-To; b=Yakg5NgzXEBrJAA5oXg+U76JGvIanO6cacIxpTtB1nXqW3y3XVIFhhqXg5dsxFOHM SoBmjoSENnQfRV6dApp9fuxerpR5qFkRPcxNUbZlCO91UjHA/Qa+0JlJhoHPPxIYBN +vHpHXbiBbmyIDukLf4ZCrokeiDEVcIcaSr9PjAU= 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 21:06:16 +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> 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: <201711172106.16346.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 20:52:45 Ilia Mirkin wrote: > On Fri, Nov 17, 2017 at 2:37 PM, Ilia Mirkin wrote: > > On Fri, Nov 17, 2017 at 2:25 PM, Ondrej Zary wrote: > >> 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. > > > > By the way, instead of booting $kernel, you can use modetest from > > libdrm/tests. Not sure if it supports C8 though =/ > > > > I think the issue is this: > > > > - OUT_RING(evo, nv_crtc->lut.depth == 8 ? > > - NV50_EVO_CRTC_CLUT_MODE_OFF : > > - NV50_EVO_CRTC_CLUT_MODE_ON); > > > > Whereas now we always set 0xC0000000 (aka "ON"). > Changing that to 0x80000000 does not help :( > In case I was being unclear, I'm talking about > > https://github.com/skeggsb/nouveau/blob/master/drm/nouveau/nv50_display.c#L >1808 > > and surrounding items. Looks like lut_clr sets 0x40000000 which was > previously not used. Not sure what the difference between that and > 0x00000000 is. This is what we have in rnndb for it: lut_clr is not called during boot so we can ignore it for now. > https://github.com/envytools/envytools/blob/master/rnndb/display/nv_evo.xml >#L408 > > So bit 30 is mode, set is "high res", unset is "low res". So really > what we want is 0x80000000 which leaves the LUT enabled but uses the > low-res mode? > > All this could use some playing-around with. > > -ilia -- Ondrej Zary From 1584377548652982217@xxx Sat Nov 18 04:42:55 +0000 2017 X-GM-THRID: 1584342040192660961 X-Gmail-Labels: Inbox,Category Forums,HistoricalUnread