<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> <HTML> <HEAD> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=gb2312"> <META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7654.12"> <TITLE>´ð¸´: [Xorg-driver-geode] Plans for next releases</TITLE> </HEAD> <BODY>  For debug the driver, the best way it to use GDB. A graphic tool to debug the driver based on GDB is DDD. I always use this great tool to debug the driver. It can check the values of all struct and function values. It is just like debugging a application. Very powerful! For the link you provided, I gave a look at it. He does a great job to port the Glint to KMS. Actually, right now I am porting the open source code to anoterh operating system, I have to port radeon KMS driver too. So I am very familiar with his project describes. You have seen that Alex gave Matt a lot of help when he ports the driver. So do I too right now :). I think for porint the UMS driver to KMS driver, we need to add CRTC, Encoder and Connector support. We need I2C probe to get EDID information. We need use TTM memory manager to use VRAM. We also need to port Fbdev interface. Actually for geode, it is necessary to port it into KMS. The TTM can solve a lot of memory manage work instead of the static method now. And 2D accel will be sooner if we implement in kernel instead of user space. And we can support VGA and DVI connector too in kernel. Actually I am ver interested to such a work. Thanks, Frank -----Original Message----- From: xorg-driver-geode-bounces+frankr.huang=amd.com@lists.x.org 代表 Christian Gmeiner Sent: 2011-4-4 (星期一) 17:25 To: Huang, FrankR Cc: xorg-driver-geode@lists.x.org Subject: Re: [Xorg-driver-geode] Plans for next releases Hi > Geode hardware has limit 2d hw accel capability. When you meet low speed hw accel issue, you should look into code to see which operation will consume more time, then improve that. What is the best way to profile the driver. I have seen there is a GEODE_TRACE_FALL. > For the KMS, few weeks ago, when I developed ATI code, I found it is a huge project, graphics asic initialization and modeset will be done here. And 2D hw accel will be done here. It will need some guys who is familiar with KMS and DDX driver structure to do it. Unfortunately, right now I am still be occupied in ATI driver. If there are some questions about how to split the KMS fro current UMS driver, I am happy to give advice. > I would love to have KMS geode driver, but I have no experience with KMS and DDX. I have only looked at the porting of the GLINT driver to KMS - <A HREF="http://code.google.com/p/google-summer-of-code-2010-xorg/downloads/detail?name=Matt_Turner.tar.gz">http://code.google.com/p/google-summer-of-code-2010-xorg/downloads/detail?name=Matt_Turner.tar.gz</A> If there will be a public git branch etc I will do testing and maybe I can bring in some patches. Thanks -- Christian Gmeiner, MSc _______________________________________________ Xorg-driver-geode mailing list Xorg-driver-geode@lists.x.org <A HREF="http://lists.x.org/mailman/listinfo/xorg-driver-geode">http://lists.x.org/mailman/listinfo/xorg-driver-geode</A> </BODY> </HTML>