On Thu, 2004-02-12 at 03:21, Hod McWuff wrote:
> On Wed, 2004-02-11 at 19:03, Michel DÃnzer wrote:
> > On Thu, 2004-02-12 at 00:26, Hod McWuff wrote:
> > > On Wed, 2004-02-11 at 17:28, Michel DÃnzer wrote:
> 
> By the way, is there an index of CVS tags by date? Or should I just try 
> to pull something by a date near when the first Gatos commits were made?

I usually look up this kind of stuff in something like the cvs log
output.


> > > I've found Gatos-related changes in radeon_cp.c, radeon_drv.h, and
> > > radeon_state.c. I've reimplemented what changes I could find... 
> > 
> > They're mostly superfluous AFAICT. Again, the DRM in current DRI CVS
> > should basically work with the GATOS 2D driver, that one just needs to
> > set up things similarly to how the 2D driver in DRI CVS does.
> 
> I see two types of changes; adding dev_priv->fb_offset, 

dev_priv->fb_location is basically the same, and it's already added to
the relevant variables instead of everywhere they're used.

> and doing some bit masking. 

You mean getting the values into shape for the MC_{FB,AGP}_LOCATION
registers? Taking the above into consideration, they're doing the same.

> There's also the spot in radeon_cp where it appears to write a couple of 
> new initializations to the card. You're sure those are superfluous? 

Might not hurt to add those, but the 2D driver needs to set them up
correctly anyway, in particular for when it's not using the DRM.


> > > > The DRM and 3D driver in current DRI CVS should theoretically be able to
> > > > work with their 2D driver. Its aperture setup may have to be changed
> > > > slightly though.
> > > 
> > > The one in 2.6.2 works with 2D (after faking the version number) 
> > 
> > Faking the version number is obviously a bad idea. The GATOS 2D driver
> 
> The Gatos 3D driver won't even try to work unless the DRM version number
> is 1.100.0 or better.

Look, the 1.100.0 was a failed attempt to express the incompatibility,
but it didn't prevent non-GATOS 3D drivers from locking up the machine,
for example.

Again, the cause for the incompatibility has been removed in the 1.10.0
DRM, so it...

> > should work with the 1.10.0 radeon DRM with the changes described above.
> 
> Those changes are exactly what I'm trying to isolate and port to the
> current CVS DRM.

I mean the changes I have been describing for the GATOS 2D driver.


> > > 2.6.2-update.patch merges current DRI CVS into the 2.6.2 tree
> > 
> > BTW, AFAIK the DRM in the -mm kernel tree is already fairly up to date.
> 
> Good to know, but I'm more comfortable hacking against the vanilla tree,
> and it makes no sense to develop a patch against an obsolete version. 

I think it makes no sense to merge stuff with the vanilla tree when
there's more up to date code in the 2.6 maintainer's tree, but maybe
that's just me...


> As an aside though, perhaps a unified source is a good idea.

That's what the DRM in DRI CVS is, unless I misunderstand you.


PS: If you're going to keep posting to dri-devel, please subscribe...
otherwise, I or another list admin have to manually approve your posts.

-- 
Earthling Michel DÃnzer      |     Debian (powerpc), X and DRI developer
Libre software enthusiast    |   http://svcs.affero.net/rm.php?r=daenzer



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

Reply via email to