dri-devel January 2016

dri-devel@lists.freedesktop.org

194 participants
1200 discussions

[Bug 91789] MST (multi stream) with Asus PQ321 drm_dp_calc_pbn_mode() fails
by bugzilla-daemon＠freedesktop.org 25 Apr '16

25 Apr '16

https://bugs.freedesktop.org/show_bug.cgi?id=91789 Bug ID: 91789 Summary: MST (multi stream) with Asus PQ321 drm_dp_calc_pbn_mode() fails Product: DRI Version: unspecified Hardware: x86 (IA32) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: General Assignee: dri-devel(a)lists.freedesktop.org Reporter: Peter.Blum(a)lxco.com If a Asus monitor PQ321 is used in MST mode it gets no signal. This is because the function drm_dp_calc_pbn_mode() in drm_dp_mst_topology.c returns a bad pixel bandwith number for the mode Modeline 131:"1920x2160" 60 297000 1920 2008 2052 2200 2160 2168 2178 2250 0x48 0x5 The function return 8 and not the correct value of 1063. Using simple u32 arithmetic in drm_dp_calc_pbn_mode() the monitor works fine. I'm not sure if unsigned 32 bit would overflow in some cases. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 93800] xfwm4 with compositing hangs indefinitely after after coming back from dpms off
by bugzilla-daemon＠freedesktop.org 24 Apr '16

24 Apr '16

https://bugs.freedesktop.org/show_bug.cgi?id=93800 Bug ID: 93800 Summary: xfwm4 with compositing hangs indefinitely after after coming back from dpms off Product: DRI Version: XOrg git Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: DRM/Radeon Assignee: dri-devel(a)lists.freedesktop.org Reporter: h.judt(a)gmx.at Created attachment 121158 --> https://bugs.freedesktop.org/attachment.cgi?id=121158&action=edit Xorg.0.log I'm not sure whether this belongs to mesa or xf86-video-ati or somewhere else, so I'll simply state the problem: Steps to reproduce: 1) Start xfwm4 (latest git from master), which uses opengl for vsyncing to avoid screen tearing. 2) xset dpms force off; sleep 3; xset dpms force on This alone is enough to make xfwm4 hang indefinitely. I've attached gdb to the xfwm4 process and got this backtrace: Program received signal SIGINT, Interrupt. 0x00007f7584ffd50d in poll () at ../sysdeps/unix/syscall-template.S:84 84 in ../sysdeps/unix/syscall-template.S #0 0x00007f7584ffd50d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x00007f75846f8ac2 in poll (__timeout=-1, __nfds=1, __fds=0x7ffc8e0e2a80) at /usr/include/bits/poll2.h:46 #2 _xcb_conn_wait (c=c@entry=0x10fd820, cond=cond@entry=0x1447f88, vector=vector@entry=0x0, count=count@entry=0x0) at /var/tmp/portage/x11-libs/libxcb-1.11.1/work/libxcb-1.11.1/src/xcb_conn.c:459 #3 0x00007f75846fa7f9 in xcb_wait_for_special_event (c=0x10fd820, se=0x1447f60) at /var/tmp/portage/x11-libs/libxcb-1.11.1/work/libxcb-1.11.1/src/xcb_in.c:789 #4 0x00007f75817ef6db in dri3_wait_for_event (draw=draw@entry=0x1447608) at /var/tmp/portage/media-libs/mesa-9999/work/mesa-9999/src/loader/loader_dri3_helper.c:280 #5 0x00007f75817efa78 in loader_dri3_wait_for_msc (draw=0x1447608, target_msc=<optimized out>, divisor=<optimized out>, remainder=<optimized out>, ust=0x7ffc8e0e2cb8, msc=0x7ffc8e0e2cc0, sbc=0x7ffc8e0e2cd0) at /var/tmp/portage/media-libs/mesa-9999/work/mesa-9999/src/loader/loader_dri3_helper.c:314 #6 0x00007f75817ea8f1 in dri3_wait_for_msc (pdraw=<optimized out>, target_msc=<optimized out>, divisor=<optimized out>, remainder=<optimized out>, ust=<optimized out>, msc=<optimized out>, sbc=0x7ffc8e0e2cd0) at /var/tmp/portage/media-libs/mesa-9999/work/mesa-9999/src/glx/dri3_glx.c:389 #7 0x00000000004170a9 in wait_glx_vblank (screen_info=0x1216df0) at compositor.c:1424 #8 paint_all (buffer=<optimized out>, region=<optimized out>, screen_info=0x1216df0) at compositor.c:2202 #9 repair_screen (screen_info=<optimized out>) at compositor.c:2318 #10 compositor_timeout_cb (data=0x1216df0, data@entry=<error reading variable: value has been optimized out>) at compositor.c:2335 #11 0x00007f7585f66643 in g_timeout_dispatch (source=0x14ee290, callback=<optimized out>, user_data=<optimized out>) at /var/tmp/portage/dev-libs/glib-2.46.2-r1/work/glib-2.46.2/glib/gmain.c:4577 #12 0x00007f7585f65bad in g_main_dispatch (context=0x1129e70) at /var/tmp/portage/dev-libs/glib-2.46.2-r1/work/glib-2.46.2/glib/gmain.c:3154 #13 g_main_context_dispatch (context=context@entry=0x1129e70) at /var/tmp/portage/dev-libs/glib-2.46.2-r1/work/glib-2.46.2/glib/gmain.c:3769 #14 0x00007f7585f65f80 in g_main_context_iterate (context=0x1129e70, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at /var/tmp/portage/dev-libs/glib-2.46.2-r1/work/glib-2.46.2/glib/gmain.c:3840 #15 0x00007f7585f662a2 in g_main_loop_run (loop=0x148f2e0) at /var/tmp/portage/dev-libs/glib-2.46.2-r1/work/glib-2.46.2/glib/gmain.c:4034 #16 0x00007f758744b137 in IA__gtk_main () at /var/tmp/portage/x11-libs/gtk+-2.24.29/work/gtk+-2.24.29/gtk/gtkmain.c:1268 #17 0x000000000040d5d4 in main (argc=1, argv=0x7ffc8e0e3178) at main.c:686 Note this problem does not occur on another graphics card (sandybridge, haswell). I've tried to reproduce it using compiz, but it didn't happen that way (maybe it wasn't using vsync, don't know). Here are the xorg settings: Section "Device" Identifier "ATI Radeon R9 390" Driver "radeon" Option "DRI3" "on" Option "ColorTiling" "on" Option "SwapbuffersWait" "on" Option "EnablePageFlip" "on" Option "ColorTiling2D" "on" EndSection -- You are receiving this mail because: You are the assignee for the bug.

1 9

[PATCH v8 00/11] Add DRM for stih4xx platforms
by Benjamin Gaignard 22 Apr '16

22 Apr '16

This series of patches add the support of DRM/KMS drivers for STMicroelectronics chipsets stih416 and stih407. version 8: - Allow driver to be build as kernel module. - Use Universal Plane instead of legacy code. patches could be found here: git://git.linaro.org/people/benjamin.gaignard/kernel.git on branch: drm_kms_for_next-v8 version 7: - rebased on top of drm-next (2014-07-24) patches could be found here: git://git.linaro.org/people/benjamin.gaignard/kernel.git on branch: drm_kms_for_next-v7 version 6: - rebased on top of new component framework API. patches could be found here: git://git.linaro.org/people/benjamin.gaignard/kernel.git on branch: drm_kms_for_next-v6 version 5: - Rework sti_drm_drv probes functions to support deferred probe. This allow hdmi to delayed framebuffer creation until I2C is available. - Add ops functions in sti_layer structure to simpify GDP and VID code. - Add NOTES file to describe how the DRM concepts are mapped on hardware. patches could be found here: git://git.linaro.org/people/benjamin.gaignard/kernel.git on branch: drm_kms_for_next-v5 version 4: - Remove depency between TVout it subdevices HDMI and HDA - Rework and simplify VTG and VTAC code - Fix numbers of typo and indentation - Remove debug (will be push in separate patches) - Fix remarks done in previous patcheset patches could be found here: git://git.linaro.org/people/benjamin.gaignard/kernel.git on branch: drm_kms_for_next-v4 version 3: - Correctly split code between probe and bind funtions - Squash some commits - remove HQ-VDP device code to have a smaller patcheset, we will introduce it later. patches could be found here: git://git.linaro.org/people/benjamin.gaignard/kernel.git on branch: drm_kms_for_next-v3 version 2: - Use componentized device instead of register sub-devices in master driver probe function - Fix Makefile and Kconfig to only allow built-in compilation patches could be found here: git://git.linaro.org/people/benjamin.gaignard/kernel.git on branch: drm_kms_for_next-v2 version 1: - First path submission Hardware is split in two main blocks: Compositor and TVout. Each of them includes specific hardware IPs and the display timing are controlled by a specific Video Timing Generator hardware IP (VTG). Compositor is made of the follow hardware IPs: - GDP (Generic Display Pipeline) which is an entry point for graphic (RGB) buffers - VDP (Video Diplay Pipeline) which is an entry point for video (YUV) buffers - HQVDP (High Quality Video Display Processor) that supports scaling, deinterlacing and some miscellaneous image quality improvements. It fetches the Video decoded buffers from memory, processes them and pushes them to the Compositor through a HW dedicated bus. - Mixer is responsible of mixing all the entries depending of their respective z-order and layout TVout is divided in 3 parts: - HDMI to generate HDMI signals, depending of chipset version HDMI phy can change. - HDA to generate signals for HD analog TV - VIP to control/switch data path coming from Compositor On stih416 compositor and Tvout are on different dies so a Video Trafic Advance inter-die Communication mechanism (VTAC) is needed. +---------------------------------------------+ +----------------------------------------+ | +-------------------------------+ +----+ | | +----+ +--------------------------+ | | | | | | | | | | | +---------+ +----+ | | | | +----+ +------+ | | | | | | | | | VIP |---->|HDMI| | | | | |GPD +------------->| | | | | | | | | | | | +----+ | | | | +----+ |Mixer |--|-->| | | | | |---|->| switcher| | | | | | | | | | | | | | | | | +----+ | | | | | | | | | | | | | | | |---->|HDA | | | | | +------+ | |VTAC|========>|VTAC| | +---------+ +----+ | | | | | | | | | | | | | | | | Compositor | | | | | | | | TVout | | | +-------------------------------+ | | | | | | +--------------------------+ | | ^ | | | | | | ^ | | | | | | | | | | | | +--------------+ | | | | | | +-------------+ | | | VTG (master) |----->| | | | | |----->| VTG (slave) | | | +--------------+ +----+ | | +----+ +-------------+ | |Digital die | | Analog Die| +---------------------------------------------+ +----------------------------------------+ On stih407 Compositor and Tvout are on the same die +-----------------------------------------------------------------+ | +-------------------------------+ +--------------------------+ | | | | | +---------+ +----+ | | | | +----+ +------+ | | | VIP |---->|HDMI| | | | | |GPD +------------->| | | | | | +----+ | | | | +----+ |Mixer |--|--|->| switcher| | | | | +----+ +-----+ | | | | | | +----+ | | | | |VDP +-->+HQVDP+--->| | | | | |---->|HDA | | | | | +----+ +-----+ +------+ | | +---------+ +----+ | | | | | | | | | | Compositor | | TVout | | | +-------------------------------+ +--------------------------+ | | ^ ^ | | | | | | +--------------+ | | | VTG | | | +--------------+ | |Digital die | +-----------------------------------------------------------------+ In addition of the drivers for the IPs listed before a thin I2C driver (hdmiddc) is used by HDMI driver to retrieve EDID for monitor. To unify interfaces of GDP and VDP we create a "layer" interface called by compositor to control both GPD and VDP. Hardware have memory contraints (alignment, contiguous) so we use CMA drm helpers functions to allocate frame buffer. File naming convention is: - sti_* for IPs drivers - sti_drm_* for drm functions implementation. Benjamin Gaignard (11): drm: sti: add bindings for DRM driver drm: sti: add VTG driver drm: sti: add VTAC drivers drm: sti: add HDMI driver drm: sti: add HDA driver drm: sti: add TVOut driver drm: sti: add GDP layer drm: sti: add VID layer drm: sti: add Mixer drm: sti: add Compositor drm: sti: Add DRM driver itself .../devicetree/bindings/gpu/st,stih4xx.txt | 189 +++++ drivers/gpu/drm/Kconfig | 2 + drivers/gpu/drm/Makefile | 1 + drivers/gpu/drm/sti/Kconfig | 14 + drivers/gpu/drm/sti/Makefile | 21 + drivers/gpu/drm/sti/NOTES | 58 ++ drivers/gpu/drm/sti/sti_compositor.c | 279 +++++++ drivers/gpu/drm/sti/sti_compositor.h | 90 +++ drivers/gpu/drm/sti/sti_drm_crtc.c | 423 +++++++++++ drivers/gpu/drm/sti/sti_drm_crtc.h | 22 + drivers/gpu/drm/sti/sti_drm_drv.c | 241 ++++++ drivers/gpu/drm/sti/sti_drm_drv.h | 29 + drivers/gpu/drm/sti/sti_drm_plane.c | 195 +++++ drivers/gpu/drm/sti/sti_drm_plane.h | 18 + drivers/gpu/drm/sti/sti_gdp.c | 549 ++++++++++++++ drivers/gpu/drm/sti/sti_gdp.h | 16 + drivers/gpu/drm/sti/sti_hda.c | 794 ++++++++++++++++++++ drivers/gpu/drm/sti/sti_hdmi.c | 810 +++++++++++++++++++++ drivers/gpu/drm/sti/sti_hdmi.h | 88 +++ drivers/gpu/drm/sti/sti_hdmi_tx3g0c55phy.c | 336 +++++++++ drivers/gpu/drm/sti/sti_hdmi_tx3g0c55phy.h | 14 + drivers/gpu/drm/sti/sti_hdmi_tx3g4c28phy.c | 211 ++++++ drivers/gpu/drm/sti/sti_hdmi_tx3g4c28phy.h | 14 + drivers/gpu/drm/sti/sti_layer.c | 197 +++++ drivers/gpu/drm/sti/sti_layer.h | 123 ++++ drivers/gpu/drm/sti/sti_mixer.c | 249 +++++++ drivers/gpu/drm/sti/sti_mixer.h | 54 ++ drivers/gpu/drm/sti/sti_tvout.c | 648 +++++++++++++++++ drivers/gpu/drm/sti/sti_vid.c | 138 ++++ drivers/gpu/drm/sti/sti_vid.h | 12 + drivers/gpu/drm/sti/sti_vtac.c | 215 ++++++ drivers/gpu/drm/sti/sti_vtg.c | 366 ++++++++++ drivers/gpu/drm/sti/sti_vtg.h | 28 + 33 files changed, 6444 insertions(+) create mode 100644 Documentation/devicetree/bindings/gpu/st,stih4xx.txt create mode 100644 drivers/gpu/drm/sti/Kconfig create mode 100644 drivers/gpu/drm/sti/Makefile create mode 100644 drivers/gpu/drm/sti/NOTES create mode 100644 drivers/gpu/drm/sti/sti_compositor.c create mode 100644 drivers/gpu/drm/sti/sti_compositor.h create mode 100644 drivers/gpu/drm/sti/sti_drm_crtc.c create mode 100644 drivers/gpu/drm/sti/sti_drm_crtc.h create mode 100644 drivers/gpu/drm/sti/sti_drm_drv.c create mode 100644 drivers/gpu/drm/sti/sti_drm_drv.h create mode 100644 drivers/gpu/drm/sti/sti_drm_plane.c create mode 100644 drivers/gpu/drm/sti/sti_drm_plane.h create mode 100644 drivers/gpu/drm/sti/sti_gdp.c create mode 100644 drivers/gpu/drm/sti/sti_gdp.h create mode 100644 drivers/gpu/drm/sti/sti_hda.c create mode 100644 drivers/gpu/drm/sti/sti_hdmi.c create mode 100644 drivers/gpu/drm/sti/sti_hdmi.h create mode 100644 drivers/gpu/drm/sti/sti_hdmi_tx3g0c55phy.c create mode 100644 drivers/gpu/drm/sti/sti_hdmi_tx3g0c55phy.h create mode 100644 drivers/gpu/drm/sti/sti_hdmi_tx3g4c28phy.c create mode 100644 drivers/gpu/drm/sti/sti_hdmi_tx3g4c28phy.h create mode 100644 drivers/gpu/drm/sti/sti_layer.c create mode 100644 drivers/gpu/drm/sti/sti_layer.h create mode 100644 drivers/gpu/drm/sti/sti_mixer.c create mode 100644 drivers/gpu/drm/sti/sti_mixer.h create mode 100644 drivers/gpu/drm/sti/sti_tvout.c create mode 100644 drivers/gpu/drm/sti/sti_vid.c create mode 100644 drivers/gpu/drm/sti/sti_vid.h create mode 100644 drivers/gpu/drm/sti/sti_vtac.c create mode 100644 drivers/gpu/drm/sti/sti_vtg.c create mode 100644 drivers/gpu/drm/sti/sti_vtg.h -- 1.9.1

