Great work Keith.

> What I've done so far is to extend the existing radeon interfaces to accept
> & validate the new state required for the r200, and a couple of other minor
> changes. This is probably the minimal set of changes to get a working r200 
> driver.

It would seem that driver development for the R200 similar to the R100,
considering how quickly this driver came out. Is this correct? 
 
> A large part of this difference is presumably due to HyperZ - something
> that we can't implement in an open driver.
Could you please explain why this is, I'd like to know and I'll add it to the
documentation, I assume the same holds true for the R100.

Do you think a R200_dri_features page (like the one for the R100) would be in
order, would you like one?

Liam
----
it depends


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Gadgets, caffeine, t-shirts, fun stuff.
http://thinkgeek.com/sf
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel

Reply via email to