Received: by 2002:ac0:a5a7:0:0:0:0:0 with SMTP id m36-v6csp32241imm; Tue, 17 Jul 2018 20:03:39 -0700 (PDT) X-Google-Smtp-Source: AAOMgpd8+e3qQRFqn2RaPmplKN170/SDfM7QSvGM2x8aAOb6BItNdHnCpVbJCXHSpA+fhR0QR6rM X-Received: by 2002:a63:2ec3:: with SMTP id u186-v6mr3982628pgu.225.1531883019026; Tue, 17 Jul 2018 20:03:39 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1531883018; cv=none; d=google.com; s=arc-20160816; b=DcvZ7YwarNbYmvRNZ7Ll2kI6S4owHIfMYCEMwxAGNHcE7UgyvduYrqPpviCxO2KoPX SMEBCReYZEqDDFKN16LHSUUng57UR6gKdkislNDlHtIux52iwOROwhcCYeKLHjp4a5CZ HWngx1Cd22JJVDiBRWQ0SzpB8VOOjrprr/q3z/H4NBhSAQ0x9Qi0ORftTqL1BkKYrY+g IcvYIy7n1qUW75BZZoRfre4u0mTPHtmiu5VW6oH04fqZeWu/I1ftQj52c03onEHqqfXe wiFdncXB4rnsTg1SuwNAu1E2ENTTF02T6Qf37xfWYmwn5CImyhjHT/JLRBOGgXAlB4x9 16eQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:content-transfer-encoding :content-disposition:mime-version:message-id:subject:to:from:date :arc-authentication-results; bh=OXbMf3LJ9TOR2mSK+QM7QIATSPHRdYIcmLjGEQ+Gjy0=; b=Lu4eyDhklcTcAaMrD8hni7h8dOzDK7D/+oFTP5FLnPCzst1g0Q8tkEl11OF9q2+Hj0 QAi+zv72LeiHeTn/2mSKwZrlJfdF/37an8eIWbWpkkJ3vWihh0/TaRwa+xkIuTIUa94O DPIX/1oy7xn6AqU4JOEJO5DgbSkkt9l62pM429bxOcXVkErKSZ9WIQToKkm2dMTLYDF6 3+agiPmYgTyXmBilV9pjRA3v7FIEuc3B1JUtGmK1TfZANRP/ffaoRUogAMNrTelY2h0q L00+HeA/VyCD2AY+6i+kz64Atl6EpicRYzc6R7ment3DkVrnv5Hf/Ej9Wr+fJdb45b1Z 2dTg== 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 l7-v6si2376691pgc.650.2018.07.17.20.03.23; Tue, 17 Jul 2018 20:03:38 -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 S1731485AbeGRDhj (ORCPT + 99 others); Tue, 17 Jul 2018 23:37:39 -0400 Received: from tartarus.angband.pl ([89.206.35.136]:37584 "EHLO tartarus.angband.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1731138AbeGRDhi (ORCPT ); Tue, 17 Jul 2018 23:37:38 -0400 Received: from kilobyte by tartarus.angband.pl with local (Exim 4.89) (envelope-from ) id 1ffciu-0007xu-Uf; Wed, 18 Jul 2018 05:01:52 +0200 Date: Wed, 18 Jul 2018 05:01:52 +0200 From: Adam Borowski To: Greg Kroah-Hartman , Jiri Slaby , linux-console@vger.kernel.org, Bartlomiej Zolnierkiewicz , linux-fbdev@vger.kernel.org, linux-kernel@vger.kernel.org Subject: [PATCH 0/6] vt: no blinking on console, 256/24-bit color improvements Message-ID: <20180718030152.kdq53mwpdfusvwl5@angband.pl> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit X-Junkbait: aaron@angband.pl, zzyx@angband.pl User-Agent: NeoMutt/20170113 (1.7.2) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: kilobyte@angband.pl X-SA-Exim-Scanned: No (on tartarus.angband.pl); SAEximRunCond expanded to false Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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. Diffstat: drivers/tty/vt/vt.c | 56 +++++++++++++++++++++++++++++--------------------------- drivers/video/fbdev/core/fbcon.c | 1 + include/linux/console_struct.h | 4 ++-- 3 files changed, 32 insertions(+), 29 deletions(-) -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ A dumb species has no way to open a tuna can. ⢿⡄⠘⠷⠚⠋⠀ A smart species invents a can opener. ⠈⠳⣄⠀⠀⠀⠀ A master species delegates.