3 15

[Bug 44647] New: [wine regression] Call of Duty 4: Intro videos renders garbage
by bugzilla-daemon＠freedesktop.org 20 Apr '16

20 Apr '16

https://bugs.freedesktop.org/show_bug.cgi?id=44647 Bug #: 44647 Summary: [wine regression] Call of Duty 4: Intro videos renders garbage Classification: Unclassified Product: Mesa Version: git Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/r600 AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: sa(a)whiz.se Created attachment 55392 --> https://bugs.freedesktop.org/attachment.cgi?id=55392 Screenshot of broken video Intro videos in the game Call of Duty 4 (running with Wine) no longer renders correctly, bisecting leads to this: e8139ebf583acf37150a8b341bcbef6b924a7792 is the first bad commit commit e8139ebf583acf37150a8b341bcbef6b924a7792 Author: Mathias Fröhlich <Mathias.Froehlich(a)gmx.net> Date: Tue Jul 26 07:05:10 2011 +0200 r600g: Replace needless flush in texture upload. Replace pipe->flush() with pipe->texture_barrier() in the texture upload path for the staging texture. This should be enough to get data out of the gpu caches ready to be read for texture fetch. :040000 040000 b3f16d1a114f54d753ba7845b697888307f6246e faab26149053fdb2fb65d81bb2a777a77e130de2 M src Adding the flush back fixes the problem. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 7

[Bug 90655] [drm:radeon_get_bios] *ERROR* Unable to locate a BIOS ROM
by bugzilla-daemon＠freedesktop.org 19 Apr '16

19 Apr '16

https://bugs.freedesktop.org/show_bug.cgi?id=90655 Bug ID: 90655 Summary: [drm:radeon_get_bios] *ERROR* Unable to locate a BIOS ROM Product: DRI Version: XOrg git Hardware: PowerPC OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/Radeon Assignee: dri-devel(a)lists.freedesktop.org Reporter: mathieu.malaterre(a)gmail.com On my old Mac Mini G4 (PowerPC) I am seeing this dmesg output: [ 12.058859] [drm] Initialized drm 1.1.0 20060810 [ 13.051939] [drm] radeon kernel modesetting enabled. [ 13.055867] checking generic (9c008000 5a000) vs hw (98000000 8000000) [ 13.055875] fb: switching to radeondrmfb from OFfb ATY,RockHo [ 13.059702] Console: switching to colour dummy device 80x25 [ 13.060655] radeon 0000:00:10.0: enabling device (0006 -> 0007) [ 13.061195] [drm] initializing kernel modesetting (RV280 0x1002:0x5962 0x1002:0x5962). [ 13.061227] [drm] register mmio base: 0x90000000 [ 13.061236] [drm] register mmio size: 65536 [ 13.061318] radeon 0000:00:10.0: Invalid ROM contents [ 13.061341] radeon 0000:00:10.0: Invalid ROM contents [ 13.061356] [drm:radeon_get_bios] *ERROR* Unable to locate a BIOS ROM [ 13.061379] [drm] Using device-tree clock info [ 13.061417] agpgart-uninorth 0000:00:0b.0: putting AGP V2 device into 4x mode [ 13.061433] radeon 0000:00:10.0: putting AGP V2 device into 4x mode [ 13.061484] radeon 0000:00:10.0: GTT: 256M 0x00000000 - 0x0FFFFFFF It would be nice to either remove this error report as I believe it is erroneous. Using debian/jessie with: $ apt-cache policy libdrm-radeon1 libdrm-radeon1: Installé : 2.4.58-2 Candidat : 2.4.58-2 Table de version : *** 2.4.58-2 0 500 http://ftp.fr.debian.org/debian/ jessie/main powerpc Packages 100 /var/lib/dpkg/status -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 91480] Dead Island: Crash loading Act 3 possible shader issue
by bugzilla-daemon＠freedesktop.org 19 Apr '16

19 Apr '16

https://bugs.freedesktop.org/show_bug.cgi?id=91480 Bug ID: 91480 Summary: Dead Island: Crash loading Act 3 possible shader issue Product: Mesa Version: 10.6 Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/r600 Assignee: dri-devel(a)lists.freedesktop.org Reporter: sa(a)whiz.se QA Contact: dri-devel(a)lists.freedesktop.org Created attachment 117408 --> https://bugs.freedesktop.org/attachment.cgi?id=117408&action=edit backtrace with 10.5.9 I'm getting a reproducible crash in the game Dead Island when loading act 3. Sometimes this is a straight segfault, sometimes the game pops up a warning "An unknown error occured while compiling shaders." I'm attaching a backtrace of the segfault from Mesa 10.5.9, I still get the error with 10.6.3. This might be a shader issue, I get this warning in the game log: /media/Data/perforce/di/releases/di_master_steambox/src/engine/ropengl/ROpenGL_Shader.cpp(471) : Condition: 0 && "Cannot compile GL shader!" LLOG: 0:35(12): warning: extension `GL_ATI_draw_buffers' unsupported in fragment shader 0:209(3): error: syntax error, unexpected '=' ERRR: Assertion failed! /media/Data/perforce/di/releases/di_master_steambox/src/engine/ropengl/ROpenGL_Shader.cpp(678) : Condition: 0 && "Compilation of shader failed!" ERRR: [CPShader] cannot create pixel shader LLOG: binlen: 0; format: 0; program: 48828 LLOG: FAILED TO LOAD BINARY!!! Loading from sources.TOTAL TIME: 247398.718750ms I'm attaching the failing shader. I'm failing this against r600g as that's where the backtrace points, but this is probably a general shader issue. Probably not the same as #85564 as I have played through half the game with just a few hiccups. Side note: this title might be a good candidate for some sort of cache. Loading times are more than a minute and it seems to be spending most of that time compiling. -- You are receiving this mail because: You are the assignee for the bug.

