[PATCH] MAINTAINERS: Add Lukas Wunner as reviewer for vga_switcheroo

I've been contributing to vga_switcheroo for the past two years and by now am fairly familiar with it, so danvet suggested that I add myself as reviewer. While at it, add missing file pattern for vga_switcheroo.h + vgaarb.h to the DRM and DRM-MISC sections such that get_maintainer.pl returns

[Bug 98629] OpenGL applications warns "MESA-LOADER: failed to retrieve device information"

https://bugs.freedesktop.org/show_bug.cgi?id=98629 Brian Paul changed: What|Removed |Added Status|RESOLVED|REOPENED

Re: [RFC 1/5] drm: Add HDMI 2.0+ features exposing knob

Hi Daniel, On 23-03-2017 11:00, Daniel Vetter wrote: > On Thu, Mar 23, 2017 at 10:44:16AM +, Jose Abreu wrote: >> Hi Daniel, >> >> >> On 23-03-2017 07:22, Daniel Vetter wrote: >>> On Wed, Mar 22, 2017 at 05:35:57PM +, Jose Abreu wrote: We can't expect userspace to have full support

[PATCHv3 2/2] drm/panel: simple: Add support for Winstar WF35LTIACD

This adds support for the Winstar Display Co. WF35LTIACD 3.5" QVGA TFT LCD panel, which can be supported by the simple panel driver. Acked-by: Rob Herring Signed-off-by: Richard Genoud --- Changes since v2: Remove status, reg and unit-addresses from

Re: [PATCH] mm: Remove pointless might_sleep() in remove_vm_area().

Thomas Hellstrom wrote: > So to summarize. Yes, the drm callers can be fixed up, but IMO requiring > vfree() to be non-atomic is IMO not a good idea if avoidable. I agree. I don't know about drm code. But I can find AppArmor code doing kvfree() from dfa_free() from aa_dfa_free_kref() from

[PATCH 1/2] drm/sun4i: Add display backend interrupt to device tree binding

The display backend has an interrupt line. Add it to the device tree binding. Signed-off-by: Chen-Yu Tsai --- Documentation/devicetree/bindings/display/sunxi/sun4i-drm.txt | 2 ++ 1 file changed, 2 insertions(+) diff --git

Re: [PATCH v6 1/3] drm_fourcc: Add new P010, P016 video format

從我的 iPad 傳送 > Ander Conselvan De Oliveira 於 2017年3月14日 下午9:53 寫道： > >> On Tue, 2017-03-07 at 04:27 +0800, Ayaka wrote: >> >> 從我的 iPad 傳送 >> Ville Syrjälä 於 2017年3月7日 上午2:34 寫道： On Tue, Mar 07, 2017 at 01:58:23AM +0800,

Re: [PATCHv2 2/2] drm/panel: simple: Add support for Winstar WF35LTIACD

2017-03-24 16:58 GMT+01:00 Rob Herring : > On Mon, Mar 20, 2017 at 02:32:22PM +0100, Richard Genoud wrote: >> This adds support for the Winstar Display Co. WF35LTIACD 3.5" QVGA TFT >> LCD panel, which can be supported by the simple panel driver. >> >> Signed-off-by: Richard Genoud

Re: [PATCH] mm: Remove pointless might_sleep() in remove_vm_area().

On Mon, Mar 27, 2017 at 04:26:02PM +0300, Andrey Ryabinin wrote: > [+CC drm folks, see the following threads: > > http://lkml.kernel.org/r/201703232349.bgb95898.qhlvffomtfo...@i-love.sakura.ne.jp > >

Re: linux-next: manual merge of the drm tree with the drm-intel-fixes tree

> On Tue, Mar 21, 2017 at 5:00 PM, Stephen Rothwell wrote: > Hi Dave, > > Today's linux-next merge of the drm tree got a conflict in: > > drivers/gpu/drm/i915/i915_gem_shrinker.c > > between commit: > > 3d3d18f086cd ("drm/i915: Avoid rcu_barrier() from reclaim paths

[PATCH 2/2] ARM: dts: sun5i: Add interrupt for display backend

The display backend on sun5i shares the same interrupt line as the display frontend. Add it. Signed-off-by: Chen-Yu Tsai --- This won't directly apply to old releases. We may want to backport them though? --- arch/arm/boot/dts/sun5i.dtsi | 1 + 1 file changed, 1 insertion(+)

[PATCH 0/2] drm/sun4i: Add display backend interrupt to dt binding

Hi Maxime, As promised, here is the patch adding the interrupt line for the display backend to the sun5i shared dtsi, and another one adding it to the device tree bindings. The display backend has an undocumented (in the user manual) interrupt that, according to vendor code, is raised when the

Re: [PATCH] mm: Remove pointless might_sleep() in remove_vm_area().

On 03/27/2017 05:29 PM, Tetsuo Handa wrote: > Thomas Hellstrom wrote: >> So to summarize. Yes, the drm callers can be fixed up, but IMO requiring >> vfree() to be non-atomic is IMO not a good idea if avoidable. > > I agree. > > I don't know about drm code. But I can find AppArmor code doing >

drivers/gpu/drm/msm/hdmi/hdmi_hdcp.c:1319]: (style) Redundant condition

