[Bug 104762] Various segfaults/problems in qt/plasma

https://bugs.freedesktop.org/show_bug.cgi?id=104762 --- Comment #6 from Dieter Nützel --- Tested-by: Dieter Nützel I got it since the commit went in. Deleting both like Mike suggested worked here since that time, too. I ignored it 'cause I thought

Re: [PATCH] drm/pl111: Use max memory bandwidth for resolution

Linus Walleij writes: > We were previously selecting 1024x768 and 32BPP as the default > set-up for the PL111 consumers. > > This does not work on elder systems: the device tree bindings > support a property "max-memory-bandwidth" in bytes/second that > states that if

[git pull] drm vc4 fixes for 4.15

Hi Linus, Just got two vc4 fixes for a NULL ptr and misrendering issues, don't think I'll have anything else ths week, tomorrow is a public holiday here. Dave. The following changes since commit 0c5b9b5d9adbad4b60491f9ba0d2af38904bb4b9: Linux 4.15-rc9 (2018-01-21 13:51:26 -0800) are

[Bug 104762] Various segfaults/problems in qt/plasma

https://bugs.freedesktop.org/show_bug.cgi?id=104762 --- Comment #5 from Timothy Arceri --- Created attachment 136950 --> https://bugs.freedesktop.org/attachment.cgi?id=136950=edit possible fix I wasn't able to reproduce the issue, but can you give this patch a try? --

Re: [PULL] drm-misc-fixes for 4.15

On Wed, Jan 24, 2018, 8:13 PM Daniel Vetter wrote: > On Wed, Jan 24, 2018 at 7:54 PM, Sean Paul wrote: > > > > Hi Dave, > > I'm sending this since danvet is down under this week. We've collected a > couple > > fixes in drm-misc-fixes this week, and

Re: [PULL] drm-misc-fixes for 4.15

On Wed, Jan 24, 2018 at 7:54 PM, Sean Paul wrote: > > Hi Dave, > I'm sending this since danvet is down under this week. We've collected a > couple > fixes in drm-misc-fixes this week, and since we're still in the business of > 4.15, I figured I'd send them along. Hah, was

Re: [PATCH 2/5] drm: add ARM flush implementation

On Wed, Jan 24, 2018 at 11:26 AM, Russell King - ARM Linux wrote: > On Wed, Jan 24, 2018 at 10:45:28AM -0800, Gurchetan Singh wrote: >> On Wed, Jan 24, 2018 at 4:45 AM, Russell King - ARM Linux < >> li...@armlinux.org.uk> wrote: >> > So no, this is not an acceptable

Re: [PATCH 2/7] drm/ttm: use an operation ctx for ttm_mem_global_alloc

Hi, Sorry, I've been on a leave. Catching up on emails. In case this is still not yet merged, my comment is be consist with the new variable name. In some cases it's "ttm_opt_ctx", in others it's "ctx". I prefer ttm_opt_ctx because it's more descriptive. And yes, some description on why this

[RFC 4/6] drm: Respect driver set DRM_LOG_NAME in drm_printk

From: Tvrtko Ursulin Since drm_printk is built inside the DRM core module, it will not respect the potentially overriden by the driver DRM_LOG_NAME. Make it tale the driver prefix and change it's wrappers so it is passed in from the driver code. This makes the driver

Re: [PATCH 2/5] drm: add ARM flush implementation

On Wed, Jan 24, 2018 at 10:45:28AM -0800, Gurchetan Singh wrote: > On Wed, Jan 24, 2018 at 4:45 AM, Russell King - ARM Linux < > li...@armlinux.org.uk> wrote: > > So no, this is not an acceptable approach. > > > > Secondly, in light of spectre and meltdown, do we _really_ want to > > export cache

Re: [PATCH 3/5] drm: add ARM64 flush implementations

On Wed, Jan 24, 2018 at 12:00:59PM +, Robin Murphy wrote: > On 24/01/18 02:56, Gurchetan Singh wrote: > >This patch uses the __dma_map_area function to flush the cache > >on ARM64. > > > >v2: Don't use DMA API, call functions directly (Daniel) > > > >Signed-off-by: Gurchetan Singh

[RFC 5/6] drm: Respect driver set DRM_LOG_NAME in drm_dev_printk

From: Tvrtko Ursulin Same as the previous patch did for drm_printk, allow for the logging macros to pass in the driver set DRM_LOG_NAME for drm_dev_printk. Signed-off-by: Tvrtko Ursulin Cc: Daniel Vetter Cc: Gustavo

Re: [PATCH] drm/etnaviv: fix '%x' warning

Hello Lucas, Quoting Lucas Stach : Hi Gustavo, Am Dienstag, den 23.01.2018, 11:07 -0600 schrieb Gustavo A. R. Silva: Fix the following warning by using %zx instead of %x for variable of type size_t: warning: format ‘%x’ expects argument of type ‘unsigned int’, but

