From: "Antonino A. Daplas" <adaplas@gmail.com>
To: linux-fbdev-devel@lists.sourceforge.net
Cc: santiago@mail.cz
Subject: Re: Framebuffer questions
Date: Fri, 17 Mar 2006 05:26:39 +0800 [thread overview]
Message-ID: <4419D80F.9030806@gmail.com> (raw)
In-Reply-To: <20060316101744.GA3034@localhost.localdomain>
Ondrej Zajicek wrote:
> Thank you for answers. Perhaps i found some time to write
> some API documentation.
>
> On Thu, Mar 16, 2006 at 09:20:42AM +0800, Antonino A. Daplas wrote:
>>> - If i have to supply complete mode timings for videomode change
>>> why there is modedb.c and mode lines stored inside drivers?
>> Usually, these entries are used only on startup. Some drivers support
>> built-in internal mode tables, some use standard algo's (GTF, CVT) to
>> compute the mode timings. With these drivers, passing xres and yres is
>> usually enough.
>
> So with these drivers it is not possible to set non-standard timings
> (because other timing arguments are always ignored)?
As long as the modeline is valid, drivers tend to accept them. It is only
when you passed invalid timings that drivers will
a. reject;
b. compute with GTF/CVT; or
c. get the nearest modeline from its internal table.
Tony
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
next prev parent reply other threads:[~2006-03-16 21:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-15 21:10 Framebuffer questions Ondrej Zajicek
2006-03-16 1:20 ` Antonino A. Daplas
2006-03-16 10:17 ` Ondrej Zajicek
2006-03-16 21:26 ` Antonino A. Daplas [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-02-09 21:12 framebuffer questions Scott D. Davilla
2008-02-10 11:11 ` 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=4419D80F.9030806@gmail.com \
--to=adaplas@gmail.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=santiago@mail.cz \
/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;
as well as URLs for NNTP newsgroup(s).