On Tue, 3 Oct 2000, Michael Schmitz wrote:
quoted
quoted
Fine, but how would I do that? And how do I tell atyfb to set up two
framebuffers for the two separate screens`?
By adding code to atyfb. Sorry for the short answer ;-)
Har har. I almost guessed that. Once I figure out how to initialize the
chip to use separate chunks of RAM for the two ports, the little hack to
make atyfb parse multiple vmode arguments (and consequently set up
and register multiple framebuffers) would indeed be trivial.
Do you have any idea if the config registers dumped to the console by
atyfb are all I need to look at?
They're not sufficient. They're relevant for clock and bus programming only.
A second CRTC is certainly not covered by them.
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/