[RFC 3/6] drm/i915: Give our log messages our name

From: Tvrtko Ursulin Define DRM_LOG_NAME to i915 so that the log messages we output change from: [drm] RC6 on to: [i915] RC6 on Signed-off-by: Tvrtko Ursulin Cc: dri-devel@lists.freedesktop.org --- drivers/gpu/drm/i915/i915_drv.h | 5

[RFC 6/6] drm: Respect driver set DRM_LOG_NAME in drm_info_printer

From: Tvrtko Ursulin Same as the previous patch did for drm_printk, allow for the logging macros to pass in the driver set DRM_LOG_NAME for drm_info_printer. Signed-off-by: Tvrtko Ursulin Cc: Daniel Vetter Cc:

Re: [RFC][PATCH 3/4 v2] drm_hwcomposer: Use client compositing if there is only one plane

On Tue, Jan 23, 2018 at 5:16 PM, John Stultz wrote: > Originally based on work by Rob Herring, this patch changes > ValidateDisplay() so that if there is only one plane, we modify > Device composited layers to be Client composited. > > Without this, on devices with just

Re: [PATCH 2/2] drm/sun4i: Handle DRM_MODE_FLAG_**SYNC_POSITIVE correctly

Hi, Il 24/01/2018 18:38, Giulio Benetti ha scritto: Hi, Il 22/01/2018 21:27, Giulio Benetti ha scritto: Hi, Il 22/01/2018 09:51, Maxime Ripard ha scritto: On Sat, Jan 20, 2018 at 07:50:21PM +0100, Giulio Benetti wrote: On previous handling, if specified DRM_MODE_FLAG_N*SYNC, it was

[RFC 1/6] drm/armada: Simplify drm_dev_init error log

From: Tvrtko Ursulin dev_err will log the device in question and since there is a single caller to drm_dev_init inside this driver, the drm prefix and the function name can both also be safely dropped. Signed-off-by: Tvrtko Ursulin Cc:

Re: [PATCH 2/5] drm: add ARM flush implementation

On Tue, Jan 23, 2018 at 06:56:03PM -0800, Gurchetan Singh wrote: > The dma_cache_maint_page function is important for cache maintenance on > ARM32 (this was determined via testing). > > Since we desire direct control of the caches in drm_cache.c, let's make > a copy of the function, rename it and

Re: [RFC][PATCH 4/4 v2] drm_hwcomposer: Try to fallback if GLCompisition fails

On Wed, Jan 24, 2018 at 1:26 PM, John Stultz wrote: > On Wed, Jan 24, 2018 at 7:26 AM, Sean Paul wrote: >> On Tue, Jan 23, 2018 at 03:16:39PM -0800, John Stultz wrote: >>> When using drm_hwcomposer with the hikey board, the resulting >>> display

[RFC 2/6] drm: Introduce unexported DRM_LOG_NAME define for logging

From: Tvrtko Ursulin Instead of having DRM_NAME which is defined in the uAPI headers used for kernel log prefix messages, introduct a new DRM_LOG_NAME define defined privately in kernel space. Leave the DRM_NAME around, but mark it as obsolete in case there is some

Re: [RFC 1/6] drm/armada: Simplify drm_dev_init error log

On Wed, Jan 24, 2018 at 04:18:16PM +, Tvrtko Ursulin wrote: > From: Tvrtko Ursulin > > dev_err will log the device in question and since there is a single caller > to drm_dev_init inside this driver, the drm prefix and the function name > can both also be safely

[RFC v2 0/6] DRM logging tidy

From: Tvrtko Ursulin This series tries to solve a few issues in the current DRM logging code to primarily make it clearer which messages belong to which driver. Main problem is that currently some logging functions allow individual drivers to override the log prefix

Re: [PATCH 2/2] drm/sun4i: Handle DRM_MODE_FLAG_**SYNC_POSITIVE correctly

Hi, Il 22/01/2018 21:27, Giulio Benetti ha scritto: Hi, Il 22/01/2018 09:51, Maxime Ripard ha scritto: On Sat, Jan 20, 2018 at 07:50:21PM +0100, Giulio Benetti wrote: On previous handling, if specified DRM_MODE_FLAG_N*SYNC, it was ignored, because only PHSYNC and PVSYNC were taken into

Re: [RFC][PATCH 2/4 v2] drm_hwcomposer: Add platformhisi buffer importer for hikey and hikey960

On Wed, Jan 24, 2018 at 1:05 PM, John Stultz wrote: > On Wed, Jan 24, 2018 at 7:23 AM, Sean Paul wrote: >> On Tue, Jan 23, 2018 at 03:16:37PM -0800, John Stultz wrote: >>> This allows for importing buffers allocated from the >>> hikey and hikey960

