[Openchrome-devel] KMS, TTM/GEM status

[James Simmons]

> Hi James,
> 
> I see you have continued your work on KMS and TTM/GEM support for the via DRM
> driver.  Thank you for your efforts to move things forward.

Thank you for trying this code out.

> I am wondering what the current status of this work is.  Do you foresee the KMS
> and TTM/GEM support being merged into mainline anytime soon?

	Going mainline will not be for a while. The main line driver has 
been in a state of decay for some time. The driver we work on is currently 
growing since it attempts covers several generations of VIA hardware. So 
alot of work needs to be done.
	KMS is being implemented but it's currently turned off by default. 
Unfortunely turning on KMS gives you the black screen of death. PLL needs 
to be programmed as well as the display fifo. TTM is mostly implemented. 
Fencing needs to be done. I plan to finish the TTM layer soon and start 
working on the xorg driver to use this layer.

> Also, does your work tie into Thomas Hellstr?m's work on the openchrome Mesa
> driver?  Do you have any idea what the status of that work is?

Last I seen the work has been stopped for some time. Currently no Mesa 
work is being done on my end. As for Thomas drm kernel driver I would say 
both our drivers are on the same level. The one difference is I have 
attempted to maintain the old VIA driver ioctl apis as well as support new 
TTM functionality at the same time. 

> Finally, is there anything I can do to help?  I have hardware to test with (a
> VB8002 and EX15000G).

Testers always welcomed. I have been discussing with other developers 
about doing week updates for this project. Also a lack of documenation in 
the drm api is a issue. 

P.S
	I will be giving a talk about openchrome/drm driver writing at the 
linux southeast fest (http://www.southeastlinuxfest.org) this June 11. I 
hope to post a link to the talk. This will give some background for people 
that want to help kernel drm debugging or development.