Sorry for dropping into the fray in the middle but I do have a few questions:
1: What part, if any, of the SPARC fb <-> Xorg ddx setup is open/available in
source form for any fool that might want to try and create console text
and Xorg "drivers" for older graphics hardware such as the m64 series?
2: From my amature vantage point it appears there are 3 parts to getting a
graphics card working with SPARC console/Xorg (Open)Solaris:
1: Kernel driver, efb for example. I assume this does mapping and and
abstracts the hardware to a standard framebuffer framework for the OS.
This also provides the text console services?
2: Frame buffer config utility; i.e. .so for fbconfig to mess with.
3: Xorg ddx .so to hook Xorg to the hardware.
Is there any open code for 1 - 3 or is it all behind an NDA veil?
Is there an historical/(hysterical?) reason why the non-hardware specific
kernel <->framebuffer framework/text console <-> SPARC Xorg ddx
API/interfaces aren't openly documented?
I understand about bit twiddling code for various ATI/AMD/Creative registers
being hush-hush but it seems odd the API's between/in the kernel, FB
framework and /dev/fb <-> Xorg ddx parts would have need to be NDA/hush-hush.
Sorry if there is a FAQ/outline about this but I wasn't able to find one.
Other OS's get the 2D part of the m64 hardware going using generic ati Xorg
code so I'm curious as to why its harder under (Open)Solaris.
Thanks,
-Rob