Re: DRM: double free in rcar_du_vsp.c

Looping in DRM maintainer. Hello, I have found issue with double free() in RCAR DU VSP driver. it is caused by rcar_du_vsp_plane_atomic_duplicate_state(), which duplicates struct rcar_du_vsp_plane_state. This struct holds sg_tables which are then freed in rcar_du_vsp_plane_cleanup_fb(). This

Re: [PATCH 0/2] Small fixes for the meson build

ping Quoting Dylan Baker (2018-01-12 11:57:34) > Here's a few things I've caught as I've started trying to add the meson > build to our CI system. > > Dylan Baker (2): > meson: set proper pkg-config version for libdrm_freedreno > meson: set the minimum version correctly > >

[PATCH v2] drm: Warn if plane/crtc/encoder/connector index exceeds our 32bit bitmasks

From: Ville Syrjälä We use 32bit bitmasks to track planes/crtcs/encoders/connectors. Naturally we can only do that if the index of those objects stays below 32. Issue a warning whenever we exceed that limit, hopefully prompting someone to fix the problem. For

Re: [Intel-gfx] [PATCH] drm: Warn if plane/crtc/encoder/connector index exceeds our 32bit bitmasks

On Wed, Jan 24, 2018 at 11:24:05PM +0200, Ville Syrjälä wrote: > On Wed, Jan 24, 2018 at 04:01:18PM -0500, Harry Wentland wrote: > > On 2018-01-24 01:37 PM, Ville Syrjala wrote: > > > From: Ville Syrjälä > > > > > > We use 32bit bitmasks to track

Re: [PATCH] drm: Warn if plane/crtc/encoder/connector index exceeds our 32bit bitmasks

On 2018-01-24 04:24 PM, Ville Syrjälä wrote: > On Wed, Jan 24, 2018 at 04:01:18PM -0500, Harry Wentland wrote: >> On 2018-01-24 01:37 PM, Ville Syrjala wrote: >>> From: Ville Syrjälä >>> >>> We use 32bit bitmasks to track planes/crtcs/encoders/connectors. >>>

Re: [PATCH] drm: Warn if plane/crtc/encoder/connector index exceeds our 32bit bitmasks

On Wed, Jan 24, 2018 at 04:01:18PM -0500, Harry Wentland wrote: > On 2018-01-24 01:37 PM, Ville Syrjala wrote: > > From: Ville Syrjälä > > > > We use 32bit bitmasks to track planes/crtcs/encoders/connectors. > > Naturally we can only do that if the index of those

[pull] amdgpu drm-next-4.16

Hi Dave, A few more fixes for 4.16. This is on top of the pull request from last week. Most notable change here is a fix to the link order for the now separate from amdgpu GPU scheduler to fix crashes when the modules are build into the kernel rather than as modules. The following changes

Re: [PATCH] drm: Warn if plane/crtc/encoder/connector index exceeds our 32bit bitmasks

On 2018-01-24 01:37 PM, Ville Syrjala wrote: > From: Ville Syrjälä > > We use 32bit bitmasks to track planes/crtcs/encoders/connectors. > Naturally we can only do that if the index of those objects stays > below 32. Issue a warning whenever we exceed that limit,

Re: [PATCH v2 1/2] dt-bindings: etnaviv: add slave interface clock

On Wed, Jan 24, 2018 at 9:37 AM, Lucas Stach wrote: > Newer GPU cores added a new clock input, which allows to gate the slave (AHB) > interface independently from other parts of the GPU. Add it to the supported > clocks. > > Signed-off-by: Lucas Stach

Re: [PATCH v2 2/2] drm/etnaviv: remove the need for a gpu-subsystem DT node

On Wed, Jan 24, 2018 at 9:37 AM, Lucas Stach wrote: > The module autoloading can be triggered through the GPU core nodes > and the necessary platform device for the DRM toplevel device will > be instantiated on module init. > > Suggested-by: Rob Herring >

Re: [PATCH 5/5] drm: Don't pass clip to drm_atomic_helper_check_plane_state()

vmwgfx part: Reviewed-by: Sinclair Yeh On Tue, Jan 23, 2018 at 07:08:57PM +0200, Ville Syrjala wrote: > From: Ville Syrjälä > > Move the plane clip rectangle handling into > drm_atomic_helper_check_plane_state(). Drivers no longer > have to worry

Re: [PATCH v19 10/10] drm/omapdrm: Use of_find_backlight helper

Den 24.01.2018 17.41, skrev Meghana Madhyastha: Replace of_find_backlight_by_node and of the code around it with of_find_backlight helper to avoid repetition of code. Signed-off-by: Meghana Madhyastha --- Reviewed-by: Noralf Trønnes

