* fbdev timings
@ 2003-09-15 7:30 Otto Solares
2003-09-15 7:43 ` Geert Uytterhoeven
2003-09-15 16:07 ` Kronos
0 siblings, 2 replies; 4+ messages in thread
From: Otto Solares @ 2003-09-15 7:30 UTC (permalink / raw)
To: fb-devel
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
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: fbdev timings
2003-09-15 7:30 fbdev timings Otto Solares
@ 2003-09-15 7:43 ` Geert Uytterhoeven
2003-09-16 6:43 ` Otto Solares
2003-09-15 16:07 ` Kronos
1 sibling, 1 reply; 4+ messages in thread
From: Geert Uytterhoeven @ 2003-09-15 7:43 UTC (permalink / raw)
To: Otto Solares; +Cc: fb-devel
On Mon, 15 Sep 2003, Otto Solares wrote:
> 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?
Clear the FB_ACCELF_TEXT bit in fb_var_screeninfo.accel_flags, mmap the MMIO
registers and do your own voodoo.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: fbdev timings
2003-09-15 7:30 fbdev timings Otto Solares
2003-09-15 7:43 ` Geert Uytterhoeven
@ 2003-09-15 16:07 ` Kronos
1 sibling, 0 replies; 4+ messages in thread
From: Kronos @ 2003-09-15 16:07 UTC (permalink / raw)
To: Otto Solares; +Cc: fb-devel
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
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: fbdev timings
2003-09-15 7:43 ` Geert Uytterhoeven
@ 2003-09-16 6:43 ` Otto Solares
0 siblings, 0 replies; 4+ messages in thread
From: Otto Solares @ 2003-09-16 6:43 UTC (permalink / raw)
To: Geert Uytterhoeven; +Cc: fb-devel
On Mon, Sep 15, 2003 at 09:43:54AM +0200, Geert Uytterhoeven wrote:
> On Mon, 15 Sep 2003, Otto Solares wrote:
> > 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?
>
> Clear the FB_ACCELF_TEXT bit in fb_var_screeninfo.accel_flags, mmap the MMIO
> registers and do your own voodoo.
Ok, thank you.
-solca
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2003-09-16 6:44 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2003-09-15 7:30 fbdev timings Otto Solares
2003-09-15 7:43 ` Geert Uytterhoeven
2003-09-16 6:43 ` Otto Solares
2003-09-15 16:07 ` Kronos
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).