dri-devel March 2015

dri-devel@lists.freedesktop.org

196 participants
1117 discussions

[Bug 80004] New: Serious Sam 3 BFE - incorrect weapon rendering
by bugzilla-daemon＠freedesktop.org 29 May '16

29 May '16

https://bugs.freedesktop.org/show_bug.cgi?id=80004 Priority: medium Bug ID: 80004 Assignee: dri-devel(a)lists.freedesktop.org Summary: Serious Sam 3 BFE - incorrect weapon rendering Severity: normal Classification: Unclassified OS: Linux (All) Reporter: vitalif(a)yourcmc.ru Hardware: x86 (IA32) Status: NEW Version: 10.1 Component: Drivers/Gallium/r600 Product: Mesa Created attachment 101017 --> https://bugs.freedesktop.org/attachment.cgi?id=101017&action=edit Incorrect weapon rendering Hi! I try to play Serious Sam 3 BFE using Mesa and r600g driver, and I get incorrect rendering of the weapon - it's rendered "diagonal" (see the screenshot). Linux kernel is Debian's 3.14.4-1.1, but most of the system is i386. Mesa is 10.1.2 from Debian repos. Card is ATI Mobility Radeon HD 4670. OpenGL renderer string: Gallium 0.4 on AMD RV730 OpenGL core profile version string: 3.3 (Core Profile) Mesa 10.1.2 OpenGL core profile shading language version string: 3.30 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile Is it a known issue? -- You are receiving this mail because: You are the assignee for the bug.

1 12

[Bug 89254] Dota2 hangs the gpu
by bugzilla-daemon＠freedesktop.org 24 May '16

24 May '16

https://bugs.freedesktop.org/show_bug.cgi?id=89254 Bug ID: 89254 Summary: Dota2 hangs the gpu Product: Mesa Version: git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: major Priority: medium Component: Drivers/Gallium/radeonsi Assignee: dri-devel(a)lists.freedesktop.org Reporter: m.cencora(a)gmail.com QA Contact: dri-devel(a)lists.freedesktop.org Created attachment 113710 --> https://bugs.freedesktop.org/attachment.cgi?id=113710&action=edit glxinfo output Dota2 hanged gpu for me 3 times in a row after loading or rejoining a game. It wasn't crashing for other games, but only for a single one (so far). Possibly the bug is triggered by a specific custom hero outfit/effect. Attached glxinfo output and dmesg output -- You are receiving this mail because: You are the assignee for the bug.

1 6

[Bug 72307] New: [radeonsi] radeonsi_dri.so undefined symbol: setupterm
by bugzilla-daemon＠freedesktop.org 24 May '16

24 May '16

https://bugs.freedesktop.org/show_bug.cgi?id=72307 Priority: medium Bug ID: 72307 Assignee: dri-devel(a)lists.freedesktop.org Summary: [radeonsi] radeonsi_dri.so undefined symbol: setupterm Severity: normal Classification: Unclassified OS: Linux (All) Reporter: neatnoise(a)gmail.com Hardware: x86-64 (AMD64) Status: NEW Version: git Component: Drivers/Gallium/radeonsi Product: Mesa Created attachment 90220 --> https://bugs.freedesktop.org/attachment.cgi?id=90220&action=edit Xorg log Hello. I can see following errors when starting Xorg: failed to open /usr/lib64/dri/radeonsi_dri.so: /usr/lib64/dri/radeonsi_dri.so: undefined symbol: setupterm gbm: failed to open any driver (search paths /usr/lib64/dri)failed to load driver: radeonsi failed to load module: /usr/lib64/gbm/gbm_gallium_drm.so: cannot open shared object file: No such file or directory couldn't get display device Program received signal SIGSEGV, Segmentation fault. 0x000000000020e116 in ?? () OS: Gentoo User space packages: media-libs/mesa git sys-devel/llvm git x11-libs/libdrm git x11-libs/glamor git x11-drivers/xf86-video-ati git x11-base/xorg-server 1.14.3 Linux Kernel: 3.13.0-rc2 Mesa source config: ./configure --prefix=/usr --build=x86_64-pc-linux-gnu --host=x86_64-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --libdir=/usr/lib64 --disable-silent-rules --disable-dependency-tracking --enable-dri --enable-glx --enable-shared-glapi --enable-texture-float --disable-debug --enable-egl --enable-gbm --disable-gles1 --disable-gles2 --enable-glx-tls --disable-osmesa --enable-asm --without-llvm-shared-libs --with-dri-drivers=,swrast,radeon,r200 --with-gallium-drivers=,swrast,radeonsi,r300,r600 PYTHON2=/usr/bin/python2.7 --with-egl-platforms=x11,drm --enable-gallium-llvm --disable-openvg --disable-gallium-egl --enable-r600-llvm-compiler --enable-vdpau --disable-xa --disable-xvmc -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 73785] New: Team Fortress 2 causes random GPU stalls on radeonsi
by bugzilla-daemon＠freedesktop.org 24 May '16

24 May '16

https://bugs.freedesktop.org/show_bug.cgi?id=73785 Priority: medium Bug ID: 73785 Assignee: dri-devel(a)lists.freedesktop.org Summary: Team Fortress 2 causes random GPU stalls on radeonsi Severity: normal Classification: Unclassified OS: Linux (All) Reporter: xamaniqinqu(a)gmail.com Hardware: x86-64 (AMD64) Status: NEW Version: git Component: Drivers/Gallium/radeonsi Product: Mesa Created attachment 92376 --> https://bugs.freedesktop.org/attachment.cgi?id=92376&action=edit dmesg output related to the GPU stall. Overview: The game "Team Fortress 2" causes the GPU to stall randomly. The stalls sometimes resolve by themselves after ~1 min, but will occur again rapidly. Steps to reproduce: 1) Install "Team Fortress 2" through Steam ( http://store.steampowered.com/app/440/ ). 2) Start the game, join a map. 3) Play until the GPU hangs. 4) Optionally: wait until GPU recovers. Actual results: Frequent GPU stalls while playing Team Fortress 2. Sometimes video output is restored after ~1 min. Expected results: No stalls. Build date and platform: Build date of all components: 01/18/2014 Linux kernel version: 3.13-rc8 x86_64 Mesa: git (566e0ddfd01dbadd75462fed5a3f141b9f494028) LLVM: 3.5-svn (commit 199570) Additional information: I am running on a Radeon HD 7970 with DVI output at 2560x1440. Dynamic power management is enabled. Disabling Hi-Z does not alleviate the problem. The output of "dmesg 'drm\|radeon'" has been added as an attachment. I could not reproduce the issue (yet) in another Source engine title, "Left 4 Dead 2". -- You are receiving this mail because: You are the assignee for the bug.

1 18

[Bug 84327] New: crash in gnome-shell when typing in the app view
by bugzilla-daemon＠freedesktop.org 13 May '16

13 May '16