Re: [PATCH v19 10/10] drm/omapdrm: Use of_find_backlight helper

On Wed, Jan 24, 2018 at 02:23:46PM -0500, Sean Paul wrote: > On Wed, Jan 24, 2018 at 04:41:38PM +, Meghana Madhyastha wrote: > > Replace of_find_backlight_by_node and of the code around it > > with of_find_backlight helper to avoid repetition of code. > > > > Signed-off-by: Meghana Madhyastha

Re: [RFC][PATCH 4/4 v2] drm_hwcomposer: Try to fallback if GLCompisition fails

On Wed, Jan 24, 2018 at 7:26 AM, Sean Paul wrote: > On Tue, Jan 23, 2018 at 03:16:39PM -0800, John Stultz wrote: >> When using drm_hwcomposer with the hikey board, the resulting >> display shows lots of tearing. >> >> This seems to be due to EGLcomposition not initializing

Re: [PATCH v19 10/10] drm/omapdrm: Use of_find_backlight helper

On Wed, Jan 24, 2018 at 04:41:38PM +, Meghana Madhyastha wrote: > Replace of_find_backlight_by_node and of the code around it > with of_find_backlight helper to avoid repetition of code. > > Signed-off-by: Meghana Madhyastha > --- > Changes in v19: > -Changed to

Re: [RFC][PATCH 2/4 v2] drm_hwcomposer: Add platformhisi buffer importer for hikey and hikey960

On Wed, Jan 24, 2018 at 7:23 AM, Sean Paul wrote: > On Tue, Jan 23, 2018 at 03:16:37PM -0800, John Stultz wrote: >> This allows for importing buffers allocated from the >> hikey and hikey960 gralloc implelementations. >> >> Cc: Marissa Wall >> Cc: Sean

[PULL] drm-misc-fixes for 4.15

Hi Dave, I'm sending this since danvet is down under this week. We've collected a couple fixes in drm-misc-fixes this week, and since we're still in the business of 4.15, I figured I'd send them along. drm-misc-fixes-2018-01-24: Two vc4 fixes that were applied in the last day. One fixes a NULL

Re: [PATCH 1/5] drm: rename {drm_clflush_sg, drm_clflush_pages}

Quoting Gurchetan Singh (2018-01-24 18:45:07) > On Wed, Jan 24, 2018 at 1:14 AM, Chris Wilson > wrote: > > Quoting Gurchetan Singh (2018-01-24 02:55:30) > > Since clfush is an x86-only instruction, these function names won't > > make much sense if we start

[Bug 104738] Radeon HD 6970M/6990M crash on iMac on boot - only nomodeset helps

https://bugs.freedesktop.org/show_bug.cgi?id=104738 --- Comment #10 from Alex Deucher --- Is this a regression? Did it work previously? If so, with what kernel? -- You are receiving this mail because: You are the assignee for the

[Bug 104738] Radeon HD 6970M/6990M crash on iMac on boot - only nomodeset helps

https://bugs.freedesktop.org/show_bug.cgi?id=104738 --- Comment #9 from Alex Deucher --- (In reply to hansmatros76 from comment #8) > Thanks but how can a do this? You attached a partial dmesg output in comment 0. Can you just remove the grep so we get the full output?

Re: [PATCH 2/5] drm: add ARM flush implementation

On Wed, Jan 24, 2018 at 4:45 AM, Russell King - ARM Linux < li...@armlinux.org.uk> wrote: > On Tue, Jan 23, 2018 at 06:56:03PM -0800, Gurchetan Singh wrote: > > The dma_cache_maint_page function is important for cache maintenance on > > ARM32 (this was determined via testing). > > > > Since we

Re: [PATCH 1/5] drm: rename {drm_clflush_sg, drm_clflush_pages}

On Wed, Jan 24, 2018 at 1:14 AM, Chris Wilson wrote: > Quoting Gurchetan Singh (2018-01-24 02:55:30) > > Since clfush is an x86-only instruction, these function names won't > > make much sense if we start adding cases for other architectures. > > Whatever your dislike

Re: [PATCH v1 1/2] drm/bridge/synopsys: dsi: Fix dsi_host_transfer() return value

Hi Philippe, On Wed, Jan 24, 2018 at 01:33:54PM +, Philippe CORNU wrote: > On 01/23/2018 10:38 PM, Brian Norris wrote: > > Hi Philippe, > > > > On Tue, Jan 23, 2018 at 6:26 AM, Philippe Cornu > > wrote: > >> The dw_mipi_dsi_host_transfer() must return the number of >

[PATCH] drm: Warn if plane/crtc/encoder/connector index exceeds our 32bit bitmasks

From: Ville Syrjälä We use 32bit bitmasks to track planes/crtcs/encoders/connectors. Naturally we can only do that if the index of those objects stays below 32. Issue a warning whenever we exceed that limit, hopefully prompting someone to fix the problem. Or

