mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Dave Airlie <airlied@gmail.com>
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] vgacon/vt: clear buffer attributes when we load a 512 character font
Date: Thu, 24 Jan 2013 06:18:58 -0600	[thread overview]
Message-ID: <1ef10934-f81f-4a4b-b4a9-4d499e9721bc@email.android.com> (raw)
In-Reply-To: <CAPM=9tzqfDb7wtwRbDcYYcoB_HBLWksP8NYggsfj_GcNu=CY-A@mail.gmail.com>

The characters will morph anyway, it is just a matter off having them randomly scream with the intensity bit.

512-character mode is definitely useful... we get much wider language coverage with 512 than with 256, which is why most distros use a 512 console font.

Dave Airlie <airlied@gmail.com> wrote:

>On Thu, Jan 24, 2013 at 3:20 PM, H. Peter Anvin <hpa@zytor.com> wrote:
>> We should clear this bit presumably on switching either from or to
>512-char mode, since the bit doesn't really make sense either way.
>
>Yeah the only problem going from 512-char is that chars above 256 will
>morph into garbage chars below 256, like ctrl chars, I don't really
>want to face into doing some sort of safe translation out of 512-char
>mode, from reading around the net, 512 char mode doesn't seem all that
>brilliantly useful.
>
>Dave.

-- 
Sent from my mobile phone. Please excuse brevity and lack of formatting.

  reply	other threads:[~2013-01-24 12:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-24  4:22 Dave Airlie
2013-01-24  5:20 ` H. Peter Anvin
2013-01-24  8:32   ` Dave Airlie
2013-01-24 12:18     ` H. Peter Anvin [this message]
2013-01-25  2:22       ` Dave Airlie
2013-01-25  2:26         ` H. Peter Anvin

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=1ef10934-f81f-4a4b-b4a9-4d499e9721bc@email.android.com \
    --to=hpa@zytor.com \
    --cc=airlied@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®