Re: fbdev timings

[Kronos <kronos@kronoz.cjb.net>]

Il Mon, Sep 15, 2003 at 01:30:29AM -0600, Otto Solares ha scritto: 
> 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 :)

Userspace can access edid block via sysfs and can do its own parsing.

> 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)

You can use vesa_modes (in modedb.c) or you can use fb_get_mode (see
fbmon.c).

> 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?

You can get  the whole var usign ioctls. Also, once  the class_dev stuff
is in place  (I'll send patches in few minutes)  every driver can export
its own stuff via sysfs.

Luca
-- 
Reply-To: kronos@kronoz.cjb.net
Home: http://kronoz.cjb.net
Non capisco tutta questa eccitazione per il Multitasking: 
io sono anni che leggo in bagno.


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf