Hi,
this patch add's the PCI id for the Pineview GM integrated graphics controller.
Signed-off-by: Rene Bolldorf
---
src/gallium/drivers/i915/i915_reg.h|1 +
src/gallium/drivers/i915/i915_screen.c |1 +
2 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/src/gallium/drive
"C. Comren" writes:
> Unasked for events from GLX are bugging me. It was fixed in
>
> http://cgit.freedesktop.org/mesa/mesa/commit/?id=f8d81c31cee30821da3aab331a57
> f484f6a07a5d
>
> However, this commit seems to be missing from 7.8.3
> Is this correct?
It cherry-picks fine and builds in the co
https://bugs.freedesktop.org/show_bug.cgi?id=30195
Summary: drmRadeonCmdBuffer: -22. Kernel failed to parse or
rejected command streamS
Product: Mesa
Version: git
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Sta
I'm made the first 7.8.3 release candidate.
Tarballs are available at ftp://ftp.freedesktop.org/pub/mesa/beta/
md5sums:
7e64c3ab4d232b9c24c8de8b6b5c5d51 MesaLib-7.8.3-rc1.tar.gz
ba1366a2c18c01ef468b6469b7c88609 MesaLib-7.8.3-rc1.tar.bz2
22315e2ea843928d0d73ba98679595b1 MesaLib-7.8.3-rc1.zip
On Tue, Sep 14, 2010 at 6:02 PM, Ian Romanick wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Ian Romanick wrote:
>> Ian Romanick wrote:
>>> Ian Romanick wrote:
So... what are our collective criteria for a 7.9 release to happen?
>>> Paraphrasing the discussion a bit, it sounds li
On Wed, Sep 15, 2010 at 12:36 AM, Matt Turner wrote:
> wrt:
> http://cgit.freedesktop.org/mesa/mesa/commit/?id=ccb5e65bc972e0065c0b71cdf0d2feecb6cc95ab
>
> This looks like a prime candidate to go in the 7.9 branch. Please make
> sure your fixes go in 7.9 if applicable.
Acked-by: Jakob Bornecrant
wrt:
http://cgit.freedesktop.org/mesa/mesa/commit/?id=ccb5e65bc972e0065c0b71cdf0d2feecb6cc95ab
This looks like a prime candidate to go in the 7.9 branch. Please make
sure your fixes go in 7.9 if applicable.
Thanks!
Matt
___
mesa-dev mailing list
mesa-d
https://bugs.freedesktop.org/show_bug.cgi?id=26123
Pavel Rojtberg changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|
https://bugs.freedesktop.org/show_bug.cgi?id=30192
Summary: Doom3-demo segfaults since glsl2 branch merged.
Product: Mesa
Version: git
Platform: x86 (IA32)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priori
https://bugs.freedesktop.org/show_bug.cgi?id=30124
Vinson Lee changed:
What|Removed |Added
Depends on||29626
--
Configure bugmail: https://bugs.f
https://bugs.freedesktop.org/show_bug.cgi?id=30124
Vinson Lee changed:
What|Removed |Added
Depends on||29774
--
Configure bugmail: https://bugs.f
https://bugs.freedesktop.org/show_bug.cgi?id=30124
Vinson Lee changed:
What|Removed |Added
Depends on||30190
--
Configure bugmail: https://bugs.f
https://bugs.freedesktop.org/show_bug.cgi?id=26123
--- Comment #6 from Marek Olšák 2010-09-14 11:26:01 PDT ---
Pavel, could you please test latest Mesa master?
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are
https://bugs.freedesktop.org/show_bug.cgi?id=30172
--- Comment #11 from Michel Dänzer 2010-09-14 10:13:08 PDT
---
(In reply to comment #10)
> glXGetProcAddress, according to the docs, shouldn't be used any more. They
> recommend using glXGetProcAddressARB instead. Just FYI.
The Mesa libGL suppo
https://bugs.freedesktop.org/show_bug.cgi?id=30172
--- Comment #10 from Alex Buell 2010-09-14 09:48:51
PDT ---
glXGetProcAddress, according to the docs, shouldn't be used any more. They
recommend using glXGetProcAddressARB instead. Just FYI.
--
Configure bugmail: https://bugs.freedesktop.org/u
https://bugs.freedesktop.org/show_bug.cgi?id=30172
--- Comment #9 from Alex Buell 2010-09-14 09:44:41
PDT ---
I just looked at the docs. The docs says th
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the
2010/9/14 Chia-I Wu :
> 2010/9/14 Kristian Høgsberg :
>> 2010/9/14 Chia-I Wu :
>>> 2010/9/14 Kristian Høgsberg :
2010/9/13 keith whitwell :
> Hey Kristian,
>
> The first question is whether this is necessary - from vague memory I
> have an idea that current attributes need not
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ian Romanick wrote:
> Ian Romanick wrote:
>> Ian Romanick wrote:
>>> So... what are our collective criteria for a 7.9 release to happen?
>> Paraphrasing the discussion a bit, it sounds like the only thing in the
>> way of a release is fixing a bunch of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Luca Barbieri wrote:
>> Yes. Returning 0.5 is wrong. I don't think HLSL has noise, so there
>> shouldn't be a compatibility issue there.
>
> Yes, in fact, nothing seems to use the NOISE opcodes at all.
> Also, I can't find evidence of any hardware e
On Tue, 2010-09-14 at 08:18 -0700, Chia-I Wu wrote:
> 2010/9/14 Kristian Høgsberg :
> > 2010/9/14 Chia-I Wu :
> >> 2010/9/14 Kristian Høgsberg :
> >>> 2010/9/13 keith whitwell :
> Hey Kristian,
>
> The first question is whether this is necessary - from vague memory I
> have an i
Added a commit to update to the new glext.h and solve a minor issue
caused by that.
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev
On 09/14/2010 09:10 AM, Luca Barbieri wrote:
+#ifndef GL_CONTEXT_FLAG_ROBUST_ACCESS_BIT_ARB
+#define GL_CONTEXT_FLAG_ROBUST_ACCESS_BIT_ARB 0x0004
+#endif
+
This part of the patch should go into glheader.h
Actually, I think the correct solution is to update glext.h from
version 61 to versi
2010/9/14 Kristian Høgsberg :
> 2010/9/14 Chia-I Wu :
>> 2010/9/14 Kristian Høgsberg :
>>> 2010/9/13 keith whitwell :
Hey Kristian,
The first question is whether this is necessary - from vague memory I
have an idea that current attributes need not be updated by vertex
buffe
>> +#ifndef GL_CONTEXT_FLAG_ROBUST_ACCESS_BIT_ARB
>> +#define GL_CONTEXT_FLAG_ROBUST_ACCESS_BIT_ARB 0x0004
>> +#endif
>> +
>
> This part of the patch should go into glheader.h
Actually, I think the correct solution is to update glext.h from
version 61 to version 64, which has it (it's core in
On 09/13/2010 07:00 PM, Ian Romanick wrote:
Module: Mesa
Branch: master
Commit: 2cdbced10d98214616bcc5f960b21185c433d23b
URL:
http://cgit.freedesktop.org/mesa/mesa/commit/?id=2cdbced10d98214616bcc5f960b21185c433d23b
Author: Luca Barbieri
Date: Tue Sep 7 17:03:43 2010 +0200
loop_unroll: u
On 09/13/2010 08:30 PM, Luca Barbieri wrote:
Module: Mesa
Branch: shader-work
Commit: 1c6de307bb73b492274aeba303fb69160df69514
URL:
http://cgit.freedesktop.org/mesa/mesa/commit/?id=1c6de307bb73b492274aeba303fb69160df69514
Author: Luca Barbieri
Date: Wed Sep 8 06:24:10 2010 +0200
mesa: ad
2010/9/14 Chia-I Wu :
> 2010/9/14 Kristian Høgsberg :
>> 2010/9/13 keith whitwell :
>>> Hey Kristian,
>>>
>>> The first question is whether this is necessary - from vague memory I
>>> have an idea that current attributes need not be updated by vertex
>>> buffer rendering - ie. it's optional/impleme
https://bugs.freedesktop.org/show_bug.cgi?id=30172
--- Comment #8 from Alex Buell 2010-09-14 07:14:20
PDT ---
But ATI & NVidia exports it.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for th
https://bugs.freedesktop.org/show_bug.cgi?id=30172
Michel Dänzer changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
https://bugs.freedesktop.org/show_bug.cgi?id=30172
--- Comment #6 from Luca Barbieri 2010-09-14 01:40:21
PDT ---
Actually, both ATI and nVidia export it, so perhaps we should too, so that
applications written for those drivers work on Mesa.
--
Configure bugmail: https://bugs.freedesktop.org/us
https://bugs.freedesktop.org/show_bug.cgi?id=30172
--- Comment #5 from Marek Olšák 2010-09-14 01:35:29 PDT ---
I believe glxGetProcAddress is the right way to obtain the function pointer to
glBlitFramebufferEXT, not through static linking.
--
Configure bugmail: https://bugs.freedesktop.org/user
https://bugs.freedesktop.org/show_bug.cgi?id=30172
Luca Barbieri changed:
What|Removed |Added
Severity|enhancement |normal
Component|Drivers/DRI/no
>
> Yes, in fact, nothing seems to use the NOISE opcodes at all.
> Also, I can't find evidence of any hardware ever having implemented it.
> AMD IL has Perlin noise opcodes, but it looks like they are lowered to
> normal instructions since the ISA docs don't say anything about it.
>
FWIW, HLSL in
> Yes. Returning 0.5 is wrong. I don't think HLSL has noise, so there
> shouldn't be a compatibility issue there.
Yes, in fact, nothing seems to use the NOISE opcodes at all.
Also, I can't find evidence of any hardware ever having implemented it.
AMD IL has Perlin noise opcodes, but it looks lik
2010/9/14 Kristian Høgsberg :
> 2010/9/13 keith whitwell :
>> Hey Kristian,
>>
>> The first question is whether this is necessary - from vague memory I
>> have an idea that current attributes need not be updated by vertex
>> buffer rendering - ie. it's optional/implementation-dependent.
>>
>> I ass
35 matches
Mail list logo
