[Bug 105145] vaExportSurfaceHandle interaction with surface interlaced flag prevents switching on vaapi deinterlacing dynamically

https://bugs.freedesktop.org/show_bug.cgi?id=105145 --- Comment #4 from Christian König --- (In reply to k.philipp from comment #2) > Since we can do weaving on the Kodi side anyway (for VDPAU), would it be > enough to add flags, say VA_EXPORT_SURFACE_TOP_FIELD

[Bug 105076] [CI] results file indicate incomplete run.log say other result

https://bugs.freedesktop.org/show_bug.cgi?id=105076 --- Comment #7 from Marta Löfstedt --- https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3785/shard-glkb1/igt@kms_atomic_interrupti...@legacy-pageflip.html

[Bug 100919] [DC] "Out of range" on a display connected to a DVI-D output of RX460 card via DVI-D<=>HDMI-A cable

https://bugs.freedesktop.org/show_bug.cgi?id=100919 Thomas R. changed: What|Removed |Added Status|RESOLVED

[Bug 105076] [CI] results file indicate incomplete run.log say other result

https://bugs.freedesktop.org/show_bug.cgi?id=105076 --- Comment #6 from Marta Löfstedt --- https://intel-gfx-ci.01.org/tree/drm-tip/IGT_4262/shard-glkb1/igt@pm_backli...@fade.html Above is before disk change -- You are receiving this mail because: You are the

[Bug 99353] Kaveri 7400K shows random colored noise instead of GUI in X or Wayland

https://bugs.freedesktop.org/show_bug.cgi?id=99353 --- Comment #34 from Bong Cosca --- @Michel, are there any impediments in getting this patch merged with mesa-git? I tried this with both 17.3.3 and 17.3.4 without any side effects. -- You are receiving this mail because:

[Bug 105156] kdg2kfd_probe failed

https://bugs.freedesktop.org/show_bug.cgi?id=105156 Bug ID: 105156 Summary: kdg2kfd_probe failed Product: DRI Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal

Re: [PATCH 04/24] dt-bindings: display: add HPD gpio to DVI connector

On Mon, Feb 12, 2018 at 11:44:34AM +0200, Tomi Valkeinen wrote: > Add hpd-gpios property to dvi-connector.txt. > > Signed-off-by: Tomi Valkeinen > Cc: devicet...@vger.kernel.org > --- > Documentation/devicetree/bindings/display/connector/dvi-connector.txt | 1 + > 1 file

Re: [PATCH 0/6] Add support for in-line nested struct comments

On Fri, 16 Feb 2018 11:48:14 -0200 Mauro Carvalho Chehab wrote: > his series fix two bugs at kernel-doc.rst examples and add support > for in-line nested struct comments. > > It also converts one documentation at intel_dpio_phy to use it, > in order to give a practical

Re: [PATCHv2 4/8] dt-bindings: panel: common: document orientation property

On Thu, Feb 08, 2018 at 07:30:31PM +0100, Sebastian Reichel wrote: > Introduce new "orientation" property for describing in which > orientation a panel has been mounted to the device. This can > be used by the operating system to automatically rotate the > display correctly. > > Signed-off-by:

Re: [PATCH v1 1/2] dt-bindings/display/panel: Add support for Raydium rm68200 dsi panel

On Thu, Feb 08, 2018 at 03:30:25PM +0100, Philippe Cornu wrote: > The Raydium Semiconductor Corporation RM68200 is a 5.5" 720x1280 > TFT LCD panel connected using a MIPI-DSI video interface. > > Signed-off-by: Philippe Cornu > --- >

linux-next: build warning after merge of the drm tree

Hi all, After merging the drm tree, today's linux-next build (arm multi_v7_defconfig) produced this warning: In file included from include/linux/list.h:9:0, from include/linux/wait.h:7, from include/linux/wait_bit.h:8, from include/linux/fs.h:6,

linux-next: manual merge of the drm tree with Linus' tree

