On Tue, Mar 23, 2010 at 00:13, Corbin Simpson <mostawesomed...@gmail.com> wrote:
> On Mon, Mar 22, 2010 at 11:39 PM, Tom Stellard <tstel...@gmail.com> wrote:
>> On Thu, Mar 18, 2010 at 03:25:04PM -0700, Corbin Simpson wrote:
>>>
>>> Nifty. Well, there's a few places to look for information.
>>>
>>> If you're not sure how the actual video card works,
>>> http://www.x.org/wiki/Development/Documentation/HowVideoCardsWork is a
>>> great starting point. Of particular interest is the 3D engine; r300g
>>> only talks to the 3D part of the video card.
>>>
>>> The reference Gallium driver is probably identity, although softpipe
>>> is a good reference as well. We also have documentation for the
>>> Gallium API and associated bits; if you don't want to build it
>>> yourself from the Mesa tree, there should be an up-to-date copy at
>>> http://people.freedesktop.org/~csimpson/gallium-docs/. (If there's a
>>> problem with the documentation, lemme know!)
>>>
>>
>> Thanks for the information.
>>
>> After spending some time learning about the Gallium driver architecture, I
>> think it might be better to set a goal to implement or improve a specific
>> feature of the Gallium R300 driver rather than trying to get a specific
>> game or application to work.  Is there a feature that is currently missing
>> from the R300 driver that might make a good project for the summer?
>
> Good question. There's a handful of things. Passing piglit might be a
> good goal. Bumping the GL version further up, or solidifying the GLSL
> support, might be good too.
>

Keep in mind you have to make SoC projects self-contained and doable
in 3 months by a newcomer. So you have to measure the difficulty
beforehand so you don't hand out trivial/impossible projects. Usually
that requires a developer looking at the source and figuring out the
amount of work required...

Stephane

------------------------------------------------------------------------------
Download Intel&#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Mesa3d-dev mailing list
Mesa3d-dev@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mesa3d-dev

Reply via email to