From: "Antonino A. Daplas" <adaplas@gmail.com>
To: phreak@gentoo.org
Cc: trivial@kernel.org, Antonino Daplas <adaplas@pol.net>,
linux-fbdev-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Updating Documentation/fb/vesafb.txt
Date: Sat, 05 Aug 2006 20:48:04 +0800 [thread overview]
Message-ID: <44D49384.9060701@gmail.com> (raw)
In-Reply-To: <200608050902.20163.phreak@gentoo.org>
Christian Heim wrote:
> Hello Antonino,
>
> + | 640x480 800x600 1024x768 1280x1024 1600x1200
> +----+-----------------------------------------------
> +256 | 0x301 0x303 0x305 0x307 0x???
> +32k | 0x310 0x313 0x316 0x319 0x373
> +64k | 0x311 0x314 0x317 0x31A 0x374
> +16M | 0x312 0x315 0x318 0x31B 0x375
>
> To enable one of those modes you have to specify "vga=ask" in the
> lilo.conf file and rerun LILO. Then you can type in the desired
This is not correct. VESA did not define 1600x1200 as part of
its DVT standard. And starting with VBE 2.0, VESA is not going to
define new mode ID's. Thus the mode ID that you get for 1600x1200 may
be unique only for your particular hardware/Video BIOS.
You may use X's 'vesa' driver to get a list of modes that your
BIOS supports. It will be written to /var/log/X*.0.log.
Tony
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
prev parent reply other threads:[~2006-08-05 12:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-05 7:02 [PATCH] Updating Documentation/fb/vesafb.txt Christian Heim
2006-08-05 12:48 ` Antonino A. Daplas [this message]
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=44D49384.9060701@gmail.com \
--to=adaplas@gmail.com \
--cc=adaplas@pol.net \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=phreak@gentoo.org \
--cc=trivial@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).