Ian,
On 2002.05.15 21:39 Ian Molton wrote:
> ...
>
> Here are some things I think should be worked on:
>
> 1) I *NEED* info about what cards have what features supported by DRI,
> like the radeon driver does already.
I think that more important than raw data is to establish a easily
parsable format for that (either XML, or plain comma-seperated-values) and
a template for the property sheet so that it can be easily maintained.
Once this is done is just a matter of giving it to the devlopers or
issuing a RFC for each card to everyone fill in the holes.
> 2) Can someone rehash the voodoo5 glide compilation guide to be a
> generic voodoo guide please? I KNOW its a very trivial difference to the
> configure line, but I no longer have a voodoo3 and so dont know the
> change.
>
> 3) Can people help me compile a list of janitorial tasks that could be
> undertaken by new developers? perhaps installation cleanups, or trivial
> driver tidyups ?
I don't think that we should frustrate the potential new developers
expecations with janitorial tasks.
I'm of the opinion that if one can code then one should do it. The
janitorial tasks should be taken by users that want to aliviate the
developers load so that they code more.
I think that the two most rewarding things that a potential developer can
do is enhance the documentation and/or bugfixing. Both these tasks
contribute to quickly generate the required know-how to start working on
missing features. They give you better understanding of the architecture
and the code.
I can be more specific:
* Documentation:
- update the existing documents
- change the code comments to Doxygen so that we can automatically
generate reference manuals of the subsystems and the drivers.
- add more items to the Developers' FAQ
* Bugfixing:
- Basically pick a bug on the card of one's choice and hunt it down!
> 4) Can people who have information about the intimate details of card
> HARDWARE (eg. register locations, DMA engines, etc.) please send me
> them, so that I can add them to the developer documents?
Mike Harris posted recentely a link with this information for 3DFX, but
this a rare exception. Most of the documents that the current developers
have are under NDA (see
http://dri.sourceforge.net/doc/faq/getting-started.html#NDA).
>
> 5) Can someone with a nice package re-draw the DRI flowcharts? the
> Precision Insight ones look like Fischer Price 'my first flowchart'...
>
I kinda link their style... ;p
> 6) What is required in order to produce drivers for other architectures
> - If people tell me this, I will add it to the 'help us' section of the
> site. Perhaps someone could set up a mailbox that people wanting
> support for other architectures could send messages to, so that demand
> can be guaged.
>
> So, lets get to it :)
>
Good luck,
José Fonseca
_______________________________________________________________
Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: [EMAIL PROTECTED]
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