https://bugs.freedesktop.org/show_bug.cgi?id=84327 Priority: medium Bug ID: 84327 Assignee: dri-devel(a)lists.freedesktop.org Summary: crash in gnome-shell when typing in the app view Severity: normal Classification: Unclassified OS: All Reporter: rstrode(a)redhat.com Hardware: Other Status: NEW Version: unspecified Component: Drivers/Gallium/r300 Product: Mesa in gnome-shell 3.14.0 (with mutter 3.14.0) any time i type in the overview it crashes. valgrind reports this: ==6970== Thread 1: ==6970== Invalid read of size 4 ==6970== at 0x228163E9: UnknownInlinedFun (register_allocate.c:524) ==6970== by 0x228163E9: ra_allocate (register_allocate.c:555) ==6970== by 0x22AF000F: do_advanced_regalloc (radeon_pair_regalloc.c:620) ==6970== by 0x22AF000F: rc_pair_regalloc (radeon_pair_regalloc.c:776) ==6970== by 0x22AE417B: rc_run_compiler_passes (radeon_compiler.c:465) ==6970== by 0x22AE4224: rc_run_compiler (radeon_compiler.c:491) ==6970== by 0x22AF69B3: r3xx_compile_fragment_program (r3xx_fragprog.c:153) ==6970== by 0x22AD03AF: r300_translate_fragment_shader (r300_fs.c:519) ==6970== by 0x22AD1439: r300_pick_fragment_shader (r300_fs.c:597) ==6970== by 0x22ADC5F2: r300_validate_fragment_shader (r300_state_derived.c:1048) ==6970== by 0x22ADC5F2: r300_update_derived_state (r300_state_derived.c:1075) ==6970== by 0x22AD3476: r300_draw_vbo (r300_render.c:794) ==6970== by 0x22926B74: u_vbuf_draw_vbo (u_vbuf.c:1148) ==6970== by 0x227DCD5E: st_draw_vbo (st_draw.c:285) ==6970== by 0x227AF16D: vbo_draw_arrays (vbo_exec_array.c:667) ==6970== Address 0x45864d64 is 18,532 bytes inside an unallocated block of size 20,144 in arena "client" ==6970== gnome-shell: compiler/radeon_variable.c:61: rc_variable_change_dst: Assertion `new_writemask & 8' failed. COGL_DEBUG=show-source writes this to the console just before the crash: Cogl-Message: fragment shader: #version 120 #ifdef GL_ES precision highp float; #endif #define COGL_VERSION 100 uniform mat4 cogl_modelview_matrix; uniform mat4 cogl_modelview_projection_matrix; uniform mat4 cogl_projection_matrix; varying vec4 _cogl_color; #define cogl_color_in _cogl_color #define cogl_tex_coord_in _cogl_tex_coord #define cogl_color_out gl_FragColor #define cogl_depth_out gl_FragDepth #define cogl_front_facing gl_FrontFacing #define cogl_point_coord gl_PointCoord varying vec4 _cogl_tex_coord[1]; #define cogl_tex_coord0_in _cogl_tex_coord[0] /* * st-scroll-view-fade.glsl: Edge fade effect for StScrollView * * Copyright 2010 Intel Corporation. * Copyright 2011 Adel Gadllah * * This program is free software; you can redistribute it and/or modify it * under the terms and conditions of the GNU Lesser General Public License, * version 2.1, as published by the Free Software Foundation. * * This program is distributed in the hope it will be useful, but WITHOUT ANY * WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS * FOR A PARTICULAR PURPOSE. See the GNU Lesser General Public License for * more details. * * You should have received a copy of the GNU Lesser General Public License * along with this program. If not, see <http://www.gnu.org/licenses/>. */ uniform sampler2D tex; uniform float height; uniform float width; uniform float vfade_offset; uniform float hfade_offset; uniform bool fade_edges_top; uniform bool fade_edges_right; uniform bool fade_edges_bottom; uniform bool fade_edges_left; uniform vec2 fade_area_topleft; uniform vec2 fade_area_bottomright; void main () { cogl_color_out = cogl_color_in * texture2D (tex, vec2 (cogl_tex_coord_in[0].xy)); float y = height * cogl_tex_coord_in[0].y; float x = width * cogl_tex_coord_in[0].x; /* * We cannot just return here due to a bug in llvmpipe see: * https://bugzilla.freedesktop.org/show_bug.cgi?id=62357 */ if (x > fade_area_topleft[0] && x < fade_area_bottomright[0] && y > fade_area_topleft[1] && y < fade_area_bottomright[1]) { float ratio = 1.0; float fade_bottom_start = fade_area_bottomright[1] - vfade_offset; float fade_right_start = fade_area_bottomright[0] - hfade_offset; bool fade_top = y < vfade_offset && fade_edges_top; bool fade_bottom = y > fade_bottom_start && fade_edges_bottom; bool fade_left = x < hfade_offset && fade_edges_left; bool fade_right = x > fade_right_start && fade_edges_right; float vfade_scale = height / vfade_offset; if (fade_top) { ratio *= y / vfade_offset; } if (fade_bottom) { ratio *= (fade_area_bottomright[1] - y) / (fade_area_bottomright[1] - fade_bottom_start); } float hfade_scale = width / hfade_offset; if (fade_left) { ratio *= x / hfade_offset; } if (fade_right) { ratio *= (fade_area_bottomright[0] - x) / (fade_area_bottomright[0] - fade_right_start); } cogl_color_out *= ratio; } } Segmentation fault (core dumped) -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 70711] New: Audio hdmi
by bugzilla-daemon＠bugzilla.kernel.org 11 May '16

