From: Linus Torvalds <torvalds@linux-foundation.org>
To: Rene Herman <rene.herman@gmail.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Andi Kleen <ak@suse.de>, Jeff Garzik <jeff@garzik.org>,
Jeremy Fitzhardinge <jeremy@goop.org>
Subject: Re: arch/i386/boot rewrite, and all the hard-coded video cards
Date: Tue, 1 May 2007 14:41:52 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.0.98.0705011433050.3808@woody.linux-foundation.org> (raw)
In-Reply-To: <4637A3F6.70508@gmail.com>
On Tue, 1 May 2007, Rene Herman wrote:
>
> The answer will probably be "no", but would this be a good point to ask if
> this would be a good time to not bother with the mode switching code at all
> anymore?
The standard extended modes are actually really useful, if for a very
simply reason: they give you bigger more lines on screen when a bug
happens.
So I _still_ occasionally use "vga=extended" just for that reason. The
default 80x25 thing scrolls most oops away.
> I'd consider keeping anything but VESA 1.2 (which that ET4000 and most all
> other Super VGA cards of the era also do!) nonsensical and as far as I'm
> concerned this includes all the VGA modes with the strange number of lines; a
> 43/60-line VGA screen is too horrible to look at anyway...
80x50 is useful for the above reason. Yeah, it's ugly, but it's useful for
the "It's too much work to try to do anything but just take a digital
photo of the screen". And that 50-line mode will actually be 43 in EGA
mode, I think.
The 132x50 mode is probably a bit prettier, and is fairly common too, and
useful for the same reason.
And once you support those, you might as well support all the VESA text
modes.
And yes, I'm literally talking about the *text* modes. Not all of us want
to have fbcon built in - I prefer my text-mode lean and mean and fast as
hell, and if I want a frame buffer, I'll take X11, thank you very much.
Linus
next prev parent reply other threads:[~2007-05-01 21:42 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-01 1:33 H. Peter Anvin
2007-05-01 1:40 ` Jeff Garzik
2007-05-01 1:42 ` H. Peter Anvin
2007-05-02 7:46 ` Martin Mares
2007-05-02 9:22 ` Andi Kleen
2007-05-02 20:49 ` H. Peter Anvin
2007-05-03 2:15 ` H. Peter Anvin
2007-05-02 19:05 ` Lennart Sorensen
2007-05-01 1:51 ` Dave Jones
2007-05-01 2:17 ` H. Peter Anvin
2007-05-01 2:34 ` Eric W. Biederman
2007-05-01 3:46 ` Andi Kleen
2007-05-01 2:54 ` H. Peter Anvin
2007-05-01 4:29 ` Andi Kleen
2007-05-01 3:38 ` H. Peter Anvin
2007-05-01 3:06 ` Eric W. Biederman
2007-05-01 3:21 ` H. Peter Anvin
2007-05-01 3:41 ` Eric W. Biederman
2007-05-01 3:44 ` H. Peter Anvin
2007-05-01 2:43 ` Linus Torvalds
2007-05-01 2:59 ` Dave Jones
2007-05-01 20:32 ` Rene Herman
2007-05-01 21:01 ` Rene Herman
2007-05-01 21:41 ` Linus Torvalds [this message]
2007-05-01 21:52 ` H. Peter Anvin
2007-06-14 4:51 ` Oleg Verych
2007-06-14 5:11 ` H. Peter Anvin
2007-06-14 7:18 ` Oleg Verych
2007-05-01 22:59 ` Rene Herman
2007-05-01 23:18 ` Antonino A. Daplas
2007-05-02 18:22 ` Jan Engelhardt
2007-05-02 20:59 ` H. Peter Anvin
2007-05-02 21:07 ` Rene Herman
2007-05-02 21:15 ` H. Peter Anvin
2007-05-02 21:20 ` Rene Herman
2007-05-02 21:25 ` H. Peter Anvin
2007-05-02 21:39 ` Rene Herman
2007-05-02 22:11 ` H. Peter Anvin
2007-05-02 22:49 ` Rene Herman
2007-05-02 22:59 ` H. Peter Anvin
2007-05-02 23:18 ` Rene Herman
2007-05-03 2:09 ` H. Peter Anvin
2007-05-01 3:56 ` WANG Cong
2007-05-01 22:41 Vlad
2007-05-01 23:22 ` Rene Herman
2007-05-02 1:10 ` Vlad
2007-05-02 18:25 ` Jan Engelhardt
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=alpine.LFD.0.98.0705011433050.3808@woody.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=ak@suse.de \
--cc=ebiederm@xmission.com \
--cc=hpa@zytor.com \
--cc=jeff@garzik.org \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rene.herman@gmail.com \
/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®