RE: [linux-fbdev] Re: macmodes/modedb

2 messages, 2 authors, 2000-05-19 · open the first message on its own page

RE: [linux-fbdev] Re: macmodes/modedb

From: Brad Douglas <hidden>
Date: 2000-05-18 16:54:19

-----Original Message-----
From: Geert Uytterhoeven [mailto:geert@linux-m68k.org]
quoted
What I can think of off hand is adding fb_mac_monitor_sense to fb_ops
(which
quoted
already looks like a less than optimal idea) or possibly depreciating
it.
That's not a very good idea, since it's Mac only.
From the other side, DDC is something similar, so a generic call in fb_ops
may
be the good solution?
This may be a possibility.  Unfortunately, I'm not familiar with the inner
workings of DDC.  If anyone has docs on how this works, I'll take a stab at
adding support to fbdev.
quoted
Another option is to not try and do everything in fb_find_mode().
You cannot do everything in fb_find_mode() since monitor sense is
a per-monitor issue, not global.
As of now, all drivers have a 1:1 relationship with a monitor.  Even the
Matrox G400 driver insmods a second driver for the 2nd head.  Should we
expect this to change?  I do not believe fbdev is capable of initializing
two video cards from a single driver, but I could be wrong -- I have no
ability to test.
One possible thing (in each fbdev driver :-(

    default_mode = NULL;
#ifdef CONFIG_PPC_ALL
    sense = ...;
    default_mode = mac_map_monitor_sense(sense);
#endif
    ... = fb_find_mode(..., default_mode, ...);
I believe this would be acceptable, but we'll have to change
mac_map_monitor_sense() to return fb_videomode instead of VMODE.
fb_find_mode() will be unhappy to get an int when it's expecting
fb_videomode. ;)
Or: should it be considered as a real mode_option (if mode_option == NULL)
instead of a default mode?
Looking at things now, I think the default_mode is the way to go.  "Pushing"
mode_options may make things a little more confusing (well, I guess it's
nothing a little documentation won't clear up).  I still like the fallback
to NVRAM values if there are no boot options or if the boot options fail.

It looks like we have a couple ways to do this.  Suggestions?

Brad Douglas
brad@neruo.com
http://www.linux-fbdev.org

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

RE: [linux-fbdev] Re: macmodes/modedb

From: Geert Uytterhoeven <hidden>
Date: 2000-05-19 06:03:22

On Thu, 18 May 2000, Brad Douglas wrote:
quoted
From: Geert Uytterhoeven [mailto:geert@linux-m68k.org]
quoted
Another option is to not try and do everything in fb_find_mode().
You cannot do everything in fb_find_mode() since monitor sense is
a per-monitor issue, not global.
As of now, all drivers have a 1:1 relationship with a monitor.  Even the
Matrox G400 driver insmods a second driver for the 2nd head.  Should we
expect this to change?  I do not believe fbdev is capable of initializing
two video cards from a single driver, but I could be wrong -- I have no
ability to test.
Yes it is. There are drivers that can handle multiple cards. And you can have
different cards as well.
quoted
One possible thing (in each fbdev driver :-(

    default_mode = NULL;
#ifdef CONFIG_PPC_ALL
    sense = ...;
    default_mode = mac_map_monitor_sense(sense);
#endif
    ... = fb_find_mode(..., default_mode, ...);
I believe this would be acceptable, but we'll have to change
mac_map_monitor_sense() to return fb_videomode instead of VMODE.
fb_find_mode() will be unhappy to get an int when it's expecting
fb_videomode. ;)
Of course.

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


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help