On Fri, 15 Dec 2006, Michael Schmitz wrote:
Indeed, you want to replace TAG_*RES by the actual pixel clock values.
And I sure wish I knew these :-) Same for the detailed timings. What do I
need to provide in the driver so fbset can report these data?
Didn't the video modes in the old atafb have correct timings?
We never had a modedb in the old code. The timing is hardcoded in the
driver from all I can see. I was under the impression the fbcon code needs
to have the modedb entry for some purpose; atafb sure can do without
otherwise.
But at least the various old *_encode_bar() routines filled in the values, so
you can use these for your modedb array.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@xxxxxxxxxxxxxx
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
-
To unsubscribe from this list: send the line "unsubscribe linux-m68k" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
