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] [day] [month] [year] [list]

Message-Id: <1184798883.4523.80.camel@daplas>
Date:	Thu, 19 Jul 2007 06:48:03 +0800
From:	"Antonino A. Daplas" <adaplas@...il.com>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	Al Boldi <a1426z@...ab.com>, linux-kernel@...r.kernel.org
Subject: Re: VESAFB CUSTOM RESOLUTION

On Wed, 2007-07-18 at 10:38 -0700, H. Peter Anvin wrote:
> 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.

Yes, it's a lot of extra code that will be used only once, I would
rather not have it in the setup code. It's more appropriate for uvesafb
to implement that functionality.

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/