1 5

[Bug 89891] Outlast segfault on new game
by bugzilla-daemon＠freedesktop.org 19 Apr '16

19 Apr '16

https://bugs.freedesktop.org/show_bug.cgi?id=89891 Bug ID: 89891 Summary: Outlast segfault on new game Product: Mesa Version: git Hardware: x86 (IA32) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/r600 Assignee: dri-devel(a)lists.freedesktop.org Reporter: sa(a)whiz.se QA Contact: dri-devel(a)lists.freedesktop.org Created attachment 114851 --> https://bugs.freedesktop.org/attachment.cgi?id=114851&action=edit backtrace with git version lsThe game Outlast (from the latest Humble Indie Bundle) segfaults when a new game is launched. With Mesa 10.4.2 I get a segfault in ir_assignment::ir_assignment. With current git I get a "radeon: mmap failed, errno: 12" and a segfault in __memcpy_ssse3. Another problem is that the game takes ages to start, about 90 seconds from start to menu. Most of this time is spent compiling more than 18000 shaders, so maybe that's just a problem with the game. System environment: -- system architecture: 32-bit -- Linux distribution: Debian unstable -- GPU: REDWOOD -- Model: XFX Radeon HD 5670 1GB -- Display connector: DVI -- xf86-video-ati: 7.5.0 -- xserver: 1.16.4 -- mesa: 10.4.2 -- drm: 2.4.58 -- kernel: 3.19 -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 69623] New: Pink Pony misrenders - - shader requires 126 registers
by bugzilla-daemon＠freedesktop.org 19 Apr '16

