From: "Antonino A. Daplas" <adaplas@gmail.com>
To: Al Boldi <a1426z@gawab.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: VESAFB CUSTOM RESOLUTION
Date: Wed, 18 Jul 2007 20:15:17 +0800 [thread overview]
Message-ID: <1184760917.4523.13.camel@daplas> (raw)
In-Reply-To: <200707181342.00647.a1426z@gawab.com>
On Wed, 2007-07-18 at 13:42 +0300, Al Boldi wrote:
> Geert Uytterhoeven wrote:
> > On Wed, 18 Jul 2007, Sasa Ostrouska wrote:
> Is there any technical reason why vesafb shouldn't support non-BIOS modes?
>
vesafb can only use modes included by the vendor in the card's BIOS. The
mode table contains standard modes defined by VESA, and perhaps
vendor-defined custom modes. However, the mode ID of custom modes varies
from card to card, so you have to 'probe' the BIOS first for the list of
modes and their associated ID. X + the 'vesa' driver does that probe,
and so does the lrmi tool vbetest.
So, one cannot just set any mode, unless that mode is already defined in
the BIOS mode table. In VBE 3.0, you might be able to choose an
arbitrary vertical refresh rate, but that's the best mode tuning you can
do with the video BIOS.
Tony
next prev parent reply other threads:[~2007-07-18 12:15 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-18 10:42 VESAFB CUSTOM RESOLUTION Al Boldi
2007-07-18 12:15 ` Antonino A. Daplas [this message]
2007-07-18 13:45 ` Al Boldi
2007-07-18 14:20 ` Antonino A. Daplas
2007-07-18 14:52 ` Al Boldi
2007-07-18 15:07 ` Antonino A. Daplas
2007-07-18 17:38 ` H. Peter Anvin
2007-07-18 22:48 ` Antonino A. Daplas
2007-07-18 16:59 ` Matan Ziv-Av
2007-07-18 22:43 ` Antonino A. Daplas
-- strict thread matches above, loose matches on Subject: below --
2007-07-17 14:13 Sasa Ostrouska
2007-07-17 14:31 ` Jesper Juhl
2007-07-17 14:42 ` Renato S. Yamane
2007-07-17 15:04 ` Sasa Ostrouska
2007-07-18 11:35 ` Gerd Hoffmann
2007-07-17 20:44 ` Antonino A. Daplas
2007-07-17 21:13 ` Sasa Ostrouska
2007-07-18 1:50 ` Daniel Drake
2007-07-18 6:36 ` Sasa Ostrouska
2007-07-18 9:16 ` Geert Uytterhoeven
2007-07-18 9:50 ` Sasa Ostrouska
2007-07-18 11:19 ` Geert Uytterhoeven
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=1184760917.4523.13.camel@daplas \
--to=adaplas@gmail.com \
--cc=a1426z@gawab.com \
--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