On Sun, Mar 02, 2003 at 02:38:09AM +0000, Ian Molton wrote:
> On Sat, 1 Mar 2003 15:11:06 -0800 (PST)
> Linus Torvalds <[EMAIL PROTECTED]> wrote:
> 
> No, if that was all, it wouldnt be so bad...
> 
> The project has no real documentation, theres no support from
> anywhere, and there is little help from hardware manufacturers. Even
> where there is, it doesnt encourage people to join in.

What a bunch of lies!!! Have you ever been in
http://dri.sourceforge.net/doc/ !? We have weekly meetings in IRC!

You want encouragement from hardware manufacturers!? It's obvious that
you need encouragement, but don't blame anybody except yourself.

> With DRI you need to 'prove' you have manly balls by blindly fixing
> something without any documentation. only then will you stand any
> chance of ever seeing any documentation.
> 
> To me, thats arse backwards. It should be that the documentation eases
> people into develpoing the code. not the other way round.

But there *are* specs for the Voodoo 3, so what are you complaining
about!? I'm sorry to give such breaking news, but things just _don't_
appear by themselves. Not a DRI driver, not documentation, ...
*nothing*.


I agree that documentation is important and there is alot that can be
done in that field, but then why don't developers-wanna-be, instead of
whinning about lack of documentation, don't do something about it?

When I first started with DRI and Linux (about 1.5 yrs ago) I made an
huge effort to analyize about ~3 yrs worth of mails archives of two
mailing lists (dri-devel and utah-glx-dev) and all the old
documentation, but it was worth it. I've got a much better understanding
of the architecture and the outcome was the "DRI Developer's FAQ" that
you can read at http://dri.sourceforge.net/doc/faq/ which has all the
guidelines on how to get started with DRI.  Funny coincidence, the idea
was given by a guy also whining about documentation, but it took
somebody to atually do it.

BTW, Doxygen documentation for a subset of the radeon driver, the core
of Mesa, the full DRM are in the forge - under the embedded Mesa
umbrella.


Note that documentation only helps until a certain point. No matter how
much documented the existing code base is, it will still be _hard_ to
write a driver from ground up, as it take alot of lines of code, and the
proporcional debugging time.


José Fonseca
__________________________________________________
Do You Yahoo!?
Everything you'll ever need on one web page
from News and Sport to Email and Music Charts
http://uk.my.yahoo.com


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel

Reply via email to