From: "Antonino A. Daplas" <adaplas@gmail.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Al Boldi <a1426z@gawab.com>, linux-kernel@vger.kernel.org
Subject: Re: VESAFB CUSTOM RESOLUTION
Date: Thu, 19 Jul 2007 06:48:03 +0800 [thread overview]
Message-ID: <1184798883.4523.80.camel@daplas> (raw)
In-Reply-To: <469E502E.8060000@zytor.com>
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
next prev parent reply other threads:[~2007-07-18 22:48 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
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 [this message]
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=1184798883.4523.80.camel@daplas \
--to=adaplas@gmail.com \
--cc=a1426z@gawab.com \
--cc=hpa@zytor.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