From: Rene Herman <rene.herman@gmail.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Jan Engelhardt <jengelh@linux01.gwdg.de>,
Linus Torvalds <torvalds@linux-foundation.org>,
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: Thu, 03 May 2007 01:18:44 +0200 [thread overview]
Message-ID: <46391C54.5070503@gmail.com> (raw)
In-Reply-To: <463917DD.8020500@zytor.com>
On 05/03/2007 12:59 AM, H. Peter Anvin wrote:
> Rene Herman wrote:
>> Checking here, and mine also has 132x25 as BIOS mode 0x14 in addition to
>> 0x55. Probably also not universal, and 0x54 (132x43) doesn't seem to be
>> repeated. Unfortunate that Qemu/Bocks don't have the VESA text modes.
>
> Does it export these modes though the VESA interface, or do you have to
> "select them blind?"
It also provides them as VESA modes yes. On further inspection, 0x14 is
actually a bit different:
BIOS 0x14 = 132x25, 8x16 char cell on 1056x400
BIOS 0x54 = VESA 0x10A = 132x43, 8x8 char cell on 1056x350
BIOS 0x55 = VESA 0x109 = 132x25, 8x14 char cell on 1056x350
Booting 2.6.20.1 on the machine with vga=ask finds BIOS 0x14 as 0214 and
VESA 0x10A as 030A but allows me to select 0254, 0255 and 0309 as well.
('scan' finds BIOS 0x14 as 0114 and BIOS 0x54 as 0154)
Rene.
next prev parent reply other threads:[~2007-05-02 23:21 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
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 [this message]
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=46391C54.5070503@gmail.com \
--to=rene.herman@gmail.com \
--cc=ak@suse.de \
--cc=ebiederm@xmission.com \
--cc=hpa@zytor.com \
--cc=jeff@garzik.org \
--cc=jengelh@linux01.gwdg.de \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--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