Re: [PATCH v1 2/2] drm/bridge/synopsys: dsi: Add a warning msg on dsi read operations

Hi Philippe, On Wed, Jan 24, 2018 at 01:22:04PM +, Philippe CORNU wrote: > On 01/23/2018 10:28 PM, Brian Norris wrote: > > I see you sent this out already today, while I only just responded > > (late) to your questions about it... oh well :) > > > > I got a short period to clean-up and adds

Re: [PATCH v3] drm/bridge/synopsys: dsi: add optional pixel clock

On Wed, Jan 24, 2018 at 09:24:06AM +, Philippe CORNU wrote: > On 01/23/2018 09:49 PM, Brian Norris wrote: > > On Tue, Jan 23, 2018 at 06:08:06PM +0100, Philippe Cornu wrote: > >> --- a/drivers/gpu/drm/bridge/synopsys/dw-mipi-dsi.c > >> +++ b/drivers/gpu/drm/bridge/synopsys/dw-mipi-dsi.c > >>

[Bug 104738] Radeon HD 6970M/6990M crash on iMac on boot - only nomodeset helps

https://bugs.freedesktop.org/show_bug.cgi?id=104738 --- Comment #8 from hansmatro...@gmail.com --- Thanks but how can a do this? Without this option in Grub i only see 1 second a few lines, then the monitor switch into a black screen. nothing happens anymore. also am not able to ping the host. i

Re: [Intel-gfx] [RFC v2 0/6] DRM logging tidy

On 24/01/2018 16:23, Chris Wilson wrote: Quoting Tvrtko Ursulin (2018-01-24 16:18:15) From: Tvrtko Ursulin This series tries to solve a few issues in the current DRM logging code to primarily make it clearer which messages belong to which driver. Main problem is

[PATCH v19 10/10] drm/omapdrm: Use of_find_backlight helper

Replace of_find_backlight_by_node and of the code around it with of_find_backlight helper to avoid repetition of code. Signed-off-by: Meghana Madhyastha --- Changes in v19: -Changed to devm version of of_find_backlight in omapdrm (patch 10) -removed assigning

[PATCH v19 09/10] drm/panel: Use of_find_backlight helper

Replace of_find_backlight_by_node and of the code around it with of_find_backlight helper to avoid repetition of code. Reviewed-by: Noralf Trønnes Reviewed-by: Sean Paul Signed-off-by: Meghana Madhyastha ---

[PATCH v19 08/10] drm/omapdrm: Use backlight_enable/disable helpers

Use backlight_enable/disable helpers instead of changing the property and calling backlight_update_status for cleaner and simpler code and also to avoid repetitions. Reviewed-by: Noralf Trønnes Reviewed-by: Sean Paul Signed-off-by: Meghana Madhyastha

[PATCH v19 07/10] drm/panel: Use backlight_enable/disable helpers

Use backlight_enable/disable helpers instead of changing the property and calling backlight_update_status for cleaner and simpler code and also to avoid repetitions. Reviewed-by: Noralf Trønnes Reviewed-by: Sean Paul Signed-off-by: Meghana Madhyastha

[PATCH v19 06/10] drm/tinydrm: Call devres version of of_find_backlight

Call devm_of_find_backlight (the devres version) instead of of_find_backlight. Reviewed-by: Noralf Trønnes Reviewed-by: Sean Paul Signed-off-by: Meghana Madhyastha --- drivers/gpu/drm/tinydrm/mi0283qt.c | 2 +-

[PATCH v19 05/10] video: backlight: Add devres versions of of_find_backlight

Add devm_of_find_backlight and the corresponding release function because some drivers use devres versions of functions for acquiring device resources. Acked-by: Daniel Thompson Reviewed-by: Noralf Trønnes Reviewed-by: Sean

[PATCH v19 04/10] drm/tinydrm: Replace tinydrm_of_find_backlight with of_find_backlight

Remove tinydrm_of_find_backlight from tinydrm-helpers.c. We now have a generic of_find_backlight defined in backlight.c. Let the callers of tinydrm_of_find_backlight call of_find_backlight. Also, remove select BACKLIGHT_LCD_SUPPORT and select BACKLIGHT_CLASS_DEVICE from tinydrm/Kconfig as it is a

[PATCH v19 03/10] video: backlight: Add of_find_backlight helper in backlight.c

Add of_find_backlight, a helper function which is a generic version of tinydrm_of_find_backlight that can be used by other drivers to avoid repetition of code and simplify things. Acked-by: Daniel Thompson Reviewed-by: Noralf Trønnes Reviewed-by:

[PATCH v19 02/10] drm/tinydrm: Convert tinydrm_enable/disable_backlight to backlight_enable/disable