Hello there, linux-4.11-rc4/drivers/gpu/drm/msm/hdmi/hdmi_hdcp.c:1319]: (style) Redundant condition: If 'EXPR == 0', the comparison 'EXPR != 1' is always true. Source code is if ((HDCP_STATE_INACTIVE != hdcp_ctrl->hdcp_state) || (HDCP_STATE_NO_AKSV == hdcp_ctrl->hdcp_state)) {

Re: [PATCH] drm: Add description for scdc variable

On Sat, 25 Mar 2017, Shashank Sharma wrote: > This patch adds description about 'scdc' variable in drm_hdmi_info > structure, to fix this warning during doc-build. > > "drm_connector.h:140: warning: No description found for parameter 'scdc'" Did you actually run 'make

Re: [PATCH] drm: Add description for scdc variable

On Mon, 27 Mar 2017, Jani Nikula wrote: > On Sat, 25 Mar 2017, Shashank Sharma wrote: >> This patch adds description about 'scdc' variable in drm_hdmi_info >> structure, to fix this warning during doc-build. >> >> "drm_connector.h:140:

Re: [PATCH 01/19] drm: Wire up proper acquire ctx for plane functions

On Wednesday, March 22, 2017 10:50:40 PM EDT Daniel Vetter wrote: > This is just prep work to get an acquire ctx into every place where we > call ->update_plane or ->disable_plane. > > v2: Keep the hidden acquire_ctx pointers valid while transitioning. > > Signed-off-by: Daniel Vetter

Re: [PATCH 07/19] drm/tegra: Don't use modeset_lock_crtc

On Wed, Mar 22, 2017 at 10:50:46PM +0100, Daniel Vetter wrote: > Yes the help text is unhelpful, but atomic drivers should never use > this. Just grab the lock without context or anything. > > Also an aside: Checking ->active like this doesn't protect against > nonblocking commits, this is rather

[PATCH 3/3] dim: Backronym

It's kinda beyond just drm-intel nowadays ... Idea from Jani on irc. Signed-off-by: Daniel Vetter --- dim.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/dim.rst b/dim.rst index be541d80ec7e..87a8906aad8d 100644 --- a/dim.rst +++ b/dim.rst

Re: [PATCH 7/15] dt-bindings: display: sun4i: Add allwinner,tcon-channel property

On Fri, Mar 17, 2017 at 11:34:45AM +0800, Chen-Yu Tsai wrote: > On Thu, Mar 16, 2017 at 1:37 AM, Rob Herring wrote: > > On Tue, Mar 07, 2017 at 09:56:26AM +0100, Maxime Ripard wrote: > >> The Allwinner Timings Controller has two, mutually exclusive, channels. > >> When the

[PATCH 1/3] drm: Document maintainer duties

I wanted to get Sean Paul to run the drm-misc show for a bit, for training reasons and to increase the bus factor. And then realized there's no docs about what maintainers are doing. Fix that. v2: Add backmerges and taking the blame. Signed-off-by: Daniel Vetter ---

[PATCH 2/3] dim: Review subcommand docs

Inspired by Jani's efforts to clean this up and structure it better. Signed-off-by: Daniel Vetter --- dim.rst | 20 ++-- 1 file changed, 14 insertions(+), 6 deletions(-) diff --git a/dim.rst b/dim.rst index 2f8fda8c42a7..be541d80ec7e 100644 ---

Re: [PATCH 06/19] drm/vmwgfx: Drop the cursor locking hack

On 03/27/2017 08:28 AM, Daniel Vetter wrote: > We discussed this quickly on irc, transcribing. > > On Mon, Mar 27, 2017 at 5:01 AM, Michel Dänzer wrote: >> Strictly speaking, the (virtual) hardware is too limited to support the >> legacy KMS cursor API. AFAIR e.g. weston at

Re: vsps DT property (was: Re: [PATCH 10/22] drm: rcar-du: Expose the VSP1 compositor through KMS planes)

Hi Geert, On Thursday 23 Mar 2017 16:10:56 Geert Uytterhoeven wrote: > On Mon, Sep 14, 2015 at 12:50 AM, Laurent Pinchart wrote: > > Signed-off-by: Laurent Pinchart > > > > > > --- /dev/null > > +++ b/drivers/gpu/drm/rcar-du/rcar_du_vsp.c > > > > +int

[PATCH] drm: rcar-du: Document the vsps property in the DT bindings

The property is used by the driver but is missing from the DT bindings. Document it. Reported-by: Geert Uytterhoeven Signed-off-by: Laurent Pinchart --- Documentation/devicetree/bindings/display/renesas,du.txt | 5 + 1 file

Re: [PATCHv2 26/31] drm/omap: Create fbdev emulation only for the first DRM connector

On 25/03/17 23:22, Daniel Vetter wrote: > On Fri, Mar 24, 2017 at 11:40:47AM +0200, Tomi Valkeinen wrote: >> From: Peter Ujfalusi >> >> Add fbdev emulation only for the first DRM connector. >> When the fbdev emulation was created for all connectors with different >>

Re: [PATCH v2] drm: dw_hdmi: Don't rely on the status of the bridge for updating HPD

Hi, On 03/10/2017 03:01 PM, Romain Perier wrote: Currently, the irq handler that monitores changes for HPD anx RX_SENSE relies on the status of the bridge for updating the status of the HPD. The update is done only when the bridge is enabled. However, on Rockchip platforms we have found use

Re: [PATCH v2] drm/tinydrm: Fix drm_driver.fops.owner

On Sun, Mar 26, 2017 at 04:25:29PM +0200, Noralf Trønnes wrote: > drm_driver.fops can't be shared since the owner then becomes tinydrm.ko. > Move the fops declaration to the driver. > > v2: Use DEFINE_DRM_GEM_CMA_FOPS > > Reported-by: Daniel Vetter > Signed-off-by:

Re: [PATCH] drm/atomic: Introduce drm_atomic_helper_shutdown

On Mon, Mar 27, 2017 at 10:15:12AM +0300, Tomi Valkeinen wrote: > On 21/03/17 18:41, Daniel Vetter wrote: > > The trouble here is that it does multiple atomic commits under one > > drm_modeset_lock_all, which breaks the behind-the-scenes acquire > > context magic that function pulls off. It's much

Re: [PATCH 2/3] dim: Review subcommand docs

On Mon, Mar 27, 2017 at 10:45:45AM +0200, Daniel Vetter wrote: > Inspired by Jani's efforts to clean this up and structure it better. > > Signed-off-by: Daniel Vetter Forgot to add in the commit message: This adds the doc for update-next-continue. -Daniel > --- >

Re: [PATCH] drm/atomic: Introduce drm_atomic_helper_shutdown

On 21/03/17 18:41, Daniel Vetter wrote: > The trouble here is that it does multiple atomic commits under one > drm_modeset_lock_all, which breaks the behind-the-scenes acquire > context magic that function pulls off. It's much better to have one > overall atomic commit. That we still have multiple

Re: [PATCH v5 4/8] drm: Add driver-private objects to atomic state

On Mon, Mar 27, 2017 at 10:28:42AM +0200, Maarten Lankhorst wrote: > Op 27-03-17 om 08:38 schreef Daniel Vetter: > > On Wed, Mar 22, 2017 at 03:30:49PM -0700, Dhinakaran Pandiyan wrote: > >> From: "Pandiyan, Dhinakaran" > >> > >> It is necessary to track states for

Re: [PATCHv2 31/31] drm/omap: fix crash on module unload

On 25/03/17 23:25, Daniel Vetter wrote: > On Fri, Mar 24, 2017 at 11:40:52AM +0200, Tomi Valkeinen wrote: >> When unloading omapdrm we get a NULL pointer deref in >> omap_drm_irq_uninstall(). This is caused by: >> >> 967dd48417874dd25491a4e933648f394a64f70f ("drm: remove >>

Re: [PATCH] drm/tinydrm: Fix drm_driver.fops.owner

On Sun, Mar 26, 2017 at 01:56:55AM +0100, Noralf Trønnes wrote: > > Den 25.03.2017 22.32, skrev Daniel Vetter: > > On Sat, Mar 25, 2017 at 02:56:20PM +0100, Noralf Trønnes wrote: > > > drm_driver.fops can't be shared since the owner then becomes tinydrm.ko. > > > Move the fops declaration to the

[PATCH] drm/exynos: Properly release default ARM DMA-IOMMU mapping

Exynos DRM on ARM architecture creates its own DMA-IOMMU mapping, shared between all devices that builds the Exynos DRM subsystem. Thus, the default DMA-IOMMU mapping structure created by platform init code can be released to avoid leaking resources, because after exynos_iommu_attach() the default

Re: [PATCH 06/19] drm/vmwgfx: Drop the cursor locking hack

We discussed this quickly on irc, transcribing. On Mon, Mar 27, 2017 at 5:01 AM, Michel Dänzer wrote: > Strictly speaking, the (virtual) hardware is too limited to support the > legacy KMS cursor API. AFAIR e.g. weston at least used to make use of HW > cursors for other

Re: [PATCH v5 4/8] drm: Add driver-private objects to atomic state

Op 27-03-17 om 10:31 schreef Daniel Vetter: > On Mon, Mar 27, 2017 at 10:28:42AM +0200, Maarten Lankhorst wrote: >> Op 27-03-17 om 08:38 schreef Daniel Vetter: >>> On Wed, Mar 22, 2017 at 03:30:49PM -0700, Dhinakaran Pandiyan wrote: From: "Pandiyan, Dhinakaran"

Re: [PATCH v5 4/8] drm: Add driver-private objects to atomic state

Hey, There are still 2 unnecessary NULL checks, afaict. Op 22-03-17 om 23:30 schreef Dhinakaran Pandiyan: > From: "Pandiyan, Dhinakaran" > > It is necessary to track states for objects other than connector, crtc > and plane for atomic modesets. But adding objects

Re: [PATCHv2 26/31] drm/omap: Create fbdev emulation only for the first DRM connector

On Mon, Mar 27, 2017 at 09:28:07AM +0300, Tomi Valkeinen wrote: > On 25/03/17 23:22, Daniel Vetter wrote: > > On Fri, Mar 24, 2017 at 11:40:47AM +0200, Tomi Valkeinen wrote: > >> From: Peter Ujfalusi > >> > >> Add fbdev emulation only for the first DRM connector. > >> When

Re: [PATCH v5 4/8] drm: Add driver-private objects to atomic state

On Wed, Mar 22, 2017 at 03:30:49PM -0700, Dhinakaran Pandiyan wrote: > From: "Pandiyan, Dhinakaran" > > It is necessary to track states for objects other than connector, crtc > and plane for atomic modesets. But adding objects like DP MST link > bandwidth to

Re: [PATCH v5 4/8] drm: Add driver-private objects to atomic state

Op 27-03-17 om 08:38 schreef Daniel Vetter: > On Wed, Mar 22, 2017 at 03:30:49PM -0700, Dhinakaran Pandiyan wrote: >> From: "Pandiyan, Dhinakaran" >> >> It is necessary to track states for objects other than connector, crtc >> and plane for atomic modesets. But

Re: [PATCHv2 26/31] drm/omap: Create fbdev emulation only for the first DRM connector

On 27/03/17 09:40, Daniel Vetter wrote: > On Mon, Mar 27, 2017 at 09:28:07AM +0300, Tomi Valkeinen wrote: >> On 25/03/17 23:22, Daniel Vetter wrote: >>> On Fri, Mar 24, 2017 at 11:40:47AM +0200, Tomi Valkeinen wrote: From: Peter Ujfalusi Add fbdev emulation

Re: [PATCHv2 26/31] drm/omap: Create fbdev emulation only for the first DRM connector

On Mon, Mar 27, 2017 at 10:25:46AM +0300, Tomi Valkeinen wrote: > On 27/03/17 09:40, Daniel Vetter wrote: > > On Mon, Mar 27, 2017 at 09:28:07AM +0300, Tomi Valkeinen wrote: > >> On 25/03/17 23:22, Daniel Vetter wrote: > >>> On Fri, Mar 24, 2017 at 11:40:47AM +0200, Tomi Valkeinen wrote: >

Re: [CRTC:24] vblank wait timed out

On Fri, Mar 24, 2017 at 11:42:53AM +0100, Philipp Zabel wrote: > On Fri, 2017-03-24 at 10:24 +, Martyn Welch wrote: > [...] > > > Could you move to v4.9 or v4.10 and check if the four patches in > > > https://git.pengutronix.de/cgit/pza/linux/tag/?id=v4.9-ipu-dp-plane-fix > > > or > > >

[PATCH] drm/ttm, drm/vmwgfx: Relax permission checking when opening surfaces

Previously, when a surface was opened using a legacy (non prime) handle, it was verified to have been created by a client in the same master realm. Relax this so that opening is also allowed recursively if the client already has the surface open. This works around a regression in svga mesa where

[PATCH] drm: document drm_ioctl.[hc]

Also unify/merge with the existing stuff. I was a bit torn where to put this, but in the end I decided to put all the ioctl/sysfs/debugfs stuff into drm-uapi.rst. That means we have a bit a split with the other uapi related stuff used internally, like drm_file.[hc], but I think overall this makes

Re: [PATCH] drm: rcar-du: Document the vsps property in the DT bindings

Hi Laurent, On Mon, Mar 27, 2017 at 11:56 AM, Laurent Pinchart wrote: > The property is used by the driver but is missing from the DT bindings. > Document it. > > Reported-by: Geert Uytterhoeven > Signed-off-by: Laurent Pinchart

[PATCH] drm/vmwgfx: Type-check lookups of fence objects

A malicious caller could otherwise hand over handles to other objects causing all sorts of interesting problems. Testing done: Ran a Fedora 25 desktop using both Xorg and gnome-shell/Wayland. Cc: Signed-off-by: Thomas Hellstrom Reviewed-by:

[PATCH 02/11] drm/vmwgfx: CRTC atomic state

Create and Add CRTC state. We currently do not track any properties or custom states so we can technically use the DRM helpers. Creating this code just to make potential future additions easier. Most of the new code will be compiled but not enabled until plane/connector state handling code is

[PATCH 01/11] drm/vmwgfx: Add universal plane support

Universal support is prerequisite for atomic mode set. Explicitly create planes for the cursor and the primary FB. With a functional cursor plane, the DRM will no longer use the legacy cursor_set2 and cursor_move entry points. Signed-off-by: Sinclair Yeh Signed-off-by: Thomas

[PATCH 04/11] drm/vmwgfx: Connector atomic state

Add connector handling functions. Start tracking is_implicity in the connector state. Eventually, this field should be tracked exclusively in a connector state. Now that plane and connector states have been created, we can also activate the code that use CRTC state. Signed-off-by: Sinclair Yeh

[PATCH 03/11] drm/vmwgfx: Plane atomic state

Add plane state handling functions. We have to keep track of a few plane states so we cannot use the DRM helper for this. Created vmw_plane_state along with functions to reset, duplicate, and destroty it. Signed-off-by: Sinclair Yeh Reviewed-by: Thomas Hellstrom

[PATCH 00/11] Enable Atomic Mode Set on vmwgfx

This series enables atomic mode set on vmwgfx. Developed in collaboration with Thomas Hellstrom and the VMWare Graphics Team. ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel

[PATCH 05/11] drm/vmwgfx: Add and connect CRTC helper functions

Atomic mode set requires us to refactor existing vmw_stdu_crtc_set_config code into sections that check the validity of the new mode, and sections that actually program the hardware state. vmw_du_crtc_atomic_check() takes CRTC-related checking code. In a later patch,

[PATCH 06/11] drm/vmwgfx: Add and connect plane helper functions

Refactor previous FB and cursor plane update code into their atomic counterparts: check, update, prepare, cleanup, and disable. These helpers won't be called until we flip on the atomic support flag or set drm_crtc_funcs->set_config to using the atomic helper. v2: * Removed unnecessary pinning

[PATCH 10/11] drm/vmwgfx: Switch over to internal atomic API for STDU

Switch over to using internal atomic API for mode set. This removes the legacy set_config API, replacing it with drm_atomic_helper_set_config(). The DRM helper will use various vmwgfx-specific atomic functions to set a mode. DRIVER_ATOMIC capability flag is not yet set, so the user mode will

[PATCH 09/11] drm/vmwgfx: Fixes to vmwgfx_fb

1. When unsetting a mode, num_connector should be set to zero 2. The pixel_format field needs to be initialized as newer DRM internal functions checks this field 3. Take the drm_modeset_lock_all() because vmw_fb_kms_detach() can change current mode Signed-off-by: Sinclair Yeh

[PATCH 08/11] drm/vmwgfx: Add and connect atomic state object check/commit

This connects the main state object check and commit function. Signed-off-by: Sinclair Yeh Signed-off-by: Thomas Hellstrom Reviewed-by: Thomas Hellstrom --- drivers/gpu/drm/vmwgfx/vmwgfx_kms.c | 66

[PATCH 07/11] drm/vmwgfx: Add and connect connector helper function

Since the link between connector and encoder is always fixed in our case, just return the one encoder. These helpers won't be called until we flip on the atomic support flag or set drm_crtc_funcs->set_config to using the atomic helper. Signed-off-by: Sinclair Yeh Reviewed-by:

[PATCH 11/11] drm/vmwgfx: Switch over to internal atomic API for SOU and LDU

Switch over to internal atomic API. This completes the atomic internal atomic switch for all the Display Units. Signed-off-by: Sinclair Yeh Signed-off-by: Thomas Hellstrom Reviewed-by: Thomas Hellstrom ---

[Bug 100398] [agd5f] New errors when tonga card powers up

https://bugs.freedesktop.org/show_bug.cgi?id=100398 --- Comment #1 from Alex Deucher --- Is this still an issue with the latest drm-next-4.12-wip branch? I just a squashed in a fix for this. -- You are receiving this mail because: You are the assignee for the

Re: [PATCH v2 09/10] drm/nouveau: Handle frame-packing mode geometry and timing effects

Hi Alastair, [auto build test ERROR on drm/drm-next] [also build test ERROR on v4.11-rc4 next-20170327] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Alastair-Bridgewater/Enable-HDMI

[Bug 100400] Game Valhalla Hills crash on startup

https://bugs.freedesktop.org/show_bug.cgi?id=100400 Michel Dänzer changed: What|Removed |Added Attachment #130461|application/octet-stream|text/plain

[Bug 100400] Game Valhalla Hills crash on startup

https://bugs.freedesktop.org/show_bug.cgi?id=100400 --- Comment #7 from Michel Dänzer --- valgrind might give more information. -- You are receiving this mail because: You are the assignee for the bug.___ dri-devel mailing list

[Bug 100424] X hang (in kernel) after some event in Serious Sam Fusion using radv. 4.9/and-staging-4.9

https://bugs.freedesktop.org/show_bug.cgi?id=100424 Michel Dänzer changed: What|Removed |Added Component|DRM/AMDgpu

[Bug 100395] DC, Powerplay, Tonga, top screen flicker with current amd-staging-4.9

https://bugs.freedesktop.org/show_bug.cgi?id=100395 --- Comment #1 from Michel Dänzer --- So this doesn't happen with amdgpu.dc=0? -- You are receiving this mail because: You are the assignee for the bug.___ dri-devel mailing list

[Bug 100392] Applications Requiring 3d accel fail to launch on Wayland after waking from sleep

https://bugs.freedesktop.org/show_bug.cgi?id=100392 Michel Dänzer changed: What|Removed |Added Attachment #130456|text/x-log |text/plain

[Bug 100392] Applications Requiring 3d accel fail to launch on Wayland after waking from sleep

https://bugs.freedesktop.org/show_bug.cgi?id=100392 --- Comment #2 from Michel Dänzer --- Please attach the dmesg output from when the problem occurs. -- You are receiving this mail because: You are the assignee for the bug.___

[PATCH 5/9] drm/vmwgfx: Introduce a simple resource type

From: Thomas Hellstrom The callbacks we need to provide to many resources are very similar, so provide a simple resource type with a number of helpers for these callbacks. Signed-off-by: Thomas Hellstrom Reviewed-by: Sinclair Yeh

[PATCH 7/9] drm/vmwgfx: Define an overlaid handle_close ioctl.

From: Thomas Hellstrom Instead of providing an ioctl for each handle type, provide a single handle_close ioctl, and reuse the UNREF_DMABUF ioctl. Signed-off-by: Thomas Hellstrom Reviewed-by: Sinclair Yeh ---

[PATCH 6/9] drm/vmwgfx: Re-implement the stream resource as a simple resource.

From: Thomas Hellstrom Provide and document a reference implementation. Signed-off-by: Thomas Hellstrom Reviewed-by: Sinclair Yeh --- drivers/gpu/drm/vmwgfx/Makefile | 2 +- drivers/gpu/drm/vmwgfx/vmwgfx_resource.c |

[PATCH 4/9] drm/vmwgfx: Revert "drm/vmwgfx: Replace numeric parameter like 0444 with macro"

From: Øyvind A. Holm This reverts commit 2d8e60e8b074 ("drm/vmwgfx: Replace numeric parameter like 0444 with macro") The commit belongs to the series of 1285 patches sent to LKML on 2016-08-02, it changes the representation of file permissions from the octal value "0600" to

[PATCH 1/9] drm/vmwgfx: Explicityly track screen target width and height

We can no longer make the assumption that vmw_stdu_update_st() will be called when there's a valid display surface attached. So instead of using display_srf for width and height, make a record of these paremeters when the screen target is first defined. Signed-off-by: Sinclair Yeh

[0/9] Collection of patches queued up for vmwgfx-next

These are a collection of patches currently queued for vmwgfx-next ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel

[PATCH 2/9] drm/vmwgfx: Skipping fbdev fb pinning for ldu

Pinning fbdev's FB at the start of VRAM prevents X from pinning its FB. Since for ldu, the fb would be pinned anyway during a mode set, just skip pinning it in fbdev. This is not the best solution, but since ldu is not used much anymore, it seems like a reasonable workaround. Signed-off-by:

[PATCH 3/9] drm/vmwgfx: Fix LDU X blank screen until mode change issue

vmw_ldu_crtc_helper_commit() is not called if drm_atomic_crtc_needs_modeset() decides nothing related to CRTC timing has changed. So a better place for this code is in vmw_ldu_primary_plane_atomic_update() since we will need to update ld->fb every time the FB is updated. Signed-off-by: Sinclair

[Bug 100424] X hang (in kernel) after some event in Serious Sam Fusion using radv. 4.9/and-staging-4.9

https://bugs.freedesktop.org/show_bug.cgi?id=100424 Bug ID: 100424 Summary: X hang (in kernel) after some event in Serious Sam Fusion using radv. 4.9/and-staging-4.9 Product: DRI Version: DRI git Hardware: x86-64 (AMD64)

Re: [PATCH v6 1/3] drm_fourcc: Add new P010, P016 video format

On 03/26/2017 09:05 PM, Ayaka wrote: 從我的 iPad 傳送 Ander Conselvan De Oliveira 於 2017年3月14日 下午9:53 寫道： On Tue, 2017-03-07 at 04:27 +0800, Ayaka wrote: 從我的 iPad 傳送 Ville Syrjälä 於 2017年3月7日 上午2:34 寫道： On Tue, Mar 07, 2017 at

[PATCH] drm/vc4: Allow using more than 256MB of CMA memory.

Until now, we've had to limit Raspberry Pi to 256MB of CMA memory to keep from triggering the hardware addressing bug between of the tile binner of the tile alloc memory (where the top 4 bits come from the tile state data array's address). To work around that and allow more memory to be reserved

[radeon-alex:drm-next-4.12-wip 208/266] drivers/gpu/drm/amd/amdgpu/gfxhub_v1_0.c:166:31: warning: right shift count >= width of type

tree: git://people.freedesktop.org/~agd5f/linux.git drm-next-4.12-wip head: ba92d1fc68425bbff454195c1a7bf07ec9b650d0 commit: 7b6a92ae5cf029e021246cb79c8613b19e4554d4 [208/266] drm/amdgpu: Add GMC 9.0 support (v2) config: i386-allmodconfig (attached as .config) compiler: gcc-6 (Debian 6.2.0-3)

[Bug 100398] [agd5f] New errors when tonga card powers up

https://bugs.freedesktop.org/show_bug.cgi?id=100398 Mike Lothian changed: What|Removed |Added CC||m...@fireburn.co.uk

[Bug 100424] X hang (in kernel) after some event in Serious Sam Fusion using radv. 4.9/and-staging-4.9

https://bugs.freedesktop.org/show_bug.cgi?id=100424 --- Comment #1 from Darren Salt --- I'm aware (via IRC) that 4.11-rc3 should be fine. However, as I'm using amd-staging-4.9 for its HDMI audio support, this isn't an option. -- You are receiving this mail because:

[Bug 100390] [steam] Grand Ages: Medieval crashes instantly

https://bugs.freedesktop.org/show_bug.cgi?id=100390 --- Comment #6 from Samuel Pitoiset --- The game requests a 4.1 compatibility profile which is unsupported by Mesa and it crashes because it doesn't check the return value of glXCreateContextAttribsARB. I'm

[Bug 98924] [AMDGPU][SI] R9 m265x doesn't work with experimental kernel driver

https://bugs.freedesktop.org/show_bug.cgi?id=98924 --- Comment #3 from Jeroen Bollen --- I can confirm this bug also. Hardware: 03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Opal XT [Radeon R7 M265] (rev 81) Subsystem: Hewlett-Packard

[PATCH 8/9] drm/vmwgfx: Support topology greater than texture size

Most of the display servers today use a single surface to represent the entire desktop even if it's stretched across multiple screens. For vmwgfx with STDU, the maximum surface size is limited to the maximum texture size on the host. On a 2D VM, this limits our ability to support configurations

[PATCH 9/9] drm/vmwgfx: Properly check display/scanout surface size

The scanout surface size is the smaller of max texture size and max STDU size. Signed-off-by: Sinclair Yeh Reviewed-by: Thomas Hellstrom --- drivers/gpu/drm/vmwgfx/vmwgfx_kms.c | 3 +++ drivers/gpu/drm/vmwgfx/vmwgfx_stdu.c| 16 +++-

[radeon-alex:drm-next-4.12-wip 211/266] drivers/gpu/drm/amd/amdgpu/vega10_ih.c:106:82: warning: right shift count >= width of type

tree: git://people.freedesktop.org/~agd5f/linux.git drm-next-4.12-wip head: ba92d1fc68425bbff454195c1a7bf07ec9b650d0 commit: 8ddf606557a311b7a4b4b5ad0578e52d2e7d5728 [211/266] drm/amdgpu: add vega10 interrupt handler config: i386-allmodconfig (attached as .config) compiler: gcc-6 (Debian

[Bug 100390] [steam] Grand Ages: Medieval crashes instantly

https://bugs.freedesktop.org/show_bug.cgi?id=100390 --- Comment #7 from Samuel Pitoiset --- Okay, the game uses ARB_texture_buffer_object which is only exposed with a core profile for some reasons. I'm able to run the game with some hacky changes but it fails to render

[Bug 100375] forced EDID's can cause a amdgpu to null ptr deref

https://bugs.freedesktop.org/show_bug.cgi?id=100375 --- Comment #1 from Michel Dänzer --- set_root doesn't look directly related to amdgpu or drm, so this could be memory corruption. KASAN might give more information. Does this only happen when forcing an invalid EDID? --

[Bug 100375] forced EDID's can cause a amdgpu to null ptr deref

https://bugs.freedesktop.org/show_bug.cgi?id=100375 --- Comment #2 from Edward O'Callaghan --- (In reply to Michel Dänzer from comment #1) > set_root doesn't look directly related to amdgpu or drm, so this could be > memory corruption. KASAN might give more

[Bug 100375] forced EDID's can cause a amdgpu to null ptr deref

https://bugs.freedesktop.org/show_bug.cgi?id=100375 Michel Dänzer changed: What|Removed |Added Component|DRM/AMDgpu |DRM/other ---

[Bug 100426] Trine 3 takes long time to load

https://bugs.freedesktop.org/show_bug.cgi?id=100426 Bug ID: 100426 Summary: Trine 3 takes long time to load Product: Mesa Version: git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal

[Bug 100400] Game Valhalla Hills crash on startup

https://bugs.freedesktop.org/show_bug.cgi?id=100400 --- Comment #6 from Samuel Pitoiset --- Thanks for this very nice report. :) I can reproduce the issue with mesa/LLVM from today. -- You are receiving this mail because: You are the assignee for the

Re: [PATCH 13/19] drm: simplify the locking in the GETCRTC ioctl

On Wednesday, March 22, 2017 10:50:52 PM EDT Daniel Vetter wrote: > No need to grab both plane and crtc locks at the same time, we can do > them one after the other. If userspace races it'll get what it > deserves either way. > > This removes another user of drm_modeset_lock_crtc. There's only

Re: [PATCH 00/19] wire acquire ctx through legacy modeset paths

Patches 2-5, 9-12, 14-19: Reviewed-by: Harry Wentland Patches 1,13: Questions in response to those patches Patches 6-8: Acked-by: Harry Wentland Looks like a nice cleanup. Harry On Wednesday, March 22, 2017 10:50:39 PM EDT Daniel Vetter wrote:

[PATCH v2 01/10] drm/nouveau: Use drm_mode_set_crtcinfo() to compensate for vscan / ilace

* drm_mode_set_crtcinfo() does compensation for interlace and doublescan timing effects already, so do it first and use the compensated figures instead of the constant "vscan / ilace" terms that we had before. * Also prefer using the mode->crtc_* fields generally instead of the

[PATCH v2 03/10] drm/nouveau: Pass mode-dependent AVI and Vendor HDMI InfoFrames to NVKM

Now that we have mechanism by which to pass mode-dependent HDMI InfoFrames to the low-level hardware driver, it is incumbent upon us to do so. Signed-off-by: Alastair Bridgewater --- drivers/gpu/drm/nouveau/nv50_display.c | 30 +- 1

[PATCH v2 06/10] drm/nouveau: Use supplied HDMI InfoFrames on GT215 hardware

Now that we have the InfoFrame data being provided, for the most part, program the hardware to use it. While we're here, and since the functionality will come in handy for supporting 3D stereoscopy, implement setting the Vendor ("generic") InfoFrame. Also don't enable any AVI or Vendor InfoFrame

Re: [RFC v2 05/11] v4l2-core: Don't sync cache for a buffer if so requested

On Thu, Dec 15, 2016 at 6:24 PM, Laurent Pinchart wrote: > From: Samu Onkalo > > The user may request to the driver (vb2) to skip the cache maintenance > operations in case the buffer does not need cache synchronisation, e.g. in >

[PATCH v2 04/10] drm/nouveau: Add mechanism to convert HDMI InfoFrames to hardware format

HDMI InfoFrames are passed to NVKM as bags of bytes, but the hardware needs them to be packed into words. Rather than having four (or more) copies of the packing logic introduce a single copy now, in a central place. We currently need these for AVI and Vendor InfoFrames, but we may also expect

  1   2   >