All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Antonino A. Daplas" <adaplas@gmail.com>
To: Pozsar Balazs <pozsy@uhulinux.hu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fix vgacon blanking
Date: Fri, 21 Oct 2005 08:01:03 +0800	[thread overview]
Message-ID: <43582FBF.1070406@gmail.com> (raw)
In-Reply-To: <20051020161311.GA30041@ojjektum.uhulinux.hu>

Pozsar Balazs wrote:
> Hi all,
> 
> This patch fixes a long-standing vgacon bug: characters with the bright 
> bit set were left on the screen and not blacked out.

I cannot reproduce the bug though, so this bug probably depends on the
chipset implementation of VGA. Everything works perfectly whatever value
is written to 0x3c6, so this register is either ignored or hardwired to
0xff.

> All I did was that I lookuped up some examples on the net about setting 
> the vga palette, and added the call missing from the linux kernel, but 
> included in all other ones. It works for me.
> 
> You can test this by writing something with the bright set to the 
> console, for example:
>   echo -e "\e[1;31mhello there\e[0m"
> and then wait for the console to blank itself (by default, after 10 mins 
> of inactivity), maybe making it faster using
>   setterm -blank 1
> so you only have to wait 1 minute.

The patch is obviously correct, and makes vgacon safe from rogue apps
that sets the the palette mask register to a different value.

> 
> 
> Signed-off-by: Pozsar Balazs <pozsy@uhulinux.hu>
Acked-by: Antonino Daplas <adaplas@pol.net>


  parent reply	other threads:[~2005-10-21  0:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-20 16:13 [PATCH] fix vgacon blanking Pozsar Balazs
2005-10-20 20:27 ` Bob Copeland
2005-10-21  0:01 ` Antonino A. Daplas [this message]
     [not found] <4ZLja-4gH-5@gated-at.bofh.it>
2005-10-20 21:23 ` Bodo Eggert
2005-10-20 21:54   ` Pozsar Balazs
2005-10-21  0:17   ` Antonino A. Daplas

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=43582FBF.1070406@gmail.com \
    --to=adaplas@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pozsy@uhulinux.hu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.