Remove tinydrm_enable/disable_backlight and let the callers call the more generic backlight_enable/disable helpers Reviewed-by: Noralf Trønnes Reviewed-by: Sean Paul Signed-off-by: Meghana Madhyastha ---

[PATCH v19 01/10] video: backlight: Add helpers to enable and disable backlight

Add helper functions backlight_enable and backlight_disable to enable/disable a backlight device. These helper functions can then be used by different drm and tinydrm drivers to avoid repetition of code and also to enforce a uniform and consistent way to enable/disable a backlight device.

[PATCH v19 00/10] Add backlight helper functions

Move drm helper functions from tinydrm-helpers to linux/backlight for ease of use by callers in other drivers. Changes in v19: -Changed to devm version of of_find_backlight in omapdrm (patch 10) -removed assigning pdev->dev to variable dev in omapdrm (patch 10) Meghana Madhyastha (10): video:

Re: [Intel-gfx] [RFC v2 0/6] DRM logging tidy

Quoting Tvrtko Ursulin (2018-01-24 16:18:15) > From: Tvrtko Ursulin > > This series tries to solve a few issues in the current DRM logging code to > primarily make it clearer which messages belong to which driver. > > Main problem is that currently some logging

[Bug 104738] Radeon HD 6970M/6990M crash on iMac on boot - only nomodeset helps

https://bugs.freedesktop.org/show_bug.cgi?id=104738 --- Comment #7 from Michel Dänzer --- I suspect Alex meant the full dmesg output without nomodeset. :) -- You are receiving this mail because: You are the assignee for the

Re: [RFC][PATCH 2/4 v2] drm_hwcomposer: Add platformhisi buffer importer for hikey and hikey960

On Tue, Jan 23, 2018 at 03:16:37PM -0800, John Stultz wrote: > This allows for importing buffers allocated from the > hikey and hikey960 gralloc implelementations. > > Cc: Marissa Wall > Cc: Sean Paul > Cc: Dmitry Shmidt > Cc:

Re: [PATCH] drm: fix gpu scheduler link order

On Wed, Jan 24, 2018 at 5:46 AM, Christian König wrote: > It should initialize before the drivers using it. > > Signed-off-by: Christian König > Bug: https://bugs.freedesktop.org/show_bug.cgi?id=104736 Reviewed-by: Alex Deucher

[PATCH v2 1/2] dt-bindings: etnaviv: add slave interface clock

Newer GPU cores added a new clock input, which allows to gate the slave (AHB) interface independently from other parts of the GPU. Add it to the supported clocks. Signed-off-by: Lucas Stach --- v2: State when this clock is required. ---

[PATCH v2 2/2] drm/etnaviv: remove the need for a gpu-subsystem DT node

The module autoloading can be triggered through the GPU core nodes and the necessary platform device for the DRM toplevel device will be instantiated on module init. Suggested-by: Rob Herring Signed-off-by: Lucas Stach ---

[Bug 104738] Radeon HD 6970M/6990M crash on iMac on boot - only nomodeset helps

https://bugs.freedesktop.org/show_bug.cgi?id=104738 --- Comment #6 from hansmatro...@gmail.com --- Thanks for your replay @Michel Tested but the system crash and the screen becomes only black. @Alex Done -- You are receiving this mail because: You are the assignee for the

[Bug 104738] Radeon HD 6970M/6990M crash on iMac on boot - only nomodeset helps

https://bugs.freedesktop.org/show_bug.cgi?id=104738 --- Comment #5 from hansmatro...@gmail.com --- Created attachment 136943 --> https://bugs.freedesktop.org/attachment.cgi?id=136943=edit grub.cfg -- You are receiving this mail because: You are the assignee for the

[Bug 104738] Radeon HD 6970M/6990M crash on iMac on boot - only nomodeset helps

https://bugs.freedesktop.org/show_bug.cgi?id=104738 --- Comment #4 from hansmatro...@gmail.com --- Created attachment 136942 --> https://bugs.freedesktop.org/attachment.cgi?id=136942=edit lspci.log -- You are receiving this mail because: You are the assignee for the

[Bug 104738] Radeon HD 6970M/6990M crash on iMac on boot - only nomodeset helps

https://bugs.freedesktop.org/show_bug.cgi?id=104738 --- Comment #3 from hansmatro...@gmail.com --- Created attachment 136941 --> https://bugs.freedesktop.org/attachment.cgi?id=136941=edit dmesg.log -- You are receiving this mail because: You are the assignee for the

Re: [RFC][PATCH 1/4 v2] drm_hwcomposer: Make sure we set the active state when doing modesets

On Tue, Jan 23, 2018 at 03:16:36PM -0800, John Stultz wrote: > In trying to use drm_hwcomposer with HiKey/HiKey960 boards, I > found that the crtc wouldn't intitalize and the atomic commit > calls were failing. > > I initially chased this down to following check in the kernel >

