On 2002.04.25 23:22 Thomas Winischhofer wrote: > Keith Whitwell wrote: > >... > > > > It should be fairly easy to examine the differences in interfaces and > > make only the minimal set of changes. There isn't *that* huge of a > > difference. > > I will take a look. Is there a document on these differences somewhere?
Take a look in the forwarded message below. Just an extra note: where you read Mesa 3.x you should really read 3.4.x, since the big change was from 3.4.x (stable) to 3.5.x (devel). IMHO you should be able to port the SiS driver without looking into the specs - I don't remember to look at them when coding during the Mach64 port -, but you may get a hard time debugging it without them. Nevertheless I'm sure that you find the alternative worst! Regards, José Fonseca ----- Begin Forwarded Message ----- Date: 2002.04.11 09:53 Subject: Re: [Dri-devel] Re: Porting guide From: José Fonseca <[EMAIL PROTECTED]> To: graeme fisher <[EMAIL PROTECTED]> CC: [EMAIL PROTECTED] On 2002.04.11 07:40 graeme fisher wrote: > Hi, > > Does anyone know if there is a detailed porting guide for porting a > graphics driver using Mesa 3.x to one using Mesa 4.x. > Is not really a porting guide but by comparing the following notes you get a good picture: http://dri.sourceforge.net/doc/faq/architecture.html#MESA-INTERNALS http://dri.sourceforge.net/doc/faq/architecture.html#MESA-4X-INTERNALS > Also, roughly how much time would it take to do the port? The mach64 branch was recently ported to Mesa 4.x. There were two people working on this. I would say the bulk of the work was roughly done in 7 days/men. The best thing to do is to use a driver that has been ported as a comparison term. In the mach64 was used the r128. For each file of the driver I was working on I always had two xxdiff windows open: one comparing r128 3.x driver to the r128 4.x open, and other comparing the r128 3.x driver to the mach64 3.x driver. The steps were basically the following: 1. merge the mesa 4.x code 2. get everything to compile without missing headers problems 3. update the context strucutures 3. start by the easiest files, i.e., those that require less changes (this way you already accumulated know-how when you get to the hard ones). 4. get everything to compile without errors 5. get everything to link without missing symbols Then the r128 4.x driver was compared to the mach64 4.x driver to search for unexplainable differences. After this is a matter of debugging, which took much more time than this. > > Thanks > Graeme > Regards, José Fonseca _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
