[Openchrome-devel] KMS, TTM/GEM status

Forest Bond forest
Mon Jun 6 18:38:43 PDT 2011

Hi James,

On Sat, Jun 04, 2011 at 02:01:55AM +0100, James Simmons wrote:
> > 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 haven't actually tried it yet. ;)

> > 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.

I am glad you are continuing to make progress.  Thank you for your work!

> > 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. 

Okay.  Sounds like it will be a long while before we can expect any improvements
in Mesa support.

> > 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. 

Feel free to get in touch if you have anything in particular you'd like tested.
Right now it is not very clear to me what features would be helpful for me to

> 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.

Great, I look forward to it.

Forest Bond
rapidrollout.com / alittletooquiet.net / pytagsfs.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
Url : http://wiki.openchrome.org/pipermail/openchrome-devel/attachments/20110607/2782a847/attachment.bin

More information about the Openchrome-devel mailing list