There are a few useful prerequisites for contributing to Mesa and
being efficient:
1) Know OpenGL and GLSL
Tutorials: http://ogldev.atspace.co.uk/
You need to know the API one way or another. Eventually, you want to
switch to the official OpenGL, GLSL, and extension specifications as
your primary
On 08.12.2015 15:04, Ilia Mirkin wrote:
> On Tue, Dec 8, 2015 at 8:43 AM, Ernst Sjöstrand wrote:
>> Hello list!
>>
>> I lurk here and try to follow Mesa/DRI and most specifically Radeon
>> driver development, report bugs, test new stuff and help get the bugs
>> closed and so on...
>>
>> However
On 8 December 2015 at 14:22, Christian König
wrote:
> On 08.12.2015 15:04, Ilia Mirkin wrote:
>>
>> On Tue, Dec 8, 2015 at 8:43 AM, Ernst Sjöstrand wrote:
>>>
>>> Hello list!
>>>
>>> I lurk here and try to follow Mesa/DRI and most specifically Radeon
>>> driver development, report bugs, test
Hi Ernst,
On 8 December 2015 at 13:43, Ernst Sjöstrand wrote:
> Hello list!
>
> I lurk here and try to follow Mesa/DRI and most specifically Radeon
> driver development, report bugs, test new stuff and help get the bugs
> closed and so on...
>
> However I see that the commit messages for
Hello list!
I lurk here and try to follow Mesa/DRI and most specifically Radeon
driver development, report bugs, test new stuff and help get the bugs
closed and so on...
However I see that the commit messages for AMD/Radeon are often very
unhelpful. They don't state the motivation behind the
On Tue, Dec 8, 2015 at 8:43 AM, Ernst Sjöstrand wrote:
> Hello list!
>
> I lurk here and try to follow Mesa/DRI and most specifically Radeon
> driver development, report bugs, test new stuff and help get the bugs
> closed and so on...
>
> However I see that the commit messages for AMD/Radeon are
