Hi all,
As you probably know the code from r300.sf.net got merged into main Mesa
and DRM trees.
This is great, but it looks like everyone thinks they should check in
only the "perfect" patches. This won't work as few people (if any) can
spend days focused on the same issue.
Me being a prime example - I can spend half hour in the evening on a
problem I know how to solve, but I was not able to do anything more
thorough for at least a few months.
So, it is ok to post the following patches:
* do you know a place in the driver that is broken, but you
don't know how to fix offhand ? Please, submit a WARN_ONCE
patch that has a WARN_ONCE() statement and a comment explain
what is broken
* do you know an application that does not work properly and which
feature is broken ? Please, let us know.
* Can you get PCI-Express cards to do a tiny bit more (like get
2d working) than they do now - patch is fine.
* Feel shaky about a patch ? Make it easy to remove it afterwards
and switch it on/off during compile time.
* Think there is a better implementation of a function ?
Make another version so people can switch from one to another
and report results.
Well, you get the idea - there is still much fun to be had with this
driver :)
best
Vladimir Dergachev
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
--
_______________________________________________
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel
