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]

Message-ID: <469E502E.8060000@zytor.com>
Date:	Wed, 18 Jul 2007 10:38:54 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	"Antonino A. Daplas" <adaplas@...il.com>
CC:	Al Boldi <a1426z@...ab.com>, linux-kernel@...r.kernel.org
Subject: Re: VESAFB CUSTOM RESOLUTION

Antonino A. Daplas wrote:
> 
>> What about the VBE 3.0 arbitrary vertical refresh rate thing?
> 
> This is not implemented by the video-vesa.c because it will require
> complex calculations of mode timings (such as with GTF) to be done
> before starting the kernel.  However, uvesafb probably does.
> 

There is no real reason video-vesa.c couldn't do those calculations, but
it would have to get the information from the command line proper and
not just from the 16-bit vga= mode number.  That is a minor
complication, but not significant (the new setup code has a proper
command line parser.)

The desirability of it is another matter, especially since it wouldn't
let any switching happen at runtime.

	-hpa
-
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/