Re: [RFC][PATCH 4/4 v2] drm_hwcomposer: Try to fallback if GLCompisition fails

On Tue, Jan 23, 2018 at 03:16:39PM -0800, John Stultz wrote: > When using drm_hwcomposer with the hikey board, the resulting > display shows lots of tearing. > > This seems to be due to EGLcomposition not initializing > properly, potentially due to I'm guessing limitations of what > the utgard

Re: [RFC][PATCH 2/4 v2] drm_hwcomposer: Add platformhisi buffer importer for hikey and hikey960

On Tue, Jan 23, 2018 at 03:16:37PM -0800, John Stultz wrote: > This allows for importing buffers allocated from the > hikey and hikey960 gralloc implelementations. > > Cc: Marissa Wall > Cc: Sean Paul > Cc: Dmitry Shmidt > Cc:

[Bug 104770] GL_ARB_compute_shader advertised but none-functional / piglit tests failing on CAYMAN.

https://bugs.freedesktop.org/show_bug.cgi?id=104770 --- Comment #1 from Thomas Rohloff --- Maybe this is helpfull, too: OpenGL vendor string: X.Org OpenGL renderer string: AMD CAYMAN (DRM 2.50.0 / 4.14.14, LLVM 5.0.1) OpenGL core profile version string: 4.3 (Core Profile)

[Bug 104770] GL_ARB_compute_shader advertised but none-functional / piglit tests failing on CAYMAN.

https://bugs.freedesktop.org/show_bug.cgi?id=104770 Bug ID: 104770 Summary: GL_ARB_compute_shader advertised but none-functional / piglit tests failing on CAYMAN. Product: Mesa Version: git Hardware: Other

Re: [PATCH 1/5] drm/rcar-du: Use drm_mode_get_hv_timing() to populate plane clip rectangle

On Wed, Jan 24, 2018 at 02:07:30AM +0200, Laurent Pinchart wrote: > Hi Ville, > > Thank you for the patch. > > On Tuesday, 23 January 2018 19:08:53 EET Ville Syrjala wrote: > > From: Ville Syrjälä > > > > Use drm_mode_get_hv_timing() to fill out the plane clip

[Bug 104762] Various segfaults/problems in qt/plasma

https://bugs.freedesktop.org/show_bug.cgi?id=104762 Christoph Haag changed: What|Removed |Added Attachment #136931|0 |1 is

Re: [RFC] Per file OOM badness

On 2018-01-24 12:50 PM, Michal Hocko wrote: > On Wed 24-01-18 12:23:10, Michel Dänzer wrote: >> On 2018-01-24 12:01 PM, Michal Hocko wrote: >>> On Wed 24-01-18 11:27:15, Michel Dänzer wrote: > [...] 2. If the OOM killer kills a process which is sharing BOs with another process, this

[Bug 103234] KWin crashed when Alt+Tab-ing through open windows

https://bugs.freedesktop.org/show_bug.cgi?id=103234 --- Comment #12 from Emil Velikov --- FYI Mesa 17.2.x is EOL, so it might be better to check if 17.3.3 and master still have the issue. -- You are receiving this mail because: You are the assignee for the

[Bug 104745] HEVC VDPAU decoding broken on RX 460 with UVD Firmware v1.130

https://bugs.freedesktop.org/show_bug.cgi?id=104745 --- Comment #5 from Emil Velikov --- Nicely spotted guys. I'll pick Boyuan's VCN/UVD fixed for the next 17.3 release. Feel free to forward future requests to the mesa-stable@ mailing list. I won't be able to catch

Re: [PATCH v1 1/2] drm/bridge/synopsys: dsi: Fix dsi_host_transfer() return value

Hi Brian, And many thanks for your review. On 01/23/2018 10:38 PM, Brian Norris wrote: > Hi Philippe, > > On Tue, Jan 23, 2018 at 6:26 AM, Philippe Cornu wrote: >> The dw_mipi_dsi_host_transfer() must return the number of >> bytes transmitted/received on success instead

Re: [PATCH v1 2/2] drm/bridge/synopsys: dsi: Add a warning msg on dsi read operations

