On Thu, 2004-02-12 at 18:09, Ian Romanick wrote:
> I'd go the other way around. *If* all that GATOS needed to modify (to
> add their new functionality) was in the 2D driver, take a current DRI
> CVS and merge in the changes from
> programs/Xserver/hw/xfree86/drivers/ati (the 2D driver) that are
> relevant to the added GATOS functionality. *EVERYTHING* else should
> come from the DRI tree.
OK that's my ultimate goal... there remains the problem of isolating the
Gatos functionality. I have a feeling fishing through the CVS web
interface isn't going to cut it. I have no idea what kind of changes I'm
looking for.
I did my best at a first hack-whack at it, but radeon_driver.c was so
drastically changed I couldn't tell what the hell was going on. I need
to divide and conquer somewhere. Any suggestions on where the fault
lines might be?
It seems it might be simplest to update Gatos to the latest DRI CVS
because it's a logically straightforward update; ie the changes I need
to make are already reflected elsewhere, and there should be something
similar getting added for everything that's getting removed.
I. From there it would be as easy as using diff -ruN to find out
what the Gatos changes really were, and then I could read the
changes and figure out a graceful way to integrate them.
Any suggestions on how to proceed are most welcome!
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
--
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
