Re: VESAFB CUSTOM RESOLUTION

[H. Peter Anvin]

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@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/