On Tue, May 26, 2015 at 1:10 AM, Pierre Moreau wrote:
>> On 26 May 2015, at 00:39, Ilia Mirkin wrote:
>>
>>> On Mon, May 25, 2015 at 6:22 PM, Pierre Moreau
>>> wrote:
>>> Most _DSM will return an integer value of 0x8002 when given an unknown
>>> UUID, revision ID or function ID. Checking lo
> On 26 May 2015, at 00:39, Ilia Mirkin wrote:
>
>> On Mon, May 25, 2015 at 6:22 PM, Pierre Moreau wrote:
>> Most _DSM will return an integer value of 0x8002 when given an unknown
>> UUID, revision ID or function ID. Checking locally allows us to differentiate
>> that case from other ACP
The problem is that the EDGEFLAG has to be toggled at vertex submission
time. This can be done from either the draw or the regular paths. Avoid
falling back to draw just because there's an edgeflag.
Signed-off-by: Ilia Mirkin
Cc: "10.5 10.6"
---
src/gallium/drivers/nouveau/nv30/nvfx_vertprog.c
These are only used once per draw, so it makes sense to keep them in
GART. Also take this opportunity to modernize the buffer mapping API
usage.
Signed-off-by: Ilia Mirkin
Cc: "10.5 10.6"
---
src/gallium/drivers/nouveau/nv30/nv30_draw.c | 16 ++--
1 file changed, 10 insertions(+), 6
Instead of always having it in the data, let the bo placement decide it.
This fixes glxgears with swtnl forced on.
Signed-off-by: Ilia Mirkin
Cc: "10.5 10.6"
---
src/gallium/drivers/nouveau/nv30/nv30_draw.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/src/gallium/dr
Commit 8acaf862dfe switched things over to use TEXCOORD instead of
GENERIC, but did not update the nv30 swtnl draw paths. This teaches the
draw logic about TEXCOORD.
Among other things, this fixes a crash in demos/arbocclude when using
swtnl. Curiously enough, the point-sprite piglit works without
On Mon, May 25, 2015 at 8:55 PM, Tobias Klausmann
wrote:
>
>
> On 26.05.2015 02:49, Ilia Mirkin wrote:
>>
>> On Mon, May 25, 2015 at 8:37 PM, Tobias Klausmann
>> wrote:
>>>
>>>
>>> On 25.05.2015 21:29, Ilia Mirkin wrote:
Commit 8acaf862dfe switched things over to use TEXCOORD instead of
On 26.05.2015 02:49, Ilia Mirkin wrote:
On Mon, May 25, 2015 at 8:37 PM, Tobias Klausmann
wrote:
On 25.05.2015 21:29, Ilia Mirkin wrote:
Commit 8acaf862dfe switched things over to use TEXCOORD instead of
GENERIC, but did not update the nv30 swtnl draw paths. This teaches the
draw logic abou
On Mon, May 25, 2015 at 8:37 PM, Tobias Klausmann
wrote:
>
>
> On 25.05.2015 21:29, Ilia Mirkin wrote:
>>
>> Commit 8acaf862dfe switched things over to use TEXCOORD instead of
>> GENERIC, but did not update the nv30 swtnl draw paths. This teaches the
>> draw logic about TEXCOORD.
>>
>> Among other
On 25.05.2015 21:29, Ilia Mirkin wrote:
This makes the vertex buffer go to GART, not VRAM, and redoes the
mapping to not use the UNSYNCHRONIZED access (which is meaningless on a
VRAM buffer anyways). While we're at it, add some flushes for VBO data.
Moving the vertex buffer from VRAM to GART m
On 25.05.2015 21:29, Ilia Mirkin wrote:
Commit 8acaf862dfe switched things over to use TEXCOORD instead of
GENERIC, but did not update the nv30 swtnl draw paths. This teaches the
draw logic about TEXCOORD.
Among other things, this fixes a crash in demos/arbocclude when using
swtnl. Curiously e
On Mon, May 25, 2015 at 6:22 PM, Pierre Moreau wrote:
> Most _DSM will return an integer value of 0x8002 when given an unknown
> UUID, revision ID or function ID. Checking locally allows us to differentiate
> that case from other ACPI errors, and to not report a "failed to evaluate
> _DSM"
>
Signed-off-by: Pierre Moreau
---
drm/nouveau/nouveau_acpi.c | 14 +++---
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/drm/nouveau/nouveau_acpi.c b/drm/nouveau/nouveau_acpi.c
index 3d6a1ea..5d63621 100644
--- a/drm/nouveau/nouveau_acpi.c
+++ b/drm/nouveau/nouveau_acpi.c
@@
Signed-off-by: Pierre Moreau
---
drm/nouveau/nouveau_acpi.c | 8
drm/nouveau/nouveau_vga.c | 4 ++--
2 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/drm/nouveau/nouveau_acpi.c b/drm/nouveau/nouveau_acpi.c
index 7aeaf7d..104d291 100644
--- a/drm/nouveau/nouveau_acpi.c
+++
Most _DSM will return an integer value of 0x8002 when given an unknown
UUID, revision ID or function ID. Checking locally allows us to differentiate
that case from other ACPI errors, and to not report a "failed to evaluate _DSM"
if 0x8002 is returned which was confusing.
Signed-off-by: Pie
Signed-off-by: Pierre Moreau
---
drm/nouveau/nouveau_acpi.c | 8 +---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git a/drm/nouveau/nouveau_acpi.c b/drm/nouveau/nouveau_acpi.c
index 1f18018..36f4a40 100644
--- a/drm/nouveau/nouveau_acpi.c
+++ b/drm/nouveau/nouveau_acpi.c
@@ -61,11
Signed-off-by: Pierre Moreau
---
drm/nouveau/nouveau_acpi.c | 53 --
drm/nouveau/nouveau_acpi.h | 2 ++
drm/nouveau/nouveau_drm.c | 6 --
drm/nouveau/nouveau_vga.c | 10 +
4 files changed, 63 insertions(+), 8 deletions(-)
diff --git a/d
Signed-off-by: Pierre Moreau
---
drm/nouveau/nouveau_acpi.c | 10 --
1 file changed, 4 insertions(+), 6 deletions(-)
diff --git a/drm/nouveau/nouveau_acpi.c b/drm/nouveau/nouveau_acpi.c
index 36f4a40..073f7d7 100644
--- a/drm/nouveau/nouveau_acpi.c
+++ b/drm/nouveau/nouveau_acpi.c
@@ -88
This makes it clearer when reading the function name, as well as following the
names of the related ACPI function.
Signed-off-by: Pierre Moreau
---
drm/nouveau/nouveau_acpi.c | 25 ++---
1 file changed, 14 insertions(+), 11 deletions(-)
diff --git a/drm/nouveau/nouveau_acpi.
This is especially true when variables or functions are just called dsm without
precising the v1.
Signed-off-by: Pierre Moreau
---
drm/nouveau/nouveau_acpi.c | 64 +++---
drm/nouveau/nouveau_acpi.h | 4 +--
drm/nouveau/nouveau_drm.c | 4 +--
drm/nouveau
https://bugs.freedesktop.org/show_bug.cgi?id=90632
--- Comment #3 from Willem Mulder <14mrh4x0r+f...@gmail.com> ---
mmiotrace sent to mmio.du...@gmail.com
--
You are receiving this mail because:
You are the assignee for the bug.
___
Nouveau mailing lis
https://bugs.freedesktop.org/show_bug.cgi?id=90632
Ilia Mirkin changed:
What|Removed |Added
Summary|DRI_PRIME=1 has no effect |[NVE6] grctx template
|w
https://bugs.freedesktop.org/show_bug.cgi?id=90632
--- Comment #1 from Willem Mulder <14mrh4x0r+f...@gmail.com> ---
Created attachment 116034
--> https://bugs.freedesktop.org/attachment.cgi?id=116034&action=edit
dmesg output
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=90632
Bug ID: 90632
Summary: DRI_PRIME=1 has no effect with GK106M
Product: xorg
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Sever
https://bugs.freedesktop.org/show_bug.cgi?id=90567
--- Comment #13 from Detlev Casanova ---
I'll get that in place tomorrow.
Note that the first bug could have been reported using 2.4.60, I upgrade
packages almost everyday.
For the rest, this is out of my comprehension scope :) I'll do my best
https://bugs.freedesktop.org/show_bug.cgi?id=90567
--- Comment #12 from Ilia Mirkin ---
OK, well this is phenomenally bad then:
nouveau E[League of Legen[1565]] Unknown handle 0x0017
nouveau E[League of Legen[1565]] validate_init
nouveau E[League of Legen[1565]] validate: -2
And in your ear
https://bugs.freedesktop.org/show_bug.cgi?id=90567
--- Comment #11 from Detlev Casanova ---
No, this is libdrm 2.4.61, the latest version in archlinux.
--
You are receiving this mail because:
You are the assignee for the bug.
___
Nouveau mailing list
https://bugs.freedesktop.org/show_bug.cgi?id=90567
--- Comment #10 from Ilia Mirkin ---
Are you using libdrm 2.4.60? If so, don't. Either use 2.4.59 or 2.4.61.
--
You are receiving this mail because:
You are the assignee for the bug.
___
Nouveau maili
https://bugs.freedesktop.org/show_bug.cgi?id=90567
--- Comment #9 from Detlev Casanova ---
Created attachment 116032
--> https://bugs.freedesktop.org/attachment.cgi?id=116032&action=edit
begining of errors with mesa git and nvc0 shader validation patch
--
You are receiving this mail because:
https://bugs.freedesktop.org/show_bug.cgi?id=90567
--- Comment #8 from Detlev Casanova ---
Unfortunately, the patch did not fix the problem. Though now, I can Alt-Tab to
switch to other windows and even kill the app with Ctrl-Alt-Esc.
I attach the log for the start of the game.
--
You are rece
This makes the vertex buffer go to GART, not VRAM, and redoes the
mapping to not use the UNSYNCHRONIZED access (which is meaningless on a
VRAM buffer anyways). While we're at it, add some flushes for VBO data.
Moving the vertex buffer from VRAM to GART makes glxgears work fully
with NV30_SWTNL=1.
Commit 8acaf862dfe switched things over to use TEXCOORD instead of
GENERIC, but did not update the nv30 swtnl draw paths. This teaches the
draw logic about TEXCOORD.
Among other things, this fixes a crash in demos/arbocclude when using
swtnl. Curiously enough, the point-sprite piglit works without
https://bugs.freedesktop.org/show_bug.cgi?id=90567
--- Comment #7 from Detlev Casanova ---
Mesa git won't solve the issue. I'm trying the patch as soon as possible :)
--
You are receiving this mail because:
You are the assignee for the bug.
___
Nouvea
On 25.05.2015 20:36, Roland Scheidegger wrote:
This doesn't really do what the commit message claims - it just adds a
cap bit, not actual support for arb_cull_distance (which was already
there), so the log should be changed accordingly.
Yep, you are completely right here, will change it to be
This doesn't really do what the commit message claims - it just adds a
cap bit, not actual support for arb_cull_distance (which was already
there), so the log should be changed accordingly.
Apart from what was already mentioned (that is, the cap bit isn't used
by st/mesa which instead mistakenly us
https://bugs.freedesktop.org/show_bug.cgi?id=89558
--- Comment #34 from SMF ---
Created attachment 116031
--> https://bugs.freedesktop.org/attachment.cgi?id=116031&action=edit
kernel 4.1-rc5 nouveau driver with patches applied
For interest tested patches against kernel 4.1-rc5 (with nouveau de
On Mon, May 25, 2015 at 9:40 AM, Tobias Klausmann
wrote:
>
> On 25.05.2015 07:17, Dave Airlie wrote:
>>
>> On 25 May 2015 at 08:11, Marek Olšák wrote:
>>>
>>> It's the same on Radeon. There are 2x ClipOrCullDistance output
>>> vectors and a mask saying it should clip or cull or do nothing.
>>>
>>
https://bugs.freedesktop.org/show_bug.cgi?id=90630
Bug ID: 90630
Summary: random driver crashes mostly after screen lock
Product: xorg
Version: 7.7 (2012.06)
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Signed-off-by: Tobias Klausmann
---
I'm already getting emails wanting me to do this, so just mark it,
wont change anything really
docs/GL3.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/docs/GL3.txt b/docs/GL3.txt
index 44a824b..8e1c8cd 100644
--- a/docs/GL3.txt
+++ b/
On 25.05.2015 07:17, Dave Airlie wrote:
On 25 May 2015 at 08:11, Marek Olšák wrote:
It's the same on Radeon. There are 2x ClipOrCullDistance output
vectors and a mask saying it should clip or cull or do nothing.
Marek
My thinking was gallium should have a single semantic and a mask in
the s
On Mon, 2015-05-25 at 00:46 +0200, Tobias Klausmann wrote:
> hi,
> replay inline.
>
> On 25.05.2015 00:34, Timothy Arceri wrote:
> > On Sun, 2015-05-24 at 19:58 +0200, Tobias Klausmann wrote:
> >> Signed-off-by: Tobias Klausmann
> >> ---
> >> src/glsl/ast_to_hir.cpp | 14 +
> >>
On Sun, 2015-05-24 at 19:58 +0200, Tobias Klausmann wrote:
> Signed-off-by: Tobias Klausmann
> ---
> src/glsl/ast_to_hir.cpp | 14 +
> src/glsl/builtin_variables.cpp | 13 +++-
> src/glsl/glcpp/glcpp-parse.y| 3 +
> src/glsl/glsl_parser_extras.cpp | 1 +
> s
https://bugs.freedesktop.org/show_bug.cgi?id=90567
--- Comment #6 from Samuel Pitoiset ---
Created attachment 116021
--> https://bugs.freedesktop.org/attachment.cgi?id=116021&action=edit
0001-nvc0-prevent-using-unvalidated-vertex-programs.patch
Hello Detlev,
Did you test with mesa git?
In any
https://bugs.freedesktop.org/show_bug.cgi?id=90567
--- Comment #4 from Detlev Casanova ---
Hello, thanks for your response.
The version of mesa was just updated by my distro (archlinux) to version :
OpenGL core profile version string: 3.3 (Core Profile) Mesa 10.5.6
OpenGL version string: 3.0 Me
https://bugs.freedesktop.org/show_bug.cgi?id=90567
--- Comment #5 from Detlev Casanova ---
Created attachment 116019
--> https://bugs.freedesktop.org/attachment.cgi?id=116019&action=edit
Nouveau log from beginning
--
You are receiving this mail because:
You are the assignee for the bug.
_
HI,
I have an old motherboard ...
Base Board Information
Manufacturer: Gigabyte Technology Co., Ltd.
Product Name: M61PME-S2P
Version: x.x
Serial Number:
Processor Information
Socket Designation: Socket M2
Type: Central Processor
Family: Athlon
Manufacturer: AMD
https://bugs.freedesktop.org/show_bug.cgi?id=90626
Bug ID: 90626
Summary: HP ZBook 15 nouveau driver hangup for kernel >= 3.19
Product: xorg
Version: unspecified
Hardware: Other
OS: All
Status: NEW
Severit
https://bugs.freedesktop.org/show_bug.cgi?id=90626
René changed:
What|Removed |Added
Summary|HP ZBook 15 nouveau driver |HP ZBook 15 nouveau driver
|han
48 matches
Mail list logo
