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 22:20:26 +0800 [thread overview]
Message-ID: <1184768426.4523.20.camel@daplas> (raw)
In-Reply-To: <200707181645.01097.a1426z@gawab.com>
On Wed, 2007-07-18 at 16:45 +0300, Al Boldi wrote:
> Antonino A. Daplas wrote:
> > 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.
>
> Thanks for a great explanation!
>
> Looks like this chip supports VBE 3.0, but it only locks into 60Hz refresh.
> Here is an excerpt; full log attached.
>
>
What you need to look at the X log is this particular part (this is the
output of my card, and for the sake of brevity, I removed the
descriptive sections):
Mode: 100 (640x400)
Mode: 101 (640x480)
Mode: 102 (800x600)
Mode: 103 (800x600)
Mode: 104 (1024x768)
Mode: 105 (1024x768)
Mode: 106 (1280x1024)
Mode: 107 (1280x1024)
*Mode: 10e (320x200)
Mode: 10f (320x200)
*Mode: 111 (640x480)
Mode: 112 (640x480)
*Mode: 114 (800x600)
Mode: 115 (800x600)
*Mode: 117 (1024x768)
Mode: 118 (1024x768)
Mode: 11a (1280x1024)
Mode: 11b (1280x1024)
Mode: 130 (320x200)
Mode: 131 (320x400)
*Mode: 132 (320x400)
Mode: 133 (320x400)
Mode: 134 (320x240)
*Mode: 135 (320x240)
Mode: 136 (320x240)
*Mode: 13d (640x400)
Mode: 13e (640x400)
Mode: 145 (1600x1200)
Mode: 146 (1600x1200)
Mode: 147 (1400x1050)
Mode: 148 (1400x1050)
Mode: 152 (2048x1536)
The list of modes include standard VESA modes and custom modes such as
2048x1536. So, if I want to use this mode for vesafb, I will add
vga=0x352 (0x152 + 0x200) to my boot line.
Tony
next prev parent reply other threads:[~2007-07-18 14:20 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
2007-07-18 13:45 ` Al Boldi
2007-07-18 14:20 ` Antonino A. Daplas [this message]
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=1184768426.4523.20.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