11 May '16

https://bugzilla.kernel.org/show_bug.cgi?id=70711 Bug ID: 70711 Summary: Audio hdmi Product: Drivers Version: 2.5 Kernel Version: 3.14.0-rc3 Hardware: x86-64 OS: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Video(DRI - non Intel) Assignee: drivers_video-dri(a)kernel-bugs.osdl.org Reporter: vincenzov72(a)hotmail.com Regression: No Audio hdmi not work with radeon 7750, works good with radeon 6450 -- You are receiving this mail because: You are watching the assignee of the bug.

1 17

[Bug 83461] New: hdmi screen flicker/unusable
by bugzilla-daemon＠bugzilla.kernel.org 02 May '16

02 May '16

https://bugzilla.kernel.org/show_bug.cgi?id=83461 Bug ID: 83461 Summary: hdmi screen flicker/unusable Product: Drivers Version: 2.5 Kernel Version: 3.15, 3.16 Hardware: x86-64 OS: Linux Tree: Mainline Status: NEW Severity: blocking Priority: P1 Component: Video(DRI - non Intel) Assignee: drivers_video-dri(a)kernel-bugs.osdl.org Reporter: kb(a)spatium.org Regression: No Since kernel 3.15 I cannot get a stable video output on HDMI. The screen flickers and blinks, and my dmesg is full of these: sound hdaudioC1D0: HDMI ATI/AMD: no speaker allocation for ELD The video card in question is: Advanced Micro Devices, Inc. [AMD/ATI] RS880 [Radeon HD 4200] Downgrading to 3.14 seems to remove the issue. -- You are receiving this mail because: You are watching the assignee of the bug.

1 38

[Bug 87856] Driver load fails with no error on ppc64 host
by bugzilla-daemon＠freedesktop.org 30 Apr '16

30 Apr '16

https://bugs.freedesktop.org/show_bug.cgi?id=87856 Bug ID: 87856 Summary: Driver load fails with no error on ppc64 host Product: Mesa Version: 10.2 Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/r600 Assignee: dri-devel(a)lists.freedesktop.org Reporter: freedesktopbugs(a)63bit.net Created attachment 111507 --> https://bugs.freedesktop.org/attachment.cgi?id=111507&action=edit Xorg log, dmesg | fgrep radeon, and glxinfo with LIBGL_DEBUG set I have a PowerPC G5 (ppc64 with 64-bit userland) with working KMS using a (ostensibly x86) Radeon HD4650. KMS is enabled and the kernel and Xorg parts of KMS/DRI2 appear to be attaching correctly. After X starts, running LIBGL_DEBUG=verbose glxinfo outputs the following: libGL: OpenDriver: trying /usr/lib64/dri/tls/r600_dri.so libGL: OpenDriver: trying /usr/lib64/dri/r600_dri.so libGL: driver does not expose __driDriverGetExtensions_r600(): /usr/lib64/dri/r600_dri.so: undefined symbol: __driDriverGetExtensions_r600 libGL: Can't open configuration file /root/.drirc: No such file or directory. libGL: Can't open configuration file /root/.drirc: No such file or directory. libGL error: failed to load driver: r600 libGL: OpenDriver: trying /usr/lib64/dri/tls/swrast_dri.so libGL: OpenDriver: trying /usr/lib64/dri/swrast_dri.so libGL: driver does not expose __driDriverGetExtensions_swrast(): /usr/lib64/dri/swrast_dri.so: undefined symbol: __driDriverGetExtensions_swrast libGL: Can't open configuration file /root/.drirc: No such file or directory. libGL: Can't open configuration file /root/.drirc: No such file or directory. libGL error: failed to load driver: swrast Error: couldn't find RGB GLX visual or fbconfig Error: couldn't find RGB GLX visual or fbconfig I am under the impression that the undefined symbol should not be causing problems after reading this bug: https://bugs.freedesktop.org/show_bug.cgi?id=72198 Nonetheless, glxgears will not run, and in general it appears mesa acceleration is not occurring. Mesa was compiled with support for llvm and the r600 generator. I am attaching various logs. I would be glad to test patches or hacks :) -- You are receiving this mail because: You are the assignee for the bug.

1 16

[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

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel March 2015