Hi Brian, On 01/23/2018 10:28 PM, Brian Norris wrote: > Hi Philippe, > > I see you sent this out already today, while I only just responded > (late) to your questions about it... oh well :) > I got a short period to clean-up and adds features to this driver (1.31 ip version + maybe the read

Re: [PATCH 3/5] drm: add ARM64 flush implementations

On 24/01/18 12:36, Russell King - ARM Linux wrote: On Wed, Jan 24, 2018 at 12:00:59PM +, Robin Murphy wrote: On 24/01/18 02:56, Gurchetan Singh wrote: This patch uses the __dma_map_area function to flush the cache on ARM64. v2: Don't use DMA API, call functions directly (Daniel)

[Bug 104756] [bisected] [kabini] [regression] [drm:amdgpufb_create] *ERROR* failed to create fbcon object -12

https://bugs.freedesktop.org/show_bug.cgi?id=104756 Christian König changed: What|Removed |Added Status|RESOLVED

[Bug 104736] Kernel panic with agd5's drm-next-4.17-wip & GFX8/Polaris10/Ellesmere/Rx-480-8GiB

https://bugs.freedesktop.org/show_bug.cgi?id=104736 Christian König changed: What|Removed |Added Status|NEW

Re: [RFC] Per file OOM badness

Am 24.01.2018 um 12:50 schrieb Michal Hocko: On Wed 24-01-18 12:23:10, Michel Dänzer wrote: On 2018-01-24 12:01 PM, Michal Hocko wrote: On Wed 24-01-18 11:27:15, Michel Dänzer wrote: [...] 2. If the OOM killer kills a process which is sharing BOs with another process, this should result in

Re: [PATCH 3/5] drm: add ARM64 flush implementations

On 24/01/18 02:56, Gurchetan Singh wrote: This patch uses the __dma_map_area function to flush the cache on ARM64. v2: Don't use DMA API, call functions directly (Daniel) Signed-off-by: Gurchetan Singh --- drivers/gpu/drm/drm_cache.c | 13 + 1 file

Re: [PATCH] drm/etnaviv: fix '%x' warning

Hi Gustavo, Am Dienstag, den 23.01.2018, 11:07 -0600 schrieb Gustavo A. R. Silva: > Fix the following warning by using %zx instead of %x for variable of > type size_t: > > warning: format ‘%x’ expects argument of type ‘unsigned int’, but > argument 4 has type ‘size_t {aka long unsigned int}’

Re: [RFC] Per file OOM badness

On Wed 24-01-18 12:23:10, Michel Dänzer wrote: > On 2018-01-24 12:01 PM, Michal Hocko wrote: > > On Wed 24-01-18 11:27:15, Michel Dänzer wrote: [...] > >> 2. If the OOM killer kills a process which is sharing BOs with another > >> process, this should result in the other process dropping its

Re: [PATCH 2/5] drm: add ARM flush implementation

Am Dienstag, den 23.01.2018, 18:56 -0800 schrieb Gurchetan Singh: > The dma_cache_maint_page function is important for cache maintenance on > ARM32 (this was determined via testing). > > Since we desire direct control of the caches in drm_cache.c, let's make > a copy of the function, rename it

Re: [RFC] Per file OOM badness

On 2018-01-24 12:01 PM, Michal Hocko wrote: > On Wed 24-01-18 11:27:15, Michel Dänzer wrote: >> On 2018-01-24 10:28 AM, Michal Hocko wrote: > [...] >>> So how exactly then helps to kill one of those processes? The memory >>> stays pinned behind or do I still misunderstand? >> >> Fundamentally, the

Re: [PATCH] drm: fix gpu scheduler link order

On 24 January 2018 at 10:46, Christian König wrote: > It should initialize before the drivers using it. > > Signed-off-by: Christian König > Bug: https://bugs.freedesktop.org/show_bug.cgi?id=104736 > --- > drivers/gpu/drm/Makefile | 2

Re: [RFC] Per file OOM badness

On Wed 24-01-18 11:27:15, Michel Dänzer wrote: > On 2018-01-24 10:28 AM, Michal Hocko wrote: [...] > > So how exactly then helps to kill one of those processes? The memory > > stays pinned behind or do I still misunderstand? > > Fundamentally, the memory is only released once all references to

[Bug 104736] Kernel panic with agd5's drm-next-4.17-wip & GFX8/Polaris10/Ellesmere/Rx-480-8GiB

https://bugs.freedesktop.org/show_bug.cgi?id=104736 --- Comment #7 from Mike Lothian --- I can confirm is does fix the issues I was seeing -- You are receiving this mail because: You are the assignee for the bug.___ dri-devel

[Bug 104736] Kernel panic with agd5's drm-next-4.17-wip & GFX8/Polaris10/Ellesmere/Rx-480-8GiB

https://bugs.freedesktop.org/show_bug.cgi?id=104736 --- Comment #6 from Christian König --- Created attachment 136937 --> https://bugs.freedesktop.org/attachment.cgi?id=136937=edit Possible fix I was able to reproduce the problem and the attached patch should

[PATCH] drm: fix gpu scheduler link order

It should initialize before the drivers using it. Signed-off-by: Christian König Bug: https://bugs.freedesktop.org/show_bug.cgi?id=104736 --- drivers/gpu/drm/Makefile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpu/drm/Makefile

  1   2   >