From: Otto Solares <solca@guug.org>
To: fb-devel <linux-fbdev-devel@lists.sourceforge.net>
Subject: fbdev timings
Date: Mon, 15 Sep 2003 01:30:29 -0600 [thread overview]
Message-ID: <20030915073029.GA13799@guug.org> (raw)
hi!
finally i am coding the video part of a "desktop engine",
but i want something that works profesionally, i'm using
fbdev and embedded mesa for it, i am trying to get the
video modes as automagically as posible, in that regard
my plan is to hack get-edid (cause we don't have a proper
mechanism from userspace, yea modedb is marked _init
and the new edid just works in radeons and only usable
too from kernelspace -end of critic :) into my software
and fallback to a text database like hwdata to obtain
monitor specs if edid doesn't work, but i have a problem,
how i am supposed to construct fbdev timings with just
this info:
- resolution (width x height, 800x600).
- hsync range (31-49 Khz)
- vsync range (48-80 hz)
i do know that is possible to contruct such timings
because the monitor specs in windows xp are stored
in /windows/inf/monitor.inf and contains only that
variables. Please any detailed response in how can
they construct their timings with just this variables
and how can i use it with fbdevs from userspace in 2.6?
thanks in advance,
-solca
PS. i know 2 questions is a bad habit :) but here goes
the other: how can i access fbdev features like
acceleration from userspace? or i'm supposed to map
the MMIO registers and do my own voodoo?
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
next reply other threads:[~2003-09-15 7:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-15 7:30 Otto Solares [this message]
2003-09-15 7:43 ` fbdev timings Geert Uytterhoeven
2003-09-16 6:43 ` Otto Solares
2003-09-15 16:07 ` Kronos
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=20030915073029.GA13799@guug.org \
--to=solca@guug.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/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).