Hi all, Today's linux-next merge of the drm tree got a conflict in: drivers/gpu/drm/i915/intel_breadcrumbs.c between commit: 117172c8f9d4 ("drm/i915/breadcrumbs: Ignore unsubmitted signalers") from Linus' tree and commit: b7a3f33bd5ab ("drm/i915/breadcrumbs: Drop request reference for

linux-next: manual merge of the drm tree with Linus' tree

Hi all, Today's linux-next merge of the drm tree got a conflict in: drivers/gpu/drm/i915/i915_pmu.h between commit: 4c83f0a788cc ("drm/i915/pmu: Fix sleep under atomic in RC6 readout") from Linus' tree and commit: 109ec558370f ("drm/i915/pmu: Only enumerate available counters in

[Bug 104520] Intermittent X crashes: GPU HANG: ecode 9:0:0x85dffffb, in Xorg [443], reason: Hang on rcs0, action: reset

https://bugs.freedesktop.org/show_bug.cgi?id=104520 --- Comment #10 from Amy --- Additonally: Mesa version is OpenGL version string: 3.0 Mesa 17.3.4 -- You are receiving this mail because: You are the assignee for the bug.___

[Bug 104520] Intermittent X crashes: GPU HANG: ecode 9:0:0x85dffffb, in Xorg [443], reason: Hang on rcs0, action: reset

https://bugs.freedesktop.org/show_bug.cgi?id=104520 Amy changed: What|Removed |Added Severity|normal |major -- You are receiving

[Bug 104520] Intermittent X crashes: GPU HANG: ecode 9:0:0x85dffffb, in Xorg [443], reason: Hang on rcs0, action: reset

https://bugs.freedesktop.org/show_bug.cgi?id=104520 --- Comment #9 from Amy --- Still happening on: Linux Playful-Plankton 4.15.4-1-ARCH #1 SMP PREEMPT Sat Feb 17 16:01:38 UTC 2018 x86_64 GNU/Linux version number:11.0 X.Org version: 1.19.6 xf86-video-intel

Re: Question about lima kernel MM implementation

> > > > > > Current MM: > > 1. drm_gem_cma_object, only support contiguous memory > > Please note that drm_gem_cma_object only looks at memory after the MMU > has done the mapping. If you have a good IOMMU driver that registers > correctly the dma_ops then you can allocate memory from anywhere and

[PATCH] drm/edid: Add 6 bpc quirk for CPT panel in Asus UX303LA

Similar to commit e10aec652f31 ("drm/edid: Add 6 bpc quirk for display AEO model 0."), the EDID reports "DFP 1.x compliant TMDS" but it support 6bpc instead of 8 bpc. Hence, use 6 bpc quirk for this panel. Fixes: 196f954e2509 ("drm/i915/dp: Revert "drm/i915/dp: fall back to 18 bpp when sink

Re: [PATCH] fix double ;;s in code

Le 17/02/2018 à 22:19, Pavel Machek a écrit : Fix double ;;'s in code. Signed-off-by: Pavel Machek A summary of the files modified on top of the patch would help understand the impact. A maybe there should be one patch by area, eg one for each arch specific modif and one

[Bug 105145] vaExportSurfaceHandle interaction with surface interlaced flag prevents switching on vaapi deinterlacing dynamically

https://bugs.freedesktop.org/show_bug.cgi?id=105145 --- Comment #3 from k.phil...@gmail.com --- OK, scratch that. Our VAAPI weave implementation uses legacy GL features, and we're not very keen to accommodate for fields in separate textures in our general shaders. Here's what we'll do instead

[Bug 105152] Display artifacts related to DCC on radeonsi

https://bugs.freedesktop.org/show_bug.cgi?id=105152 Bug ID: 105152 Summary: Display artifacts related to DCC on radeonsi Product: Mesa Version: git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW

[PATCH libdrm] meson: do not use cairo/valgrind if disabled

-Dcairo-tests=false currently results into enabling cairo support if it was found. Same for valgrind. Signed-off-by: Igor Gnatenko --- meson.build | 20 1 file changed, 16 insertions(+), 4 deletions(-) diff --git a/meson.build b/meson.build index

Re: [PATCH] drm/edid: Add 6 bpc quirk for CPT panel in Asus UX303LA

On 02/18/2018 09:53 AM, Kai-Heng Feng wrote: Similar to commit e10aec652f31 ("drm/edid: Add 6 bpc quirk for display AEO model 0."), the EDID reports "DFP 1.x compliant TMDS" but it support 6bpc instead of 8 bpc. Hence, use 6 bpc quirk for this panel. Fixes: 196f954e2509 ("drm/i915/dp: Revert

[GIT PULL FOR v4.17] R-Car DU changes

Hi Dave, The following changes since commit 94fc27ac487a80daf42f97b1a0503d029f3c1325: Merge tag 'drm-intel-next-fixes-2018-02-07' of git:// anongit.freedesktop.org/drm/drm-intel into drm-next (2018-02-08 08:21:37 +1000) are available in the git repository at:

Re: [PATCH v3 03/43] drm/rockchip: Respect page offset for PRIME mmap calls

Am Dienstag, 30. Januar 2018, 21:28:33 CET schrieb Thierry Escande: > From: Ørjan Eide > > When mapping external DMA-bufs through the PRIME mmap call, we might be > given an offset which has to be respected. However for the internal DRM > GEM mmap path, we have to ignore the

Re: [PATCH v3 02/43] drm/rockchip: support prime import sg table

Am Dienstag, 30. Januar 2018, 21:28:32 CET schrieb Thierry Escande: > From: Haixia Shi > > The prime fd to handle ioctl was not used with rockchip before. Support > was added in order to pass graphics_Gbm and to support potential uses > within Chrome OS (e.g. zero-copy video

Re: [PATCH v3 01/43] drm/rockchip: Get rid of unnecessary struct fields

Am Dienstag, 30. Januar 2018, 21:28:31 CET schrieb Thierry Escande: > From: Tomasz Figa > > This patch removes unused fields from vop structure. > > Signed-off-by: Tomasz Figa > Signed-off-by: Sean Paul > Signed-off-by: Thierry

[Bug 103769] Unity based games do not start

https://bugs.freedesktop.org/show_bug.cgi?id=103769 --- Comment #12 from letha...@gmail.com --- bug still present with versions: mesa-filesystem-18.1.0-0.2.gita5053ba.fc27.x86_64 llvm-libs-7.0.0-0.1.r323994.fc27.x86_64 clang-7.0.0-0.1.r324055.fc27.x86_64 always segfaulting. -- You are

Re: [PATCH 3/7] drm/rockchip: dsi: Remove unnecessary platform_get_resource() error check

Am Montag, 18. Dezember 2017, 14:02:26 CET schrieb Fabio Estevam: > From: Fabio Estevam > > devm_ioremap_resource() already checks if the resource is NULL, so > remove the unnecessary platform_get_resource() error check. > > Cc: Heiko Stübner >

Re: [PATCH 4/7] drm/rockchip: inno_hdmi: Remove unnecessary platform_get_resource() error check

Am Montag, 18. Dezember 2017, 14:02:27 CET schrieb Fabio Estevam: > From: Fabio Estevam > > devm_ioremap_resource() already checks if the resource is NULL, so > remove the unnecessary platform_get_resource() error check. > > Cc: Heiko Stübner >

Re: [PATCH v5] drm/rockchip: Add device links for master and components

Hi, Am Mittwoch, 7. Februar 2018, 18:53:09 CET schrieb Enric Balletbo i Serra: > From: Jeffy Chen > > Since we are trying to access components' resources in the master's > suspend/resume PM callbacks(e.g. panel), add device links to correct > the suspend/resume and

[Bug 105042] [LLVM Regression] Shadow of Mordor stucks at intro video

https://bugs.freedesktop.org/show_bug.cgi?id=105042 --- Comment #5 from Gregor Münch --- The crash with nir in the beginning is gone. It has now exactly the same behavior and freezes right after the intro video is finished (or you press a button to skip). I think this bug is

[PATCH 7/7] drm/nouveau: Runtime suspend despite HDA being unbound

Commit 5addcf0a5f0f ("nouveau: add runtime PM support (v0.9)") prevents runtime suspend of the GPU if its integrated HDA controller is not bound to a driver. The rationale appears to be that probing the HDA fails if the GPU is in D3cold. However we now use a device link to ensure that the GPU is

[PATCH 5/7] vga_switcheroo: Use device link for HDA controller

Back in 2013, runtime PM for GPUs with integrated HDA controller was introduced with commits 0d69704ae348 ("gpu/vga_switcheroo: add driver control power feature. (v3)") and 246efa4a072f ("snd/hda: add runtime suspend/resume on optimus support (v4)"). Briefly, the idea was that the HDA controller

[PATCH 6/7] vga_switcheroo: Let HDA autosuspend on mux change

When switching the display on muxed machines, we currently force the HDA controller into runtime suspend on the previously used GPU and into runtime active state on the newly used GPU. That's unnecessary if the GPU uses driver power control, we can just let the audio device autosuspend or

[PATCH 4/7] vga_switcheroo: Deduplicate power state tracking

If DRM drivers use runtime PM, they currently notify vga_switcheroo whenever they ->runtime_suspend or ->runtime_resume to update vga_switcheroo's internal power state tracking. That's essentially a duplication of a functionality performed by the PM core as it already tracks the GPU's power state

[PATCH 3/7] vga_switcheroo: Update PCI current_state on power change

When cutting power to a GPU and its integrated HDA controller, their cached current_state should be updated to D3cold to reflect reality. We currently rely on the DRM and HDA drivers to do that, however: - The HDA driver updates the current_state in azx_vs_set_state(), which will no longer be

[PATCH 1/7] PCI: Restore BARs on runtime resume despite being unbound

PCI devices not bound to a driver are supposed to stay in D0 during runtime suspend. But they may have a parent which is bound and can be transitioned to D3cold at runtime. Once the parent goes to D3cold, the unbound child may go to D3cold as well. When the child comes out of D3cold, its BARs

[PATCH 2/7] PCI: Make pci_wakeup_bus() & pci_bus_set_current_state() public

There are PCI devices which are power-manageable by a nonstandard means, such as a custom ACPI method. One example are discrete GPUs in hybrid graphics laptops, another are Thunderbolt controllers in Macs. Such devices can't be put into D3cold with pci_set_power_state() because

[PATCH 0/7] Modernize vga_switcheroo by using device link for HDA

Modernize vga_switcheroo by using a "device link" to enforce a runtime PM dependency from an HDA controller to the GPU it's integrated into. Remove thereby obsoleted code and fix a bunch of bugs. Device links were introduced in v4.10. Users might see a small power saving if the discrete GPU is in

[Bug 105145] vaExportSurfaceHandle interaction with surface interlaced flag prevents switching on vaapi deinterlacing dynamically

https://bugs.freedesktop.org/show_bug.cgi?id=105145 --- Comment #2 from k.phil...@gmail.com --- This "interlaced" data layout - what does it mean exactly? Does it just mean fields in separate surfaces or is there anything else going on additionally? I couldn't find any docs on this in mesa.