From: "Alan Curry" <pacman-kernel@manson.clss.net>
To: aebr@win.tue.nl (Andries Brouwer)
Cc: akpm@osdl.org (Andrew Morton),
linux-kernel@vger.kernel.org, eich@freedesktop.org
Subject: Re: SVGATextMode on 2.6.11
Date: Tue, 22 Mar 2005 16:31:11 -0500 (EST) [thread overview]
Message-ID: <20050322213114.20103.qmail@manson.clss.net> (raw)
In-Reply-To: <20050322200616.GA4583@pclin040.win.tue.nl> from "Andries Brouwer" at Mar 22, 2005 09:06:16 PM
Andries Brouwer writes the following:
>
>> "Alan Curry" <pacman-kernel@manson.clss.net> wrote:
>>> An SVGATextMode
>>> block cursor isn't affected by ^[c -- it truly *becomes* the default
>
>True - it is obtained by hardware reprogramming. But having lots of programs
>touch the hardware is getting less popular.
Yes, I realize that SVGATextMode is probably considered obsolete by now. If
the new cursor-restoring code actually solved a problem, SVGATextMode
breakage is an acceptable side effect.
>Concerning your 1. - You know that such an echo actually creates the VC?
>I still recall the times that there was not enough memory for more than
>four or five VCs, but probably you don't mind wasting a few hundred kB.
I did find a better way, as explained in a subsequent message: Set the
console font before changing the cursor, and don't touch it afterward.
next prev parent reply other threads:[~2005-03-22 21:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-02 22:38 SVGATextMode on 2.6.11 Alan Curry
2005-03-21 22:18 ` Andrew Morton
2005-03-22 20:06 ` Andries Brouwer
2005-03-22 21:31 ` Alan Curry [this message]
[not found] <no.id>
2005-03-04 23:33 ` Alan Curry
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=20050322213114.20103.qmail@manson.clss.net \
--to=pacman-kernel@manson.clss.net \
--cc=aebr@win.tue.nl \
--cc=akpm@osdl.org \
--cc=eich@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;
as well as URLs for NNTP newsgroup(s).