Re: [PATCH 1/3] drm/ttm: split BO structure initialization into a separate function

On 2017年02月14日 18:37, Nicolai Hähnle wrote: From: Nicolai Hähnle Allow callers to opt out of calling ttm_bo_validate immediately. This allows more flexibility in how locking of the reservation object is done, which is needed to fix a locking bug (destroy locked

Re: [PATCH] uapi: add missing install of dma-buf.h

Hi Denys, On 15 February 2017 at 01:30, Denys Dmytriyenko wrote: > From: Denys Dmytriyenko > > As part of c11e391da2a8fe973c3c2398452000bed505851e "dma-buf: Add ioctls to > allow userspace to flush" a new uapi header file dma-buf.h was added, but an > entry was

[Bug 99323] White horizontal lines and graphics curruption in ATI HD 4570 when radeon.dpm=1

https://bugs.freedesktop.org/show_bug.cgi?id=99323 --- Comment #12 from kartik --- Forcing dpm to high performance mode resolves the problem for now. -- You are receiving this mail because: You are the assignee for the

[PATCH v7 2/7] drm/rockchip/dsi: dw-mipi: support RK3399 mipi dsi

The vopb/vopl switch register of RK3399 mipi is different from RK3288, the default setting for mipi dsi mode is different too, so add a of_device_id structure to distinguish them, and make sure set the correct mode before mipi phy init. Signed-off-by: Chris Zhong

[PATCH v7 1/7] dt-bindings: add rk3399 support for dw-mipi-rockchip

The dw-mipi-dsi of rk3399 is almost the same as rk3288, the rk3399 has additional phy config clock. Signed-off-by: Chris Zhong Acked-by: Rob Herring --- Changes in v6: None Changes in v5: None Changes in v4: None Changes in v3: None

[PATCH v7 0/7] Rockchip dw-mipi-dsi driver

Hi all This version does not change the existing v6 patches, just to add the "bandwidth fix" patch back, since we really need it. This patch serial is for RK3399 MIPI DSI. The MIPI DSI controller of RK3399 is almost the same as RK3288, except a little bit of difference in phy clock controlling

Re: [PATCH v2 11/11] drm/rockchip/dsi: fix insufficient bandwidth of some panel

Hi John On 01/17/2017 06:54 PM, John Keeping wrote: On Tue, 17 Jan 2017 17:31:53 +0800, Chris Zhong wrote: On 01/16/2017 08:44 PM, John Keeping wrote: On Mon, 16 Jan 2017 18:08:31 +0800, Chris Zhong wrote: Set the lanes bps to 1 / 0.9 times of pclk, the margin is not enough for some

Re: [PATCH v3 23/24] drm/rockchip: dw-mipi-dsi: add reset control

Hi John On 01/29/2017 09:24 PM, John Keeping wrote: In order to fully reset the state of the MIPI controller we must assert this reset. This is slightly more complicated than it could be in order to maintain compatibility with device trees that do not specify the reset property.

Re: [PATCH] uapi: add missing install of dma-buf.h

Hi Denys, On 15 February 2017 at 01:30, Denys Dmytriyenko wrote: > From: Denys Dmytriyenko > > As part of c11e391da2a8fe973c3c2398452000bed505851e "dma-buf: Add ioctls > to > allow userspace to flush" a new uapi header file dma-buf.h was added, but > an > entry

Re: [RFC][PATCH 1/2] drm/probe-helper: Add mode_valid check to drm_crtc_helper_funcs

On Tue, Feb 14, 2017 at 4:49 PM, Daniel Vetter wrote: > On Tue, Feb 14, 2017 at 01:07:21PM -0800, John Stultz wrote: >> On Tue, Feb 14, 2017 at 12:32 PM, Daniel Stone wrote: >> > Hi John, >> > >> > On 14 February 2017 at 19:25, John Stultz

[Bug 99387] Kernel 4.9: Kaveri + Hainan choked on boot using amdgpu

https://bugs.freedesktop.org/show_bug.cgi?id=99387 --- Comment #17 from Luya Tshimbalanga --- The fix is working. Hainan video card aka Jet Pro R5 M230 successfully initialized along the Kaveri card 01:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Jet

Re: [PATCH] drm/rockchip: add extcon dependency for DP

On 2017年02月15日 05:31, Arnd Bergmann wrote: The newly added DP driver links against the extcon core, which fails when extcon is a module and this driver is not: drivers/gpu/drm/rockchip/cdn-dp-core.o: In function `cdn_dp_get_port_lanes': cdn-dp-core.c:(.text.cdn_dp_get_port_lanes+0x24):

[drm-intel:drm-intel-next-queued 11/59] drivers/gpu/drm/i915/selftests/i915_mock_selftests.h:11: warning: missing braces around initializer

tree: git://anongit.freedesktop.org/drm-intel drm-intel-next-queued head: d892e9398ecf6defc7972a62227b77dad6be20bd commit: 953c7f82eb890085c60dbe22578e883d6837c674 [11/59] drm/i915: Provide a hook for selftests config: x86_64-randconfig-s1-02150712 (attached as .config) compiler: gcc-4.4

Re: [PATCH 1/3] drm/ttm: split BO structure initialization into a separate function

On 14.02.2017 11:49, Christian König wrote: Am 14.02.2017 um 11:37 schrieb Nicolai Hähnle: From: Nicolai Hähnle Allow callers to opt out of calling ttm_bo_validate immediately. This allows more flexibility in how locking of the reservation object is done, which is

[PATCH] uapi: add missing install of dma-buf.h

From: Denys Dmytriyenko As part of c11e391da2a8fe973c3c2398452000bed505851e "dma-buf: Add ioctls to allow userspace to flush" a new uapi header file dma-buf.h was added, but an entry was not added on Kbuild to install it. This patch resolves this omission so that "make

Re: [PATCH] drm/rockchip: add extcon dependency for DP

On Tue, Feb 14, 2017 at 1:31 PM, Arnd Bergmann wrote: > The newly added DP driver links against the extcon core, which fails when > extcon is a module and this driver is not: > > drivers/gpu/drm/rockchip/cdn-dp-core.o: In function `cdn_dp_get_port_lanes': >

Re: [PATCH v2 5/6] drm: convert drivers to use drm_of_find_panel_or_bridge

On Mon, Feb 13, 2017 at 1:47 AM, Boris Brezillon wrote: > On Thu, 9 Feb 2017 13:05:57 -0600 > Rob Herring wrote: > >> Similar to the previous commit, convert drivers open coding OF graph >> parsing to use drm_of_find_panel_or_bridge instead.

Re: [Intel-gfx] [PATCH v3 7/8] drm: Connector helper function to release resources

On Tue, 2017-02-14 at 20:51 +0100, Daniel Vetter wrote: > On Mon, Feb 13, 2017 at 10:26 PM, Pandiyan, Dhinakaran > wrote: > > On Mon, 2017-02-13 at 09:05 +, Lankhorst, Maarten wrote: > >> Pandiyan, Dhinakaran schreef op do 09-02-2017 om 18:55 [+]: > >> > On

Re: [PATCH v2 3/6] drm: of: introduce drm_of_find_panel_or_bridge

On Sun, Feb 12, 2017 at 10:47 PM, Archit Taneja wrote: > > > On 02/10/2017 12:35 AM, Rob Herring wrote: >> >> Many drivers have a common pattern of searching the OF graph for either an >> attached panel or bridge and then finding the DRM struct for the panel >> or bridge.

Re: [PATCH 0/8] Refactor DC atomic commit and gamma

On 2017-02-14 04:30 PM, Daniel Vetter wrote: On Fri, Feb 10, 2017 at 11:26:22AM -0500, Harry Wentland wrote: Resending with CC to dri-devel as per Alex's suggestions. This might be of interest to a wider audience. These patches are first steps of addressing some of the problems in DC's atomic

Re: [Intel-gfx] [PATCH] drm: Reduce EDID warnings from DRM_ERROR to DRM_NOTE

On Tue, Feb 14, 2017 at 09:43:45PM +, Chris Wilson wrote: > On Tue, Feb 14, 2017 at 10:36:09PM +0100, Daniel Vetter wrote: > > On Mon, Feb 13, 2017 at 12:17:27PM -0500, Sean Paul wrote: > > > On Mon, Feb 13, 2017 at 3:59 AM, Chris Wilson > > > wrote: > > > > On Mon,

[Bug 194579] AMDGPU: Possible size overflow detected by PaX in ttm_bo_handle_move_mem (drivers/gpu/drm/ttm/ttm_bo.c:388)

https://bugzilla.kernel.org/show_bug.cgi?id=194579 --- Comment #6 from PaX Team (pagee...@freemail.hu) --- ``` (In reply to Christian König from comment #4) > Now back to topic, what code base is this? Could you post the branch > you are using somewhere? it's vanilla 4.9.9 + grsecurity (we don't

[Bug 99542] vdpau logging errors since gallium/radeon: adjust the rule for using the LINEAR_ALIGNED layout

https://bugs.freedesktop.org/show_bug.cgi?id=99542 Kai changed: What|Removed |Added Status|NEW |RESOLVED

Re: [PATCH v2 7/7] drm: Rename connector list iterator API

On Fri, Feb 10, 2017 at 06:48:06PM +0100, Thierry Reding wrote: > On Fri, Feb 10, 2017 at 06:14:14PM +0100, Thierry Reding wrote: > [...] > > /** > > - * drm_connector_list_iter_get - initialize a connector_list iterator > > + * drm_connector_list_iter_begin - initialize a connector_list iterator

Re: [RFC][PATCH 1/2] drm/probe-helper: Add mode_valid check to drm_crtc_helper_funcs

On Tue, Feb 14, 2017 at 01:07:21PM -0800, John Stultz wrote: > On Tue, Feb 14, 2017 at 12:32 PM, Daniel Stone wrote: > > Hi John, > > > > On 14 February 2017 at 19:25, John Stultz wrote: > >> +static enum drm_mode_status > >>

Re: [Intel-gfx] [PATCH] drm: Reduce EDID warnings from DRM_ERROR to DRM_NOTE

On Tue, Feb 14, 2017 at 10:36:09PM +0100, Daniel Vetter wrote: > On Mon, Feb 13, 2017 at 12:17:27PM -0500, Sean Paul wrote: > > On Mon, Feb 13, 2017 at 3:59 AM, Chris Wilson > > wrote: > > > On Mon, Feb 13, 2017 at 08:41:10AM +0100, Thierry Reding wrote: > > >> On Fri,

Re: [RFC][PATCH 1/2] drm/probe-helper: Add mode_valid check to drm_crtc_helper_funcs

On Tue, Feb 14, 2017 at 01:03:27PM -0800, John Stultz wrote: > On Tue, Feb 14, 2017 at 12:22 PM, Daniel Vetter wrote: > > On Tue, Feb 14, 2017 at 11:45:54AM -0800, John Stultz wrote: > >> > >> Not following here. What do you mean by "put it into drivers"? Where? > > > > In your

Re: [Intel-gfx] [PATCH RESEND] drm/dp/mst: fix kernel oops when turning off secondary monitor

On Tue, Feb 14, 2017 at 02:49:21PM +0200, Jani Nikula wrote: > From: Pierre-Louis Bossart > > 100% reproducible issue found on SKL SkullCanyon NUC with two external > DP daisy-chained monitors in DP/MST mode. When turning off or changing > the input of the

Re: [Intel-gfx] [PATCH] drm: Reduce EDID warnings from DRM_ERROR to DRM_NOTE

On Mon, Feb 13, 2017 at 12:17:27PM -0500, Sean Paul wrote: > On Mon, Feb 13, 2017 at 3:59 AM, Chris Wilson > wrote: > > On Mon, Feb 13, 2017 at 08:41:10AM +0100, Thierry Reding wrote: > >> On Fri, Feb 10, 2017 at 07:59:13PM +, Chris Wilson wrote: > >> > The warnings

Re: [PATCH v2] drm/atmel-hlcdc: Simplify the HLCDC layer logic

On Fri, Feb 10, 2017 at 07:07:45PM +0100, Boris Brezillon wrote: > An HLCDC layers in Atmel's nomenclature is either a DRM plane or a 'Post > Processing Layer' which can be used to output the results of the HLCDC > composition in a memory buffer. > > atmel_hlcdc_layer.c was designed to be generic

[PATCH] drm/rockchip: add extcon dependency for DP

The newly added DP driver links against the extcon core, which fails when extcon is a module and this driver is not: drivers/gpu/drm/rockchip/cdn-dp-core.o: In function `cdn_dp_get_port_lanes': cdn-dp-core.c:(.text.cdn_dp_get_port_lanes+0x24): undefined reference to `extcon_get_state'

Re: [PATCH 0/8] Refactor DC atomic commit and gamma

On Fri, Feb 10, 2017 at 11:26:22AM -0500, Harry Wentland wrote: > Resending with CC to dri-devel as per Alex's suggestions. This > might be of interest to a wider audience. > > These patches are first steps of addressing some of the problems > in DC's atomic implementation. Please take a look and

Re: [PATCH v2 1/2] drm/cma-helper: Add multi buffer support for cma fbdev

Hi Daniel, On Tuesday 14 Feb 2017 21:09:51 Daniel Vetter wrote: > On Mon, Feb 13, 2017 at 11:20:51AM +, Daniel Stone wrote: > > On 13 February 2017 at 10:54, Maxime Ripard wrote: > >> On Sun, Feb 12, 2017 at 02:28:11PM +0200, Laurent Pinchart wrote: > >>> On Thursday 02 Feb 2017 11:31:56

Re: [RFC][PATCH 1/2] drm/probe-helper: Add mode_valid check to drm_crtc_helper_funcs

On Tue, Feb 14, 2017 at 12:32 PM, Daniel Stone wrote: > Hi John, > > On 14 February 2017 at 19:25, John Stultz wrote: >> +static enum drm_mode_status >> +drm_connector_check_crtc_modes(struct drm_connector *connector, >> +

Re: [RFC][PATCH 1/2] drm/probe-helper: Add mode_valid check to drm_crtc_helper_funcs

On Tue, Feb 14, 2017 at 12:22 PM, Daniel Vetter wrote: > On Tue, Feb 14, 2017 at 11:45:54AM -0800, John Stultz wrote: >> >> Not following here. What do you mean by "put it into drivers"? Where? > > In your driver callback for ->mode_valid, call into a shared function to >

Re: [PATCH] drm/nouveau/core: recognise GP107 chipset

I believe what's missing at this point is a mmiotrace of the NVIDIA driver to make sure that there's nothing different about this GPU. If you can make one (see https://wiki.ubuntu.com/X/MMIOTracing for a guide - should end up ~100MB uncompressed), please send a compressed one to

Re: [RFC][PATCH 1/2] drm/probe-helper: Add mode_valid check to drm_crtc_helper_funcs

Hi John, On 14 February 2017 at 19:25, John Stultz wrote: > +static enum drm_mode_status > +drm_connector_check_crtc_modes(struct drm_connector *connector, > + struct drm_display_mode *mode) > +{ > + struct drm_device *dev =

Re: [RFC][PATCH 1/2] drm/probe-helper: Add mode_valid check to drm_crtc_helper_funcs

On Tue, Feb 14, 2017 at 11:45:54AM -0800, John Stultz wrote: > On Tue, Feb 14, 2017 at 11:38 AM, Daniel Vetter wrote: > > On Tue, Feb 14, 2017 at 8:25 PM, John Stultz wrote: > >> Currently, on the hikey board, we have the adv7511 bridge wired > >> up to

Re: [PATCH] drm: ensure atomic messages consistently include the name of the component

On Mon, Feb 13, 2017 at 04:47:01PM +, Russell King - ARM Linux wrote: > On Mon, Feb 13, 2017 at 02:37:31PM +0100, Maarten Lankhorst wrote: > > All for it, looks sane. The last hunk fails to apply because it's based on > > an older version of page_flip, but easy enough to fix. > > Yes, it's

[Bug 99815] Power management problems & kernel hangs with Cap Verde

https://bugs.freedesktop.org/show_bug.cgi?id=99815 --- Comment #1 from Klaus Kusche --- I just checked: It seems that the problem does not depend on two active outputs. The gpu consumes roughly the same amount of power with just the laptop display. -- You are

Re: [PATCH -next] drm/msm/dsi: fix error return code in msm_dsi_host_init()

On Thu, Feb 09, 2017 at 03:19:07PM +, Wei Yongjun wrote: > From: Wei Yongjun > > Fix to return error code -ENOMEM from the malloc error handling > case instead of 0, as done elsewhere in this function. > > Signed-off-by: Wei Yongjun Applied

Re: [PATCH 2/6] drm: Introduce drm_mode_object_{get,put}()

On Thu, Feb 09, 2017 at 09:55:22PM +, Emil Velikov wrote: > On 9 February 2017 at 20:41, Thierry Reding wrote: > > On Thu, Feb 09, 2017 at 06:08:10PM +0100, Daniel Vetter wrote: > >> On Wed, Feb 08, 2017 at 02:28:14PM -0500, Sean Paul wrote: > >> > On Wed, Feb 08,

Re: [PATCH v2 1/2] drm/cma-helper: Add multi buffer support for cma fbdev

On Mon, Feb 13, 2017 at 11:20:51AM +, Daniel Stone wrote: > Hi Maxime, > > On 13 February 2017 at 10:54, Maxime Ripard > wrote: > > On Sun, Feb 12, 2017 at 02:28:11PM +0200, Laurent Pinchart wrote: > >> On Thursday 02 Feb 2017 11:31:56 Maxime Ripard wrote: >

Re: [PATCH v3 3/7] drm/atomic: Use new atomic iterator macros.

Hi Daniel, On Tuesday 14 Feb 2017 21:03:07 Daniel Vetter wrote: > On Tue, Jan 17, 2017 at 01:55:50AM +0200, Laurent Pinchart wrote: > > On Monday 16 Jan 2017 10:37:40 Maarten Lankhorst wrote: > > > > Could we please get a description ? Apart from that, > > Typed something small and merged the

Re: [PATCH] drm: change connector disconnected debug message to an error

On Fri, Feb 10, 2017 at 09:29:07AM -0700, Shuah Khan wrote: > On 02/03/2017 01:06 AM, Daniel Vetter wrote: > > On Thu, Feb 02, 2017 at 10:25:44AM -0700, Shuah Khan wrote: > >> On 02/02/2017 01:32 AM, Jani Nikula wrote: > >>> On Thu, 02 Feb 2017, Shuah Khan wrote: >

Re: [PATCH v3 3/7] drm/atomic: Use new atomic iterator macros.

On Tue, Jan 17, 2017 at 01:55:50AM +0200, Laurent Pinchart wrote: > Hi Maarten, > > Thank you for the patch. > > On Monday 16 Jan 2017 10:37:40 Maarten Lankhorst wrote: > > Could we please get a description ? Apart from that, Typed something small and merged the first 3 patches from this

Re: [RFC simple allocator v2 1/2] Create Simple Allocator module

Hi Daniel, On Tuesday 14 Feb 2017 20:44:44 Daniel Vetter wrote: > On Tue, Feb 14, 2017 at 8:39 PM, Laurent Pinchart wrote: > > On Tuesday 14 Feb 2017 20:33:58 Daniel Vetter wrote: > >> On Mon, Feb 13, 2017 at 3:45 PM, Benjamin Gaignard wrote: > >>> This is the core of simple allocator module. >

Re: [PATCH v4 1/7] drm: Add DRM support for tiny LCD displays

On Sun, Feb 12, 2017 at 2:57 PM, Noralf Trønnes wrote: > tinydrm will be merged the way it is now, unless someone points to > something that is broken. But I collect your comments for a later > cleanup patchset. It takes a lot of effort for me as an amateur to > keeps this

Re: [RFC][PATCH 1/2] drm/probe-helper: Add mode_valid check to drm_crtc_helper_funcs

On Tue, Feb 14, 2017 at 08:38:40PM +0100, Daniel Vetter wrote: > On Tue, Feb 14, 2017 at 8:25 PM, John Stultz wrote: > > Currently, on the hikey board, we have the adv7511 bridge wired > > up to the kirin ade drm driver. Unfortunately, the kirin ade > > core cannot

Re: [Intel-gfx] [PATCH v3 7/8] drm: Connector helper function to release resources

On Mon, Feb 13, 2017 at 10:26 PM, Pandiyan, Dhinakaran wrote: > On Mon, 2017-02-13 at 09:05 +, Lankhorst, Maarten wrote: >> Pandiyan, Dhinakaran schreef op do 09-02-2017 om 18:55 [+]: >> > On Thu, 2017-02-09 at 09:01 +, Lankhorst, Maarten wrote: >> > >

Re: [RFC][PATCH 1/2] drm/probe-helper: Add mode_valid check to drm_crtc_helper_funcs

On Tue, Feb 14, 2017 at 11:38 AM, Daniel Vetter wrote: > On Tue, Feb 14, 2017 at 8:25 PM, John Stultz wrote: >> Currently, on the hikey board, we have the adv7511 bridge wired >> up to the kirin ade drm driver. Unfortunately, the kirin ade >> core cannot

Re: [RFC simple allocator v2 1/2] Create Simple Allocator module

On Tue, Feb 14, 2017 at 8:39 PM, Laurent Pinchart wrote: > Hi Daniel, > > On Tuesday 14 Feb 2017 20:33:58 Daniel Vetter wrote: >> On Mon, Feb 13, 2017 at 3:45 PM, Benjamin Gaignard wrote: >> > This is the core of simple allocator module. >> > It aim to offert

Re: [RFC simple allocator v2 1/2] Create Simple Allocator module

Hi Daniel, On Tuesday 14 Feb 2017 20:33:58 Daniel Vetter wrote: > On Mon, Feb 13, 2017 at 3:45 PM, Benjamin Gaignard wrote: > > This is the core of simple allocator module. > > It aim to offert one common ioctl to allocate specific memory. > > > > version 2: > > - rebased on 4.10-rc7 > > > >

Re: [RFC][PATCH 1/2] drm/probe-helper: Add mode_valid check to drm_crtc_helper_funcs

On Tue, Feb 14, 2017 at 8:25 PM, John Stultz wrote: > Currently, on the hikey board, we have the adv7511 bridge wired > up to the kirin ade drm driver. Unfortunately, the kirin ade > core cannot generate accurate byteclocks for all pixel clock > values. > > Thus if a mode

[PATCH] drm/nouveau/core: recognise GP107 chipset

From: Chris Chiu This new graphics card was failing to initialize with nouveau due to an "unknown chipset" error. Copy the GP106 configuration and rename for GP107/NV137. We don't know for certain that this is fully correct, but brief desktop testing suggests this is working

Re: [RFC simple allocator v2 1/2] Create Simple Allocator module

On Mon, Feb 13, 2017 at 3:45 PM, Benjamin Gaignard wrote: > This is the core of simple allocator module. > It aim to offert one common ioctl to allocate specific memory. > > version 2: > - rebased on 4.10-rc7 > > Signed-off-by: Benjamin Gaignard

[Bug 99275] Kernel 4.9: amdgpu regression; gui flickers; amd radeon rx 460

https://bugs.freedesktop.org/show_bug.cgi?id=99275 --- Comment #33 from Reimar Imhof --- (In reply to Michel Dänzer from comment #27) > (In reply to Reimar Imhof from comment #26) > > Together with comment #24 there is a render bug in kernel 4.8 that shows up > > at

Re: [RFC simple allocator v2 1/2] Create Simple Allocator module

Hi Benjamin, Thank you for the patch. I've CC'ed the linux-api mailing list. On Monday 13 Feb 2017 15:45:05 Benjamin Gaignard wrote: > This is the core of simple allocator module. > It aim to offert one common ioctl to allocate specific memory. > > version 2: > - rebased on 4.10-rc7 > >

[RFC][PATCH 0/2] Add mode_valid drm_crtc_helper_funcs for HiKey

Currently, on the hikey board, we have the adv7511 bridge wired up to the kirin ade drm driver. Unfortunately, the kirin ade core cannot generate accurate byteclocks for all pixel clock values. Thus if a mode clock is selected that we cannot calculate a matching byteclock, the device will boot

[RFC][PATCH 1/2] drm/probe-helper: Add mode_valid check to drm_crtc_helper_funcs

Currently, on the hikey board, we have the adv7511 bridge wired up to the kirin ade drm driver. Unfortunately, the kirin ade core cannot generate accurate byteclocks for all pixel clock values. Thus if a mode clock is selected that we cannot calculate a matching byteclock, the device will boot

[RFC][PATCH 2/2] drm: kirin: Restrict modes to known good mode clocks

Currently the hikey dsi logic cannot generate accurate byte clocks values for all pixel clock values. Thus if a mode clock is selected that cannot match the calculated byte clock, the device will boot with a blank screen. This patch uses the new mode_valid callback to enforces known good mode

[Bug 98784] Talos Principle rendering flickering garbage on start instead of its logo and loading squares

https://bugs.freedesktop.org/show_bug.cgi?id=98784 --- Comment #16 from Torbjörn Andersson --- I can't reproduce the glitch any more. Perhaps today's update of the game fixed it? -- You are receiving this mail because: You are the assignee for the

[Bug 65968] Massive memory corruption in Planetary Annihilation Alpha

https://bugs.freedesktop.org/show_bug.cgi?id=65968 Andreas Ringlstetter changed: What|Removed |Added Status|NEW

Re: [PATCH] drm/amd/dc: hw_sequencer: fix semicolon.cocci warnings

Reviewed-by: Harry Wentland Harry On 2017-02-14 01:19 AM, Julia Lawall wrote: Remove unneeded semicolon. Generated by: scripts/coccinelle/misc/semicolon.cocci CC: Harry Wentland Signed-off-by: Julia Lawall

[Bug 98869] Electronic Super Joy graphic artefacts (regression,bisected)

https://bugs.freedesktop.org/show_bug.cgi?id=98869 --- Comment #25 from cosiek...@o2.pl --- I can do more testing if needed. -- You are receiving this mail because: You are the assignee for the bug.___ dri-devel mailing list

Re: [PATCH] drm/amd/dc: fix semicolon.cocci warnings

Reviewed-by: Harry Wentland Harry On 2017-02-14 01:13 AM, Julia Lawall wrote: Remove unneeded semicolons. Generated by: scripts/coccinelle/misc/semicolon.cocci CC: Harry Wentland Signed-off-by: Julia Lawall

Re: [PATCH] drm/amd/dc: fix semicolon.cocci warnings

Reviewed-by: Harry Wentland Harry On 2017-02-14 01:14 AM, Julia Lawall wrote: Remove unneeded semicolon. Generated by: scripts/coccinelle/misc/semicolon.cocci CC: Harry Wentland Signed-off-by: Julia Lawall

Re: [PATCH v2] drm/amd/dc: resource: fix semicolon.cocci warnings (fwd)

Thanks for these fixes. I'll merge them. Reviewed-by: Harry Wentland Harry On 2017-02-14 04:47 AM, Christian König wrote: Am 14.02.2017 um 07:21 schrieb Julia Lawall: Remove unneeded semicolon. Generated by: scripts/coccinelle/misc/semicolon.cocci CC: Harry

[Bug 99801] Rx480 doesn't output properly onto z27q at 5120x2880

https://bugs.freedesktop.org/show_bug.cgi?id=99801 --- Comment #12 from Harry Wentland --- We're currently debugging an issue that looks very similar, if not the same. It's also with a 5k display with two DP input but on a different platform. The display pipe driving one

[Bug 99815] Power management problems & kernel hangs with Cap Verde

https://bugs.freedesktop.org/show_bug.cgi?id=99815 Bug ID: 99815 Summary: Power management problems & kernel hangs with Cap Verde Product: DRI Version: unspecified Hardware: Other OS: Linux (All)

Re: [RFC simple allocator v2 0/2] Simple allocator

On Mon, Feb 13, 2017 at 11:01:14AM -0800, Laura Abbott wrote: > On 02/13/2017 10:18 AM, Mark Brown wrote: > > The software defined networking people seemed to think they had a use > > case for this as well. They're not entirely upstream of course but > > still... > This is the first I've heard

Re: [PATCH v4 5/7] dt-bindings: display/panel: Add common rotation property

On Sat, Feb 11, 2017 at 12:48 PM, Noralf Trønnes wrote: > Display panels can be oriented many ways, especially in the embedded > world. The rotation property is a way to describe this orientation. > The counter clockwise direction is chosen because that's what fbdev > and drm

[Bug 99275] Kernel 4.9: amdgpu regression; gui flickers; amd radeon rx 460

https://bugs.freedesktop.org/show_bug.cgi?id=99275 --- Comment #32 from alvarex --- I'm sorry but I can't find a consistent way of reproducing the bug. I presumed that with 4.9 the bug will still be there but right now, no matter how hard I try I cannot reproduce

[Bug 194559] amdgpu problems loading 2 firmwares on multi-smp system

https://bugzilla.kernel.org/show_bug.cgi?id=194559 Christian König (deathsim...@vodafone.de) changed: What|Removed |Added CC|

[Bug 194579] AMDGPU: Possible size overflow detected by PaX in ttm_bo_handle_move_mem (drivers/gpu/drm/ttm/ttm_bo.c:388)

https://bugzilla.kernel.org/show_bug.cgi?id=194579 --- Comment #5 from fin4...@hotmail.com --- (In reply to Christian König from comment #3) > Please ignore the incorrect comment by fin4...@hotmail.com. > > The upstream kernel the official base amdgpu driver code. Only a few not > parts which

[Bug 194559] amdgpu problems loading 2 firmwares on multi-smp system

https://bugzilla.kernel.org/show_bug.cgi?id=194559 --- Comment #7 from fin4...@hotmail.com --- (In reply to Michel Dänzer from comment #6) > (In reply to fin4478 from comment #5) > > This and many other amdgpu bug reports prove my point. > > Your bug report comments like this one rather indicate

Re: [PATCH] dma-buf/fence: Avoid use of uninitialised timestamp

On Tue, Feb 14, 2017 at 12:22:02PM -0200, Gustavo Padovan wrote: > 2017-02-14 Chris Wilson : > > > On Tue, Feb 14, 2017 at 11:40:38AM -0200, Gustavo Padovan wrote: > > > Hi Chris, > > > > > > 2017-02-14 Chris Wilson : > > One thing that occurs

Re: [PATCH] dma-buf/fence: Avoid use of uninitialised timestamp

2017-02-14 Chris Wilson : > On Tue, Feb 14, 2017 at 11:40:38AM -0200, Gustavo Padovan wrote: > > Hi Chris, > > > > 2017-02-14 Chris Wilson : > > > diff --git a/drivers/dma-buf/sync_debug.c b/drivers/dma-buf/sync_debug.c > > > index

[drm-intel:drm-intel-next-queued 31/59] drivers/gpu/drm/i915/selftests/i915_gem_coherency.c:274: error: 'err' may be used uninitialized in this function

tree: git://anongit.freedesktop.org/drm-intel drm-intel-next-queued head: d892e9398ecf6defc7972a62227b77dad6be20bd commit: 170594502cf591fd0789d7e5239937b1a87af4c6 [31/59] drm/i915: Test coherency of and barriers between cache domains config: x86_64-randconfig-s2-02141638 (attached as

Re: [PATCH] drm/ttm: make TTM_MAX_BO_PRIORITY unsigned

Am 14.02.2017 um 13:25 schrieb Nicolai Hähnle: From: Nicolai Hähnle Fix a warning about different types in min() macro in amdgpu: In file included from ./include/linux/list.h:8:0, from drivers/gpu/drm/amd/amdgpu/amdgpu_object.c:32:

[Bug 99275] Kernel 4.9: amdgpu regression; gui flickers; amd radeon rx 460

https://bugs.freedesktop.org/show_bug.cgi?id=99275 --- Comment #31 from alvarex --- I will try to git bisect but last time I tried bisecting the kernel I failed miserably and it failed compiling several times. -- You are receiving this mail because: You are the

Re: [PATCH] dma-buf/fence: Avoid use of uninitialised timestamp

On Tue, Feb 14, 2017 at 11:40:38AM -0200, Gustavo Padovan wrote: > Hi Chris, > > 2017-02-14 Chris Wilson : > > diff --git a/drivers/dma-buf/sync_debug.c b/drivers/dma-buf/sync_debug.c > > index c769dc653b34..bfead12390f2 100644 > > --- a/drivers/dma-buf/sync_debug.c > >

Re: [PATCH] dma-buf/fence: Avoid use of uninitialised timestamp

Hi Chris, 2017-02-14 Chris Wilson : > [ 236.821534] WARNING: kmemcheck: Caught 64-bit read from uninitialized > memory (8802538683d0) > [ 236.828642] > 42001e7f0008 > [ 236.839543] i i i i u u u u i i i i i i

Re: [PATCH 1/2] drm/ttm: never add BO that failed to validate to the LRU list

Am 14.02.2017 um 12:37 schrieb Nicolai Hähnle: On 14.02.2017 11:38, Christian König wrote: Am 14.02.2017 um 10:18 schrieb Nicolai Hähnle: From: Nicolai Hähnle Fixes a potential race condition in amdgpu that looks as follows: Task 1: attempt ttm_bo_init, but

Re: [PATCH 1/3] drm/ttm: split BO structure initialization into a separate function

Am 14.02.2017 um 13:00 schrieb Nicolai Hähnle: On 14.02.2017 11:49, Christian König wrote: Am 14.02.2017 um 11:37 schrieb Nicolai Hähnle: From: Nicolai Hähnle Allow callers to opt out of calling ttm_bo_validate immediately. This allows more flexibility in how locking

[PATCH RESEND] drm/dp/mst: fix kernel oops when turning off secondary monitor

From: Pierre-Louis Bossart 100% reproducible issue found on SKL SkullCanyon NUC with two external DP daisy-chained monitors in DP/MST mode. When turning off or changing the input of the second monitor the machine stops with a kernel oops. This issue happened

[PATCH] dma-buf/fence: Avoid use of uninitialised timestamp

[ 236.821534] WARNING: kmemcheck: Caught 64-bit read from uninitialized memory (8802538683d0) [ 236.828642] 42001e7f0008 [ 236.839543] i i i i u u u u i i i i i i i i u u u u u u u u u u u u u u u u [ 236.850420]

[drm-intel:drm-intel-next-queued 23/59] drivers/gpu/drm/i915/selftests/i915_gem_request.c:280: error: 'request' may be used uninitialized in this function

tree: git://anongit.freedesktop.org/drm-intel drm-intel-next-queued head: d892e9398ecf6defc7972a62227b77dad6be20bd commit: b348090d6758cc391dc91f8a8233b18f0acc8458 [23/59] drm/i915: Simple selftest to exercise live requests config: x86_64-randconfig-s2-02141638 (attached as .config) compiler:

[PATCH] drm/ttm: make TTM_MAX_BO_PRIORITY unsigned

From: Nicolai Hähnle Fix a warning about different types in min() macro in amdgpu: In file included from ./include/linux/list.h:8:0, from drivers/gpu/drm/amd/amdgpu/amdgpu_object.c:32: drivers/gpu/drm/amd/amdgpu/amdgpu_object.c: In function

Re: [PATCH -next] drm/bridge/tfp410: Make symbol tfp410_platform_driver static

On 2/9/2017 8:55 PM, Wei Yongjun wrote: From: Wei Yongjun Fixes the following sparse warning: drivers/gpu/drm/bridge/ti-tfp410.c:223:24: warning: symbol 'tfp410_platform_driver' was not declared. Should it be static? This was queued to drm-misc-next Thanks,

[Bug 99484] Crusader Kings 2 - Loading bars, siege bars, morale bars, etc. do not render correctly

https://bugs.freedesktop.org/show_bug.cgi?id=99484 --- Comment #6 from Andreas Boll --- (In reply to Timothy Arceri from comment #5) > Running Mesa master with llvm 3.8 (instead of 5.0 from git) resolves the > problem. Be aware that llvm 3.8 degrades OpenGL support

[Bug 65968] Massive memory corruption in Planetary Annihilation Alpha

https://bugs.freedesktop.org/show_bug.cgi?id=65968 --- Comment #11 from Timothy Arceri --- The game runs (mostly fine on) i965, and a trace from i965 seem to run without issue on radeonsi. However running the radeonsi trace on the nvidia blob results in the same

[Bug 99275] Kernel 4.9: amdgpu regression; gui flickers; amd radeon rx 460

https://bugs.freedesktop.org/show_bug.cgi?id=99275 --- Comment #30 from alvarex --- it happens really fast for a fraction of a second and then it draws correctly, I had to record the desktop and play the video in slow motion to take the screenshot. And it's random

[Bug 99275] Kernel 4.9: amdgpu regression; gui flickers; amd radeon rx 460

https://bugs.freedesktop.org/show_bug.cgi?id=99275 --- Comment #29 from alvarex --- Hi I think I ve run into the same issue. I'm not quite sure. Firefox and other elements sometimes present artifacts, and as Reimar suggests with kernel 4.8 it doesn't happen. RX460

[Bug 99275] Kernel 4.9: amdgpu regression; gui flickers; amd radeon rx 460

https://bugs.freedesktop.org/show_bug.cgi?id=99275 --- Comment #28 from alvarex --- Created attachment 129582 --> https://bugs.freedesktop.org/attachment.cgi?id=129582=edit artifacts on radeon rx460 -- You are receiving this mail because: You are the assignee

[Bug 99484] Crusader Kings 2 - Loading bars, siege bars, morale bars, etc. do not render correctly

https://bugs.freedesktop.org/show_bug.cgi?id=99484 --- Comment #5 from Timothy Arceri --- Running Mesa master with llvm 3.8 (instead of 5.0 from git) resolves the problem. -- You are receiving this mail because: You are the assignee for the

Re: [drm-intel:drm-intel-next-queued 11/59] drivers/gpu/drm/i915/selftests/i915_mock_selftests.h:11: error: unknown field 'mock' specified in initializer

On Tue, Feb 14, 2017 at 06:32:17PM +0800, kbuild test robot wrote: > tree: git://anongit.freedesktop.org/drm-intel drm-intel-next-queued > head: d892e9398ecf6defc7972a62227b77dad6be20bd > commit: 953c7f82eb890085c60dbe22578e883d6837c674 [11/59] drm/i915: Provide a > hook for selftests >

Re: [PATCH 1/3] drm/ttm: split BO structure initialization into a separate function

Am 14.02.2017 um 11:37 schrieb Nicolai Hähnle: From: Nicolai Hähnle Allow callers to opt out of calling ttm_bo_validate immediately. This allows more flexibility in how locking of the reservation object is done, which is needed to fix a locking bug (destroy locked

Re: [PATCH 1/2] drm/ttm: never add BO that failed to validate to the LRU list

On 14.02.2017 11:38, Christian König wrote: Am 14.02.2017 um 10:18 schrieb Nicolai Hähnle: From: Nicolai Hähnle Fixes a potential race condition in amdgpu that looks as follows: Task 1: attempt ttm_bo_init, but ttm_bo_validate fails Task 1: add BO to global list

Re: [PATCH 1/2] drm/ttm: never add BO that failed to validate to the LRU list

Am 14.02.2017 um 10:18 schrieb Nicolai Hähnle: From: Nicolai Hähnle Fixes a potential race condition in amdgpu that looks as follows: Task 1: attempt ttm_bo_init, but ttm_bo_validate fails Task 1: add BO to global list anyway Task 2: grabs hold of the BO, waits on its

  1   2   >