From: "Antonino A. Daplas" <adaplas@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Rene Herman <rene.herman@gmail.com>,
"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: Wed, 02 May 2007 07:18:29 +0800 [thread overview]
Message-ID: <1178061509.4606.27.camel@daplas> (raw)
In-Reply-To: <alpine.LFD.0.98.0705011433050.3808@woody.linux-foundation.org>
On Tue, 2007-05-01 at 14:41 -0700, Linus Torvalds wrote:
>
> On Tue, 1 May 2007, Rene Herman wrote:
> >
> 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.
>
I would agree with the lean and mean, but faster, that's another
question. Even vesafb at 640x480-8 with ypan and mtrr is 30% faster
than vgacon (And for those of you with vesafb that cannot ypan, try
vgacon with the 'no-scroll' option for a more apple-to-apple
comparison). And with chipset-specific drivers, it can be as much as 3x
faster than vgacon.
Anyway, my default console is still text mode, even though I'm the
framebuffer maintainer :-)
Tony
next prev parent reply other threads:[~2007-05-01 23:18 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-01 1:33 arch/i386/boot rewrite, and all the hard-coded video cards 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
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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
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=1178061509.4606.27.camel@daplas \
--to=adaplas@gmail.com \
--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 \
--cc=torvalds@linux-foundation.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