-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Nicolai Hähnle wrote:
> Am Donnerstag 21 August 2008 17:37:48 schrieb Corbin Simpson:
>> Timo Jyrinki wrote:
>>> 2008/8/21 Nicolai Hähnle <[EMAIL PROTECTED]>:
Huh? The majority of changes to the r300 driver certainly haven't been
backported t
Am Donnerstag 21 August 2008 17:37:48 schrieb Corbin Simpson:
> Timo Jyrinki wrote:
> > 2008/8/21 Nicolai Hähnle <[EMAIL PROTECTED]>:
> >> Huh? The majority of changes to the r300 driver certainly haven't been
> >> backported to the 7.0 branch. Most importantly, support for R5xx
> >> cards...
> >
>
http://bugs.freedesktop.org/show_bug.cgi?id=17218
--- Comment #5 from Henri Verbeet <[EMAIL PROTECTED]> 2008-08-21 08:46:18 PST
---
I'm pretty sure we get that one right, for Wine to use this many uniforms,
GL_MAX_VERTEX_UNIFORM_COMPONENTS_ARB would have to be 4096. That might be
correct if
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Timo Jyrinki wrote:
> 2008/8/21 Nicolai Hähnle <[EMAIL PROTECTED]>:
>> Huh? The majority of changes to the r300 driver certainly haven't been
>> backported to the 7.0 branch. Most importantly, support for R5xx cards...
>
> Ah, ok, if that is so, R500
On Wed, Aug 20, 2008 at 2:20 AM, Brian Paul
<[EMAIL PROTECTED]> wrote:
> Dave Airlie wrote:
>>> On Sun, Aug 17, 2008 at 12:23:06 +0200, Stefan Dirsch wrote:
>>>
Looks like dri_bufmgr.h/intel_bufmgr.h are missing in the
tarball. Could this be?
>>> See my other reply on mesa3d-dev, the
2008/8/21 Nicolai Hähnle <[EMAIL PROTECTED]>:
> Huh? The majority of changes to the r300 driver certainly haven't been
> backported to the 7.0 branch. Most importantly, support for R5xx cards...
Ah, ok, if that is so, R500 support is indeed a big thing.
-Timo
-
Am Donnerstag 21 August 2008 13:12:49 schrieb Timo Jyrinki:
> 2008/8/20 Brian Paul <[EMAIL PROTECTED]>:
> > What I'd probably do then is create a mesa-7.2 branch, based on 7.1,
> > which will be a stable, bug-fix branch without GEM.
> >
> > Then, designate mesa/master as the new-feature / GEM / 7.3
2008/8/20 Brian Paul <[EMAIL PROTECTED]>:
> What I'd probably do then is create a mesa-7.2 branch, based on 7.1,
> which will be a stable, bug-fix branch without GEM.
>
> Then, designate mesa/master as the new-feature / GEM / 7.3 development
> area. I'd also consider merging gallium-0.1 into maste
