--- Goyo Roth <[EMAIL PROTECTED]> wrote:
Quoting Alex Deucher <[EMAIL PROTECTED]>:
<snip>
On that note, I am interested in getting involved in DRI development. I've been trying to read through all the recommended documents for new developers from the DRI site. I haven't finished all of them. I have good C and Linux skills. I would like to become involved. Work on radeon drivers would probably be easiest as it's the card I currently use (Radeon 8500) Any suggestions for getting my feet wet?
probably the easiest thing to get started with is to try and add a
small feature or bug to add/fix. something you are interested in. then hack on that for a bit. the 2D side is, IMHO, a lot easier to
understand than the 3D side. one you look through the code a few times
and try some things you will start to understand how it all fits
together. it really helps, for me anyway, to see how the output is
affected when I make a particular change. Some ideas that come to
mind:
- add support for 3D windows larger than 2048x2048 on radeon/r200 (see 2048 thread on dri-devel archives)
- bug in radeon/r200 with lesson 24 and glxgears (see dri-devel archives from last few days, also monday's IRC log)
- lockups with certain screensavers
- any dri bugs in bugzilla (http://bugs.xfree86.org)
- finish up mach64, cle266, or virge DRI drivers
- help Felix and Maximo with the savage DRI driver
- help Eric with the old sis DRI driver
- help Ian with hw indirect rendering and the new GLX interface
The problem is that most of these are *not* newbie jobs. A couple of those have even those of us with the most experience scratching our heads. :)
- add new extensions (http://dri.sourceforge.net/cgi-bin/moin.cgi/ToDo)
For someone with access to either R100 or R200 based hardware, adding support for ARB_texture_env_crossbar would be a good starting point. It's a fairly simple (but useful!) extension, and only requires modifications to one small part of the driver. Start looking in r200UpdateTextureEnv / radeonUpdateTextureEnv. I could have sworn that both drivers already supported that extension, but I guess not.
There are a few cards listed on the WiKi for that extension that can't support it. The Rage128 and i810 can only source texture data for a given texture unit from that unit's texture. ARB_texture_env_crossbar allows you to source data from any texture on any unit (basically). This is *different* from the output of a texture unit.
A different extension, ATIX_texture_env_route, provides that functionality. That specification isn't in the registry, but it is (or at least used to be) published on ATI's developer website. In addition to ARB_texture_env_crossbar and texture unit output routine, ATIX_texture_env_route lets you use secondary-color / fog value as inputs to the texture combiner. I think that i830 hardware could also support that. I wonder if ATI would let us implement that extension...
The next most important one for R100 / R200 is EXT_fog_coord. To do that we need to add support for fp4 secondary-color. The fog coordinate is stored as the alpha value of the secondary-color. Perhaps Keith could offer some pointers on what needs to be done for that.
One that is missing from the list is EXT_blend_func_separate / INGR_blend_func_separate for R200. I think we need access to some additional register documentation first. :(
------------------------------------------------------- This SF.net email is sponsored by OSDN's Audience Survey. Help shape OSDN's sites and tell us what you think. Take this five minute survey and you could win a $250 Gift Certificate. http://www.wrgsurveys.com/2003/osdntech03.php?site=8 _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
