https://bugs.freedesktop.org/show_bug.cgi?id=68527
Priority: medium
Bug ID: 68527
Assignee: dri-devel@lists.freedesktop.org
Summary: Planetary Annihilation Alpha: translation from TGSI
failed !
Severity: normal
Classifica
https://bugs.freedesktop.org/show_bug.cgi?id=68527
--- Comment #1 from sxx.pub...@yahoo.com ---
Created attachment 84587
--> https://bugs.freedesktop.org/attachment.cgi?id=84587&action=edit
GL trace using apitrace from git
--
You are receiving this mail because:
You are the assignee for the bu
https://bugs.freedesktop.org/show_bug.cgi?id=68527
--- Comment #2 from sxx.pub...@yahoo.com ---
Created attachment 84588
--> https://bugs.freedesktop.org/attachment.cgi?id=84588&action=edit
Screenshot of game with sun shader glitch from R600g
--
You are receiving this mail because:
You are the
https://bugs.freedesktop.org/show_bug.cgi?id=68527
sxx.pub...@yahoo.com changed:
What|Removed |Added
Attachment #84588|text/plain |image/png
mime type|
https://bugs.freedesktop.org/show_bug.cgi?id=68527
--- Comment #3 from sxx.pub...@yahoo.com ---
Created attachment 84589
--> https://bugs.freedesktop.org/attachment.cgi?id=84589&action=edit
Screenshot of game without glitch from Intel HD3000
--
You are receiving this mail because:
You are the
https://bugs.freedesktop.org/show_bug.cgi?id=68527
--- Comment #4 from sxx.pub...@yahoo.com ---
I'm also forgot to post full error:
EE r600_shader.c:158 r600_pipe_shader_create - translation from TGSI failed !
EE r600_state_common.c:754 r600_shader_select - Failed to build shader variant
(type=1)
https://bugs.freedesktop.org/show_bug.cgi?id=68527
--- Comment #5 from sxx.pub...@yahoo.com ---
Created attachment 84590
--> https://bugs.freedesktop.org/attachment.cgi?id=84590&action=edit
GLSL code of sun shader
--
You are receiving this mail because:
You are the assignee for the bug.
__
Hi
On Fri, Aug 23, 2013 at 2:00 PM, Martin Peres wrote:
> Le 23/08/2013 13:13, David Herrmann a écrit :
>
>> Hi
>>
>> I reduced the vma access-management patches to a minimum. I now do filp*
>> tracking in gem unconditionally and force drm_gem_mmap() to check this.
>> Hence,
>> all gem drivers ar
The VMA offset manager uses a device-global address-space. Hence, any
user can currently map any offset-node they want. They only need to guess
the right offset. If we wanted per open-file offset spaces, we'd either
need VM_NONLINEAR mappings or multiple "struct address_space" trees. As
both doesn'
GEM does already a good job in tracking access to gem buffers via handles
and drm_vma access management. However, TTM drivers currently do not
verify this during mmap().
TTM provides the verify_access() callback to test this. So fix all drivers
to actually call into gem+vma to verify access instea
We implement automatic vma mmap() access management for all drivers using
gem_mmap. We use the vma manager to add each open-file that creates a
gem-handle to the vma-node of the underlying gem object. Once the handle
is destroyed, we drop the open-file again.
This allows us to use drm_vma_node_is_
Render nodes provide an API for userspace to use non-privileged GPU
commands without any running DRM-Master. It is useful for offscreen
rendering, GPGPU clients, and normal render clients which do not perform
modesetting.
Compared to legacy clients, render clients no longer need any
authentication
From: Kristian Høgsberg
Enable support for drm render nodes for i915 by flagging the ioctls that
are safe and just needed for rendering.
v2: mark reg_read, set_caching and get_caching (ickle, danvet)
Signed-off-by: Kristian Høgsberg
Signed-off-by: David Herrmann
Reviewed-by: Daniel Vetter
--
From: Martin Peres
Enable support for drm render nodes for nouveau by flagging the ioctls that
are safe and just needed for rendering.
Cc: Ben Skeggs
Cc: Maarten Lankhorst
Signed-off-by: Martin Peres
Signed-off-by: David Herrmann
---
drivers/gpu/drm/nouveau/nouveau_drm.c | 24 --
From: Christian König
Enable support for drm render nodes for radeon by flagging the ioctls that
are safe and just needed for rendering.
Signed-off-by: Christian König
Signed-off-by: David Herrmann
---
drivers/gpu/drm/radeon/radeon_drv.c | 2 +-
drivers/gpu/drm/radeon/radeon_kms.c | 22 +
https://bugs.freedesktop.org/show_bug.cgi?id=68468
--- Comment #3 from adam...@gmail.com ---
Did some research, the general bisecting idea seems clear, but I couldn't build
mesa itself unfortunately.
I'll dig some more regarding those errors, but in the meantime, is there
anything else I might try
On 25/08/2013 17:09, David Herrmann wrote:
Hi
On Fri, Aug 23, 2013 at 2:00 PM, Martin Peres wrote:
Le 23/08/2013 13:13, David Herrmann a écrit :
Hi
I reduced the vma access-management patches to a minimum. I now do filp*
tracking in gem unconditionally and force drm_gem_mmap() to check this
https://bugs.freedesktop.org/show_bug.cgi?id=51798
--- Comment #3 from Ilia Mirkin ---
> ls /sys/bus/pci/devices/*/drm/*/card*/enabled | xargs -I {} -i bash -c "echo
> -n {}: ; cat {}"
Here's a neat trick:
grep . /sys/bus/pci/devices/*/drm/*/card*/enabled
I think "enabled" is like "is there a
https://bugs.freedesktop.org/show_bug.cgi?id=68544
Priority: medium
Bug ID: 68544
Assignee: dri-devel@lists.freedesktop.org
Summary: cannot build mesa 9.2 without llvm
Severity: normal
Classification: Unclassified
OS: All
https://bugs.freedesktop.org/show_bug.cgi?id=68527
--- Comment #6 from Henri Verbeet ---
(In reply to comment #4)
> I'm also forgot to post full error:
> EE r600_shader.c:158 r600_pipe_shader_create - translation from TGSI failed !
> EE r600_state_common.c:754 r600_shader_select - Failed to build
https://bugs.freedesktop.org/show_bug.cgi?id=68527
--- Comment #7 from Vadim Girlin ---
(In reply to comment #4)
> I'm also forgot to post full error:
> EE r600_shader.c:158 r600_pipe_shader_create - translation from TGSI failed !
> EE r600_state_common.c:754 r600_shader_select - Failed to build
DRM_IOCTL_MODE_GETFB is used to retrieve information about a given
framebuffer ID. It is a read-only helper and was thus declassified for
unprivileged access in:
commit a14b1b42477c5ef089fcda88cbaae50d979eb8f9
Author: Mandeep Singh Baines
Date: Fri Jan 20 12:11:16 2012 -0800
drm: r
https://bugs.freedesktop.org/show_bug.cgi?id=68544
--- Comment #1 from Kris ---
Created attachment 84625
--> https://bugs.freedesktop.org/attachment.cgi?id=84625&action=edit
Fix order of "and"/"or" for AM_CONDITIONAL
Seems to be problem within configure.ac,
occuring since:
http://cgit.freedes
https://bugzilla.kernel.org/show_bug.cgi?id=60791
Bug ID: 60791
Summary: Display corruption with Radeon driver during boot and
on desktop
Product: Drivers
Version: 2.5
Kernel Version: 3.10.5
Hardware: x86-64
https://bugzilla.kernel.org/show_bug.cgi?id=60791
--- Comment #1 from Brian Hall ---
Created attachment 107303
--> https://bugzilla.kernel.org/attachment.cgi?id=107303&action=edit
showing the problem during boot
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=60791
--- Comment #2 from Brian Hall ---
Created attachment 107304
--> https://bugzilla.kernel.org/attachment.cgi?id=107304&action=edit
green arc at lightdm login prompt
--
You are receiving this mail because:
You are watching the assignee of the bu
https://bugzilla.kernel.org/show_bug.cgi?id=60791
--- Comment #4 from Brian Hall ---
Created attachment 107306
--> https://bugzilla.kernel.org/attachment.cgi?id=107306&action=edit
hash of flickering green lines when displaying website
--
You are receiving this mail because:
You are watching t
https://bugzilla.kernel.org/show_bug.cgi?id=60791
--- Comment #3 from Brian Hall ---
Created attachment 107305
--> https://bugzilla.kernel.org/attachment.cgi?id=107305&action=edit
hash of flickering green lines when displaying website
--
You are receiving this mail because:
You are watching t
https://bugzilla.kernel.org/show_bug.cgi?id=60791
--- Comment #5 from Brian Hall ---
Created attachment 107307
--> https://bugzilla.kernel.org/attachment.cgi?id=107307&action=edit
hash of flickering green lines when displaying website
--
You are receiving this mail because:
You are watching t
https://bugzilla.kernel.org/show_bug.cgi?id=60791
Brian Hall changed:
What|Removed |Added
Regression|No |Yes
--
You are receiving this mail because:
https://bugzilla.kernel.org/show_bug.cgi?id=60791
--- Comment #6 from Brian Hall ---
Created attachment 107308
--> https://bugzilla.kernel.org/attachment.cgi?id=107308&action=edit
dmesg output
--
You are receiving this mail because:
You are watching the assignee of the bug.
__
https://bugzilla.kernel.org/show_bug.cgi?id=60791
--- Comment #7 from Brian Hall ---
Created attachment 107309
--> https://bugzilla.kernel.org/attachment.cgi?id=107309&action=edit
lspci -vvv output
--
You are receiving this mail because:
You are watching the assignee of the bug.
_
https://bugzilla.kernel.org/show_bug.cgi?id=60791
--- Comment #8 from Brian Hall ---
Created attachment 107310
--> https://bugzilla.kernel.org/attachment.cgi?id=107310&action=edit
Xorg log
--
You are receiving this mail because:
You are watching the assignee of the bug.
__
https://bugzilla.kernel.org/show_bug.cgi?id=60791
--- Comment #9 from Brian Hall ---
Problem only occurs when using the DVI output from my motherboard. When I
switch to the VGA motherboard output, the problem on kernels > 3.10.4
disappears. I'd prefer to use DVI, so I don't consider this a perman
On Sun, Aug 25, 2013 at 11:12:39PM +0200, David Herrmann wrote:
> DRM_IOCTL_MODE_GETFB is used to retrieve information about a given
> framebuffer ID. It is a read-only helper and was thus declassified for
> unprivileged access in:
>
> commit a14b1b42477c5ef089fcda88cbaae50d979eb8f9
> Author:
https://bugs.freedesktop.org/show_bug.cgi?id=68544
--- Comment #2 from Emil Velikov ---
Seems like test always priorities the _and_ over _or_ :)
Kris' patch does the right thing, although it can be simplified to either:
test "x$HAVE_GALLIUM_I915" = xyes -o "x$HAVE_GALLIUM_SOFTPIPE" = xyes && te
https://bugzilla.kernel.org/show_bug.cgi?id=60639
douglas_pe...@yahoo.com changed:
What|Removed |Added
CC||douglas_pe...@yahoo.com
--- Comm
https://bugzilla.kernel.org/show_bug.cgi?id=60639
--- Comment #6 from douglas_pe...@yahoo.com ---
Created attachment 107312
--> https://bugzilla.kernel.org/attachment.cgi?id=107312&action=edit
Requested xorg log
I hope this is the correct log file
--
You are receiving this mail because:
You a
https://bugzilla.kernel.org/show_bug.cgi?id=60639
--- Comment #7 from douglas_pe...@yahoo.com ---
Created attachment 107313
--> https://bugzilla.kernel.org/attachment.cgi?id=107313&action=edit
dmesg output
--
You are receiving this mail because:
You are watching the assignee of the bug.
__
https://bugzilla.kernel.org/show_bug.cgi?id=60639
--- Comment #8 from douglas_pe...@yahoo.com ---
Created attachment 107314
--> https://bugzilla.kernel.org/attachment.cgi?id=107314&action=edit
xrandr --verbose output
--
You are receiving this mail because:
You are watching the assignee of the
https://bugzilla.kernel.org/show_bug.cgi?id=60639
--- Comment #9 from douglas_pe...@yahoo.com ---
I will note that the system is currently set up with two monitors, one
dual-link DVI (the one I am using to enter this message) the other Display port
that was working up to grub, then it shut itself
From: Wei Yongjun
In case of error, the function devm_ioremap_resource() returns ERR_PTR()
and never returns NULL. The NULL test in the return value check should be
replaced with IS_ERR(). Also remove the dev_err call to avoid redundant
error message and check for return value of platform_get_res
Em Thu, 22 Aug 2013 18:00:14 +0200
Wolfram Sang escreveu:
> I2C of helpers used to live in of_i2c.c but experience (from SPI) shows
> that it is much cleaner to have this in the core. This also removes a
> circular dependency between the helpers and the core, and so we can
> finally register chil
https://bugs.freedesktop.org/show_bug.cgi?id=68451
--- Comment #5 from Peter Kraus ---
Hello again,
I'm trying to bisect, but the compilation fails with:
glsl_parser.cpp:2603:41: error: 'scanner' was not declared in this scope
That's on git revision 56114, which is the first one git bisect asks
https://bugs.freedesktop.org/show_bug.cgi?id=68527
--- Comment #8 from sxx.pub...@yahoo.com ---
Created attachment 84628
--> https://bugs.freedesktop.org/attachment.cgi?id=84628&action=edit
Game log with R600_DUMP_SHADERS=1, error on line 1488
--
You are receiving this mail because:
You are th
https://bugs.freedesktop.org/show_bug.cgi?id=68527
--- Comment #9 from sxx.pub...@yahoo.com ---
(In reply to comment #6)
> I don't think that's quite the full output, but it does look somewhat like
> an issue that was fixed by commit b5ddaf9975f96c46ea3dfb02c4130de5196b238c.
I'm just tried it wit
rection to find which commit broke the known good state.
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20130825/e22bfd8b/attachment.html>
ttp://lists.freedesktop.org/archives/dri-devel/attachments/20130825/aac0c4e9/attachment.html>
nee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20130825/4d3ec06c/attachment-0001.html>
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20130825/d52a1410/attachment.html>
||
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20130825/6c9e57b6/attachment.html>
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20130825/dbdeafa2/attachment.html>
(type=1) -1
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20130825/ce89d7aa/attachment.html>
the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20130825/d475b1ae/attachment.html>
Hi
On Fri, Aug 23, 2013 at 2:00 PM, Martin Peres wrote:
> Le 23/08/2013 13:13, David Herrmann a ?crit :
>
>> Hi
>>
>> I reduced the vma access-management patches to a minimum. I now do filp*
>> tracking in gem unconditionally and force drm_gem_mmap() to check this.
>> Hence,
>> all gem drivers ar
The VMA offset manager uses a device-global address-space. Hence, any
user can currently map any offset-node they want. They only need to guess
the right offset. If we wanted per open-file offset spaces, we'd either
need VM_NONLINEAR mappings or multiple "struct address_space" trees. As
both doesn'
We implement automatic vma mmap() access management for all drivers using
gem_mmap. We use the vma manager to add each open-file that creates a
gem-handle to the vma-node of the underlying gem object. Once the handle
is destroyed, we drop the open-file again.
This allows us to use drm_vma_node_is_
GEM does already a good job in tracking access to gem buffers via handles
and drm_vma access management. However, TTM drivers currently do not
verify this during mmap().
TTM provides the verify_access() callback to test this. So fix all drivers
to actually call into gem+vma to verify access instea
Render nodes provide an API for userspace to use non-privileged GPU
commands without any running DRM-Master. It is useful for offscreen
rendering, GPGPU clients, and normal render clients which do not perform
modesetting.
Compared to legacy clients, render clients no longer need any
authentication
From: Kristian H?gsberg
Enable support for drm render nodes for i915 by flagging the ioctls that
are safe and just needed for rendering.
v2: mark reg_read, set_caching and get_caching (ickle, danvet)
Signed-off-by: Kristian H?gsberg
Signed-off-by: David Herrmann
Reviewed-by: Daniel Vetter
--
From: Martin Peres
Enable support for drm render nodes for nouveau by flagging the ioctls that
are safe and just needed for rendering.
Cc: Ben Skeggs
Cc: Maarten Lankhorst
Signed-off-by: Martin Peres
Signed-off-by: David Herrmann
---
drivers/gpu/drm/nouveau/nouveau_drm.c | 24 --
From: Christian K?nig
Enable support for drm render nodes for radeon by flagging the ioctls that
are safe and just needed for rendering.
Signed-off-by: Christian K?nig
Signed-off-by: David Herrmann
---
drivers/gpu/drm/radeon/radeon_drv.c | 2 +-
drivers/gpu/drm/radeon/radeon_kms.c | 22 +
se I might try?
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20130825/f89c0871/attachment.html>
On 25/08/2013 17:09, David Herrmann wrote:
> Hi
>
> On Fri, Aug 23, 2013 at 2:00 PM, Martin Peres wrote:
>> Le 23/08/2013 13:13, David Herrmann a ?crit :
>>
>>> Hi
>>>
>>> I reduced the vma access-management patches to a minimum. I now do filp*
>>> tracking in gem unconditionally and force drm_gem
ghly recommend retesting with a new kernel and
xf86-video-nouveau (and maybe xorg-server).
--
You are receiving this mail because:
You are on the CC list for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20130825/271e7cdc/attachment.html>
llvm-c/Core.h: No such file or directory
compilation terminated.
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20130825/b18fba5f/attachment.html>
g.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20130825/45b447ad/attachment.html>
ng this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20130825/1d9399b7/attachment.html>
DRM_IOCTL_MODE_GETFB is used to retrieve information about a given
framebuffer ID. It is a read-only helper and was thus declassified for
unprivileged access in:
commit a14b1b42477c5ef089fcda88cbaae50d979eb8f9
Author: Mandeep Singh Baines
Date: Fri Jan 20 12:11:16 2012 -0800
drm: r
desktop.org/archives/dri-devel/attachments/20130825/f141f339/attachment-0001.html>
https://bugzilla.kernel.org/show_bug.cgi?id=60791
Bug ID: 60791
Summary: Display corruption with Radeon driver during boot and
on desktop
Product: Drivers
Version: 2.5
Kernel Version: 3.10.5
Hardware: x86-64
https://bugzilla.kernel.org/show_bug.cgi?id=60791
--- Comment #1 from Brian Hall ---
Created attachment 107303
--> https://bugzilla.kernel.org/attachment.cgi?id=107303&action=edit
showing the problem during boot
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=60791
--- Comment #2 from Brian Hall ---
Created attachment 107304
--> https://bugzilla.kernel.org/attachment.cgi?id=107304&action=edit
green arc at lightdm login prompt
--
You are receiving this mail because:
You are watching the assignee of the bu
https://bugzilla.kernel.org/show_bug.cgi?id=60791
--- Comment #3 from Brian Hall ---
Created attachment 107305
--> https://bugzilla.kernel.org/attachment.cgi?id=107305&action=edit
hash of flickering green lines when displaying website
--
You are receiving this mail because:
You are watching t
https://bugzilla.kernel.org/show_bug.cgi?id=60791
--- Comment #4 from Brian Hall ---
Created attachment 107306
--> https://bugzilla.kernel.org/attachment.cgi?id=107306&action=edit
hash of flickering green lines when displaying website
--
You are receiving this mail because:
You are watching t
https://bugzilla.kernel.org/show_bug.cgi?id=60791
--- Comment #5 from Brian Hall ---
Created attachment 107307
--> https://bugzilla.kernel.org/attachment.cgi?id=107307&action=edit
hash of flickering green lines when displaying website
--
You are receiving this mail because:
You are watching t
https://bugzilla.kernel.org/show_bug.cgi?id=60791
Brian Hall changed:
What|Removed |Added
Regression|No |Yes
--
You are receiving this mail because:
https://bugzilla.kernel.org/show_bug.cgi?id=60791
--- Comment #6 from Brian Hall ---
Created attachment 107308
--> https://bugzilla.kernel.org/attachment.cgi?id=107308&action=edit
dmesg output
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=60791
--- Comment #7 from Brian Hall ---
Created attachment 107309
--> https://bugzilla.kernel.org/attachment.cgi?id=107309&action=edit
lspci -vvv output
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=60791
--- Comment #8 from Brian Hall ---
Created attachment 107310
--> https://bugzilla.kernel.org/attachment.cgi?id=107310&action=edit
Xorg log
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=60791
--- Comment #9 from Brian Hall ---
Problem only occurs when using the DVI output from my motherboard. When I
switch to the VGA motherboard output, the problem on kernels > 3.10.4
disappears. I'd prefer to use DVI, so I don't consider this a perman
On Sun, Aug 25, 2013 at 11:12:39PM +0200, David Herrmann wrote:
> DRM_IOCTL_MODE_GETFB is used to retrieve information about a given
> framebuffer ID. It is a read-only helper and was thus declassified for
> unprivileged access in:
>
> commit a14b1b42477c5ef089fcda88cbaae50d979eb8f9
> Author:
82 matches
Mail list logo