19 Apr '16

https://bugs.freedesktop.org/show_bug.cgi?id=69623 Priority: medium Bug ID: 69623 Assignee: dri-devel(a)lists.freedesktop.org Summary: Pink Pony misrenders - - shader requires 126 registers Severity: normal Classification: Unclassified OS: Linux (All) Reporter: sa(a)whiz.se Hardware: x86 (IA32) Status: NEW Version: 9.2 Component: Drivers/Gallium/r600 Product: Mesa Created attachment 86224 --> https://bugs.freedesktop.org/attachment.cgi?id=86224&action=edit Screenshot of bug The game Pink Pony (http://code.google.com/p/pink-pony/) does not render correctly with the r600g driver and Mesa 9.2, see attached screenshot. The following error is printed in the terminal: EE ../../../../../../src/gallium/drivers/r600/r600_shader.c:1580 r600_shader_from_tgsi - GPR limit exceeded - shader requires 126 registers EE ../../../../../../src/gallium/drivers/r600/r600_shader.c:158 r600_pipe_shader_create - translation from TGSI failed ! EE ../../../../../../src/gallium/drivers/r600/r600_state_common.c:754 r600_shader_select - Failed to build shader variant (type=0) -12 I'm not sure if this is the same problem as bug 68527. System environment: -- system architecture: 32-bit -- Linux distribution: Debian unstable -- GPU: REDWOOD -- Model: XFX Radeon HD 5670 1GB -- Display connector: DVI -- xf86-video-ati: 7.2.0 -- xserver: 1.12.4 -- mesa: 9.2 -- drm: 2.4.46 -- kernel: 3.11 -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 90869] Rendering bug in The Witcher
by bugzilla-daemon＠freedesktop.org 19 Apr '16

19 Apr '16

https://bugs.freedesktop.org/show_bug.cgi?id=90869 Bug ID: 90869 Summary: Rendering bug in The Witcher Product: Mesa Version: git Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/r600 Assignee: dri-devel(a)lists.freedesktop.org Reporter: sa(a)whiz.se QA Contact: dri-devel(a)lists.freedesktop.org Created attachment 116318 --> https://bugs.freedesktop.org/attachment.cgi?id=116318&action=edit Screenshot of bug Hi, I'm trying to run the game The Witcher (in Wine) it has rendering errors when drawing the rain. This bug is present in both git master (78395dbf9ff429d98523f8b4a340f7188d8b4db0) and in 10.5.5. I made an apitrace of the game and it renders without problem on i965. Running the trace on r600 results in this warning: 101172: glDebugOutputCallback: Medium severity API unknown issue 1, FBO incomplete: driver marked FBO as incomplete [-1] This is on a Redwood, Radeon HD 5670 1GB. -- You are receiving this mail because: You are the assignee for the bug.

1 5

[PATCH] drm: panel: simple-panel: remove useless drm_mode_set_name
by Boris Brezillon 18 Apr '16

18 Apr '16

drm_display_mode_from_videomode() is already calling drm_mode_set_name() on the provided mode. Signed-off-by: Boris Brezillon <boris.brezillon(a)free-electrons.com> --- drivers/gpu/drm/panel/panel-simple.c | 1 - 1 file changed, 1 deletion(-) diff --git a/drivers/gpu/drm/panel/panel-simple.c b/drivers/gpu/drm/panel/panel-simple.c index 30904a9..d14b904 100644 --- a/drivers/gpu/drm/panel/panel-simple.c +++ b/drivers/gpu/drm/panel/panel-simple.c @@ -112,7 +112,6 @@ static int panel_simple_get_fixed_modes(struct panel_simple *panel) } drm_display_mode_from_videomode(&vm, mode); - drm_mode_set_name(mode); drm_mode_probed_add(connector, mode); num++; -- 1.9.1

2 2

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel January 2016