Received: by 2002:ac0:a5a7:0:0:0:0:0 with SMTP id m36-v6csp3690304imm; Sat, 21 Jul 2018 00:44:29 -0700 (PDT) X-Google-Smtp-Source: AAOMgpfnRUdCVEvdISIwJXBFbuJ2EfeTj/0ySZaiVQg6uE6+c8m9p2Ckupi0xnabdfCoJxNzrTZx X-Received: by 2002:a62:401:: with SMTP id 1-v6mr5164936pfe.28.1532159069210; Sat, 21 Jul 2018 00:44:29 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1532159069; cv=none; d=google.com; s=arc-20160816; b=ZO/YxInEzEvRlDWztr3etDpvB7dTD7ISFdUneIeqrKeoLLK15ZGp7NgKWfghjZkDdH kw3/eeWpn49o48949ftL+evZA8jpxsi0/uOKBSF/PYbjgZAx80g1Eg0dIPfvmfYhLhUp jXX4XBTMr2tfnPjB8hejGrdq/6lyIhS2fOYsj91hnGodJP2G3wJoF5qmbiEJiormdRDD 22/Ei9xC9n55sIu/UhrcIgSUU40t5eaAe+C6X2+kgp/113xBUPrRqW/z1yqLO8Igqrd8 700rhpTKnZ8QQ3Uyxi9M0fW83qdcBqjwKSI2w8KRZevId/qxv4R9MXBDPjmmPy9fib3c 9epQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:arc-authentication-results; bh=BXmOKzndTDZxPPjUJ1r6WTBeTzvJePWcd/s9fyWITdU=; b=ySgk8LUjBPxGfVKpPfG+kYl/zDh+ivqPnEEV3RKc47VVQ6CmPU+onNveqAOxxfMxP1 pq/fMT3M/Yx3xZ3E9neKWH+zzjQrO202nDzUau/BogA5NYUtQ1BMrqAJDA+Ng6HadP8c uXPUo9xM84W1ZHomJWv5Dq0A6ISqQErO79kfBEC8ThZvOG6WYKgKSTHRlr4yYBEcCHVz WWQLX5ml0+0yH7eC2K/NCTRVlZIEQPFon/pv2b9S7RMGscVl+mf3+2NG9jm4WSkqI2wh zrbiTbvlxqnrG5oD8x8roMpxoiEL1ioldcb69x9zTBMIQIikgEzvLmQIl0BSTksCPr3I yH5w== ARC-Authentication-Results: i=1; mx.google.com; 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 d31-v6si3291734pla.190.2018.07.21.00.44.13; Sat, 21 Jul 2018 00:44:29 -0700 (PDT) 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; 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 S1727486AbeGUIfJ (ORCPT + 99 others); Sat, 21 Jul 2018 04:35:09 -0400 Received: from mail.linuxfoundation.org ([140.211.169.12]:48640 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727162AbeGUIfJ (ORCPT ); Sat, 21 Jul 2018 04:35:09 -0400 Received: from localhost (LFbn-1-12238-233.w90-92.abo.wanadoo.fr [90.92.53.233]) by mail.linuxfoundation.org (Postfix) with ESMTPSA id F16EBAE7; Sat, 21 Jul 2018 07:43:21 +0000 (UTC) Date: Sat, 21 Jul 2018 09:43:19 +0200 From: Greg Kroah-Hartman To: Adam Borowski Cc: Jiri Slaby , linux-console@vger.kernel.org, Bartlomiej Zolnierkiewicz , linux-fbdev@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 0/6] vt: no blinking on console, 256/24-bit color improvements Message-ID: <20180721074319.GA30454@kroah.com> References: <20180718030152.kdq53mwpdfusvwl5@angband.pl> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180718030152.kdq53mwpdfusvwl5@angband.pl> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Jul 18, 2018 at 05:01:52AM +0200, Adam Borowski wrote: > Hi! > Here's a patchset with two entangled improvements: > > * it'd be good to get rid of blinking where possible. Even CGA (thus VGA) > allows disabling it, rendering such characters with a bright background > instead. > * due to my error, 256-color mode uses a much darker palette for conversion, > resulting in behaving inconsistently with 24-bit mode. > > The new code uses bright backgrounds when possible, enabled with \e[100m or > \e[48;m. > > Despite the whole idea following a VGA capability, this patchset doesn't > change vgacon yet, just fbcon. The reason being: ~80% of x86 users have an > nVidia chip, which means nouveau or nvidia-proprietary. Nouveau implies > fbcon, nvidia-proprietary fails to properly restore text flags (as evidenced > by 512 glyph mode turning to 256 on switch from graphics). You don't care > about the proprietary driver, but let's not break it pointlessly, and as > both nVidia cards I own work only with nouveau, I don't want to touch what I > can't test. > > Thus, let's enable unblinking on fbcon for now. We can flip that bit (in > register 0x10) later. > > This fixes the display of catimg and similar tools. I've applied the first patch, as it was obvious :) For the rest, can you make it a config option as Alan said? And I agree, we don't care about breaking nvidia systems, go ahead :) thanks, greg k-h