linux-kernel - Re: VESAFB CUSTOM RESOLUTION

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 18 Jul 2007 20:15:17 +0800
From:	"Antonino A. Daplas" <adaplas@...il.com>
To:	Al Boldi <a1426z@...ab.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: VESAFB CUSTOM RESOLUTION

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

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/