Re: [Intel-gfx] [PATCH 02/15] drm: Remove drm_modeset_(un)lock_crtc

On Tue, Apr 4, 2017 at 12:13 AM, kbuild test robot wrote: > [if your patch is applied to the wrong git tree, please drop us a note to > help improve the system] It should compile just fine on latest linux-next (if there is one) where this code in vmwgfx is already removed. Well

Re: [RFC] DRM synchronisation objects

On 4 April 2017 at 14:27, Dave Airlie wrote: > This series enhances my previous semaphore work on for amdgpu, > with a generic DRM sync object. (drm_syncobj). > > It first enhances sync_file to have a type/flags so we can have > different semantics for different sync files, and

[PATCH 4/8] sync_file: add a mutex to protect fence and callback members. (v4)

From: Dave Airlie This patch allows the underlying fence in a sync_file to be changed or set to NULL. This isn't currently required but for Vulkan semaphores we need to be able to swap and reset the fence. In order to faciliate this, it uses rcu to protect the fence, along

[PATCH 7/8] amdgpu/cs: split out fence dependency checking

From: Dave Airlie This just splits out the fence depenency checking into it's own function to make it easier to add semaphore dependencies. Signed-off-by: Dave Airlie --- drivers/gpu/drm/amd/amdgpu/amdgpu_cs.c | 86 +++--- 1

[PATCH 8/8] amdgpu: use sync file for shared semaphores (v2)

From: Dave Airlie This creates a new interface for amdgpu with ioctls to create/destroy/import and export shared semaphores using sem object backed by the sync_file code. The semaphores are not installed as fd (except for export), but rather like other driver internal objects

[RFC] DRM synchronisation objects

This series enhances my previous semaphore work on for amdgpu, with a generic DRM sync object. (drm_syncobj). It first enhances sync_file to have a type/flags so we can have different semantics for different sync files, and a wait to retrieve the type of sync_file for userspace. Then it adds drm

[PATCH 6/8] drm/syncobj: add semaphore support helpers.

From: Dave Airlie This just adds two helper interfaces to bridge the gap from drivers to sync_file for the semaphore objects. These will be used by the amdgpu driver. Signed-off-by: Dave Airlie --- drivers/gpu/drm/drm_syncobj.c | 72

[PATCH 5/8] sync_file: add support for a semaphore object

From: Dave Airlie This object can be used to implement the Vulkan semaphores. The object behaviour differs from fence, in that you can replace the underlying fence, and you cannot merge semaphores. Signed-off-by: Dave Airlie ---

[PATCH 3/8] drm: introduce sync objects as sync file objects with no fd

From: Dave Airlie Sync objects are new toplevel drm object, that have the same semantics as sync_file objects, but without requiring an fd to be consumed to support them. This patch just enables the DRM interface to create these objects, it doesn't actually provide any

[PATCH 1/8] sync_file: add type/flags to sync file object creation.

From: Dave Airlie This allows us to create sync files with different semantics, and clearly define the interoperation between them it also provides flags to allow for tweaks on those semantics. This provides a validation interface for drivers that accept types from userspace

[PATCH 2/8] sync_file: export some interfaces needed by drm sync objects.

From: Dave Airlie These are just alloc and fdget interfaces needed by the drm sync objects code. Signed-off-by: Dave Airlie --- drivers/dma-buf/sync_file.c | 21 +++-- include/linux/sync_file.h | 3 ++- 2 files changed, 21

[git pull] drm fixes for v4.11-rc6

Hi Linus, I'm going to be away for the latter part of this week, and early next week, so I probably won't get to dequeue any more fixes before -rc6, if anyone has any urgent fixes they can get Daniel's help and maybe send them to you direct, I don't know of anything that is that urgent, hopefully

[drm:drm-syncobj 2/8] drivers/dma-buf/sw_sync.c:318:37: sparse: not enough arguments for function sync_file_create

tree: git://people.freedesktop.org/~airlied/linux.git drm-syncobj head: af9b558e5436d76fde927fd1f68cc35adec4d6ea commit: e9069d711a815ca17b9bf687b935ae8383b4565e [2/8] sync_file: add type/flags to sync file object creation. reproduce: # apt-get install sparse git checkout

[drm:drm-syncobj 2/8] htmldocs: drivers/dma-buf/sync_file.c:81: warning: No description found for parameter 'type'

tree: git://people.freedesktop.org/~airlied/linux.git drm-syncobj head: af9b558e5436d76fde927fd1f68cc35adec4d6ea commit: e9069d711a815ca17b9bf687b935ae8383b4565e [2/8] sync_file: add type/flags to sync file object creation. reproduce: make htmldocs All warnings (new ones prefixed by >>):

[Bug 99515] SIGSEGV MAPERR on Android nougat-x86 with mesa 17.0.0rc

https://bugs.freedesktop.org/show_bug.cgi?id=99515 --- Comment #5 from Mauro Rossi --- In the previous post is what happened with x86_64 nougat-x86 build, for all mesa 17.0.x cycle. Here follows what still happens with mesa 17.0.3 with x86 build of nougat-x86. I hope by

Re: [PATCH 18/19] drm: Add acquire ctx parameter to ->set_config

I missed this one, and looks like it's already in. So a belated: Reviewed-by: Sinclair Yeh for the vmwgfx part On Wed, Mar 22, 2017 at 10:50:57PM +0100, Daniel Vetter wrote: > Surprisingly a lot of legacy drivers roll their own, for > runtime pm and because vmwgfx. > > Also

[drm:drm-syncobj 2/8] drivers//dma-buf/sw_sync.c:318:14: error: too few arguments to function 'sync_file_create'

tree: git://people.freedesktop.org/~airlied/linux.git drm-syncobj head: af9b558e5436d76fde927fd1f68cc35adec4d6ea commit: e9069d711a815ca17b9bf687b935ae8383b4565e [2/8] sync_file: add type/flags to sync file object creation. config: x86_64-rhel (attached as .config) compiler: gcc-6 (Debian

[Bug 195159] nouveau incorrect ACPI usgage results in ACPI Error : AE_AML_PACKAGE_LIMIT

https://bugzilla.kernel.org/show_bug.cgi?id=195159 Len Brown (l...@kernel.org) changed: What|Removed |Added CC||l...@kernel.org

[Bug 99515] SIGSEGV MAPERR on Android nougat-x86 with mesa 17.0.0rc

https://bugs.freedesktop.org/show_bug.cgi?id=99515 --- Comment #4 from Mauro Rossi --- Hi, the problem has disappeared in the last week, I've seen a series of commits for radeonsi, but could some developer point out what changes have been done, which may have corrected a

[Bug 193651] Amdgpu error messages at boot with Amd RX460

https://bugzilla.kernel.org/show_bug.cgi?id=193651 --- Comment #20 from Christian Lanig (christian.la...@gmail.com) --- This bug report is partly a duplicate of that one: https://bugs.freedesktop.org/show_bug.cgi?id=100443 I'm getting the same AVS/Powerplay messages, updating the firmware didn't

[PATCH v4] drm: Add DPCD definitions for DP 1.4 DSC feature

From: "Navare, Manasi D" Display stream compression is supported on DP 1.4 DP devices. This patch adds the corersponding DPCD register definitions for DSC. v4: * Add DSC Enable DPCD register def (Ander) v3: * Add some SHIFTS and MASKS for uniformity (Jani Nikula) v2:

Re: [Intel-gfx] [PATCH v3] drm: Add DPCD definitions for DP 1.4 DSC feature

On Thu, Mar 16, 2017 at 03:47:46PM +0200, Ander Conselvan De Oliveira wrote: > On Tue, 2017-03-14 at 13:01 -0700, Manasi Navare wrote: > > From: "Navare, Manasi D" > > > > Display stream compression is supported on DP 1.4 DP > > devices. This patch adds the

GSOC(Xorg)

Hi all, I'm Christian Lockley I'm wondering if it's too late to apply for GSOC if so I understand and will apply next year. It not, is the DRM kernel janitor position still open? While I don't have kernel or graphics experience I do know C and Java. If this position is available I'd like to work

Re: [Intel-gfx] [PATCH 02/15] drm: Remove drm_modeset_(un)lock_crtc

Hi Daniel, [auto build test ERROR on next-20170330] [cannot apply to drm/drm-next drm-intel/for-linux-next robclark/msm-next v4.9-rc8 v4.9-rc7 v4.9-rc6 v4.11-rc5] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: MAINTAINERS: 4.12 git pulls by -rc6 or wait

On 4 April 2017 at 05:51, Dave Airlie wrote: > Just so everyone is aware we are running a hard and fast rule of > everything in linux-next by rc6 this time around, so if your tree is > directly included in linux-next that means everything needs to be in > drm-next by the end of

Re: Proposal for RandR version 1.6, Leases and EDID-based output grabs

On Mon, Apr 03, 2017 at 09:41:34AM -0700, Keith Packard wrote: > Daniel Vetter writes: > > > Hm, if you restrict getresources and getplanes, you'll get your leased > > objects query api. Iirc that part was missing in your kernel patch. And it > > gives you exaclty what you want:

Re: [Intel-gfx] [PATCH] dim: Add apply-pull command

On Mon, Apr 03, 2017 at 06:17:51PM +0300, Jani Nikula wrote: > On Thu, 30 Mar 2017, Daniel Vetter wrote: > > I'm getting real lazy, let's start scripting this. Very rough draft, > > but adds a Link: (patchwork tracks pull requests too, maybe we'll > > start CI-ing them

Re: [PATCH 01/15] drm: Make drm_modeset_lock_crtc internal

Hi Daniel, [auto build test ERROR on next-20170330] [also build test ERROR on v4.11-rc5] [cannot apply to drm/drm-next drm-intel/for-linux-next robclark/msm-next v4.9-rc8 v4.9-rc7 v4.9-rc6] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH 1/2] drm: Add new DRM_IOCTL_MODE_GETPLANE2

On Sat, Apr 1, 2017 at 2:47 PM, Rob Clark wrote: > On Tue, Dec 20, 2016 at 7:12 PM, Kristian H. Kristensen > wrote: >> From: "Kristian H. Kristensen" >> >> This new ioctl exctends DRM_IOCTL_MODE_GETPLANE, by returning >>

Re: [git pull] vmwgfx-next

On Sun, Apr 02, 2017 at 08:11:12PM +0200, Daniel Vetter wrote: > On Fri, Mar 31, 2017 at 04:32:55PM -0700, Sinclair Yeh wrote: > > Hi Dave, > > > > This series enables atomic mode set for vmwgfx. A number of features and > > larger fixes are also included. > > > > The following changes since

[PATCH 3/3] [v5] drm/i915: Add format modifiers for Intel

This was based on a patch originally by Kristian. It has been modified pretty heavily to use the new callbacks from the previous patch. v2: - Add LINEAR and Yf modifiers to list (Ville) - Combine i8xx and i965 into one list of formats (Ville) - Allow 1010102 formats for Y/Yf tiled (Ville)

Re: [PATCH 6/15] dt-bindings: display: sun4i: Add HDMI display bindings

Hi Rob, On Wed, Mar 15, 2017 at 12:26:22PM -0500, Rob Herring wrote: > > +HDMI Encoder > > + > > + > > +The HDMI Encoder supports the HDMI video and audio outputs, and does > > +CEC. It is one end of the pipeline. > > + > > +Required properties: > > + - compatible: value must be one

Re: [PATCH libdrm 2/2] tegra: update symbol-check

On Mon, Apr 3, 2017 at 6:59 PM, Emil Velikov wrote: > On 29 March 2017 at 23:24, Erik Faye-Lund wrote: >> I get a few more symbols in my build tegra-libraries, so let's >> include these in the whitelist as well. >> >> While we're at it, update the

[pull] drm/msm: msm-fixes for 4.11-rc6

Sorry, meant to send this a bit sooner.. a few small fixes for 4.11 The following changes since commit 3a2d78228a4fd3dadff2b528528aa8901f724a87: Merge tag 'drm-misc-fixes-2017-03-31' of git://anongit.freedesktop.org/git/drm-misc into drm-fixes (2017-03-31 17:29:26 +1000) are available in the

Re: [PATCH] drm/amdgpu: Fix a NULL deref in amdgpu_vm_add_prt_cb()

On Mon, Apr 3, 2017 at 2:53 PM, Harry Wentland wrote: > Reviewed-by: Harry Wentland > > Harry > Applied. thanks! Alex > > On 2017-04-03 02:41 PM, Dan Carpenter wrote: >> >> We accidentally dereference "cb" if the kmalloc() fails. >> >> Fixes:

Re: [PATCH 2/2] drm/amd/powerplay: fix a couple locking issues

On Mon, Apr 3, 2017 at 2:42 PM, Dan Carpenter wrote: > We should return unlock on the error path in pp_dpm_dispatch_tasks() > and there is a double lock bug in pp_dpm_set_sclk_od(). > > Fixes: 2a5071056e6a ("drm/amd/powerplay: add global PowerPlay mutex.") >

Re: [PATCH 1/2] drm/amd/powerplay: fix pp_dpm_get_current_power_state()

On Mon, Apr 3, 2017 at 2:41 PM, Dan Carpenter wrote: > This switch statement is missing breaks. > > Fixes: 2a5071056e6a ("drm/amd/powerplay: add global PowerPlay mutex.") > Signed-off-by: Dan Carpenter Applied. thanks! > > diff --git

[Bug 100542] radeon xt9650/ powerpc /debian - videos are blue

https://bugs.freedesktop.org/show_bug.cgi?id=100542 --- Comment #2 from richard --- rich@debian:~$ glxinfo | grep render direct rendering: Yes OpenGL renderer string: Software Rasterizer GL_EXT_vertex_array_bgra, GL_NV_conditional_render, rich@debian:~$ lspci | grep

[Bug 100542] radeon xt9650/ powerpc /debian - videos are blue

https://bugs.freedesktop.org/show_bug.cgi?id=100542 --- Comment #1 from richard --- have already installed firmware-linux-nonfree -- You are receiving this mail because: You are the assignee for the bug.___ dri-devel mailing

[Bug 100542] radeon xt9650/ powerpc /debian - videos are blue

https://bugs.freedesktop.org/show_bug.cgi?id=100542 Bug ID: 100542 Summary: radeon xt9650/ powerpc /debian - videos are blue Product: Mesa Version: unspecified Hardware: PowerPC OS: Linux (All) Status: NEW

MAINTAINERS: 4.12 git pulls by -rc6 or wait

Just so everyone is aware we are running a hard and fast rule of everything in linux-next by rc6 this time around, so if your tree is directly included in linux-next that means everything needs to be in drm-next by the end of this week. If your tree is directly included in linux-next I'd still

Re: Vulkan WSI+VK_KHR_display for KMS/DRM?

On Fri 31 Mar 2017, "Keith Packard" wrote: > > Krh hacked up kmscube into vkcube which can run vulkan directly on kms, > but that doesn't use any of the WSI apis and VK_KHR_display > extension. Is anyone thinking that might be a good idea to do, or should > we just keep on hacking things like

Google Summer of Code time conflict

I forgot to mention in my application that I have classes until june 7. Also, Dave Airlie said he might be willing to mentor me: https://lists.freedesktop.org/archives/mesa-dev/2017-February/144078.html Jacob Lifshay ___ dri-devel mailing list

[PATCHv3 22/22] staging/android: Update Ion TODO list

Most of the items have been taken care of by a clean up series. Remove the completed items and add a few new ones. Signed-off-by: Laura Abbott --- drivers/staging/android/TODO | 21 - 1 file changed, 4 insertions(+), 17 deletions(-) diff --git

[PATCHv3 21/22] staging: android: ion: Set query return value

This never got set in the ioctl. Properly set a return value of 0 on success. Signed-off-by: Laura Abbott --- drivers/staging/android/ion/ion.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/staging/android/ion/ion.c b/drivers/staging/android/ion/ion.c index

[PATCHv3 20/22] staging: android: ion: Remove ion_handle and ion_client

ion_handle was introduced as an abstraction to represent a reference to a buffer via an ion_client. As frameworks outside of Ion evolved, the dmabuf emerged as the preferred standard for use in the kernel. This has made the ion_handle an unnecessary abstraction and prone to race conditions.

[PATCHv3 18/22] staging: android: ion: Rework heap registration/enumeration

The current model of Ion heap registration is based on the outdated model of board files. The replacement for board files (devicetree) isn't a good replacement for what Ion wants to do. In actuality, Ion wants to show what memory is available in the system for something else to figure out what to

[PATCHv3 19/22] staging: android: ion: Drop ion_map_kernel interface

Nobody uses this interface externally. Drop it. Signed-off-by: Laura Abbott --- drivers/staging/android/ion/ion.c | 59 --- 1 file changed, 59 deletions(-) diff --git a/drivers/staging/android/ion/ion.c

[PATCHv3 14/22] staging: android: ion: Stop butchering the DMA address

Now that we have proper caching, stop setting the DMA address manually. It should be set after properly calling dma_map. Signed-off-by: Laura Abbott --- drivers/staging/android/ion/ion.c | 17 + 1 file changed, 1 insertion(+), 16 deletions(-) diff --git

[PATCHv3 16/22] staging: android: ion: Get rid of ion_phys_addr_t

Once upon a time, phys_addr_t was not everywhere in the kernel. These days it is used enough places that having a separate Ion type doesn't make sense. Remove the extra type and just use phys_addr_t directly. Signed-off-by: Laura Abbott --- drivers/staging/android/ion/ion.h

[PATCHv3 13/22] staging: android: ion: Use CMA APIs directly

When CMA was first introduced, its primary use was for DMA allocation and the only way to get CMA memory was to call dma_alloc_coherent. This put Ion in an awkward position since there was no device structure readily available and setting one up messed up the coherency model. These days, CMA can

[PATCHv3 17/22] staging: android: ion: Collapse internal header files

Ion current has ion_priv.h and ion.h as header files. ion.h was intended to be used for public APIs but Ion never ended up really having anything public. Combine the two headers so there is only one internal header. Signed-off-by: Laura Abbott ---

[PATCHv3 15/22] staging: android: ion: Break the ABI in the name of forward progress

Several of the Ion ioctls were designed in such a way that they necessitate compat ioctls. We're breaking a bunch of other ABIs and cleaning stuff up anyway so let's follow the ioctl guidelines and clean things up while everyone is busy converting things over anyway. As part of this, also remove

[PATCHv3 11/22] staging: android: ion: Remove duplicate ION_IOC_MAP

ION_IOC_MAP is the same as ION_IOC_SHARE. We really don't need two identical interfaces. Remove it. Signed-off-by: Laura Abbott --- drivers/staging/android/ion/compat_ion.c | 1 - drivers/staging/android/ion/ion-ioctl.c | 1 - drivers/staging/android/uapi/ion.h | 10

[PATCHv3 12/22] staging: android: ion: Remove old platform support

Device specific platform support has been haphazard for Ion. There have been several independent attempts and there are still objections to what bindings exist right now. Just remove everything for a fresh start. Signed-off-by: Laura Abbott ---

[PATCHv3 10/22] staging: android: ion: Remove import interface

With the expansion of dma-buf and the move for Ion to be come just an allocator, the import mechanism is mostly useless. There isn't a kernel component to Ion anymore and handles are private to Ion. Remove this interface. Signed-off-by: Laura Abbott ---

[PATCHv3 03/22] staging: android: ion: Remove dmap_cnt

The reference counting of dma_map calls was removed. Remove the associated counter field as well. Signed-off-by: Laura Abbott --- drivers/staging/android/ion/ion_priv.h | 2 -- 1 file changed, 2 deletions(-) diff --git a/drivers/staging/android/ion/ion_priv.h

[PATCHv3 05/22] staging: android: ion: Duplicate sg_table

Ion currently returns a single sg_table on each dma_map call. This is incorrect for later usage. Signed-off-by: Laura Abbott --- drivers/staging/android/ion/ion.c | 30 +- 1 file changed, 29 insertions(+), 1 deletion(-) diff --git

[PATCHv3 08/22] staging: android: ion: Remove crufty cache support

Now that we call dma_map in the dma_buf API callbacks there is no need to use the existing cache APIs. Remove the sync ioctl and the existing bad dma_sync calls. Explicit caching can be handled with the dma_buf sync API. Signed-off-by: Laura Abbott ---

[PATCHv3 02/22] cma: Introduce cma_for_each_area

Frameworks (e.g. Ion) may want to iterate over each possible CMA area to allow for enumeration. Introduce a function to allow a callback. Signed-off-by: Laura Abbott --- include/linux/cma.h | 2 ++ mm/cma.c| 14 ++ 2 files changed, 16 insertions(+)

[PATCHv3 04/22] staging: android: ion: Remove alignment from allocation field

The align field was supposed to be used to specify the alignment of the allocation. Nobody actually does anything with it except to check if the alignment specified is out of bounds. Since this has no effect on the actual allocation, just remove it. Signed-off-by: Laura Abbott

[PATCHv3 09/22] staging: android: ion: Remove custom ioctl interface

Ion is now moving towards a unified interfact. This makes the custom ioctl interface unneeded. Remove it. Signed-off-by: Laura Abbott --- drivers/staging/android/ion/compat_ion.c | 40 -- drivers/staging/android/ion/ion-ioctl.c| 11

[PATCHv3 07/22] staging: android: ion: Remove page faulting support

The new method of syncing with dma_map means that the page faulting sync implementation is no longer applicable. Remove it. Signed-off-by: Laura Abbott --- drivers/staging/android/ion/ion.c | 117 -- 1 file changed, 117 deletions(-) diff

[PATCHv3 06/22] staging: android: ion: Call dma_map_sg for syncing and mapping

Technically, calling dma_buf_map_attachment should return a buffer properly dma_mapped. Add calls to dma_map_sg to begin_cpu_access to ensure this happens. As a side effect, this lets Ion buffers take advantage of the dma_buf sync ioctls. Signed-off-by: Laura Abbott ---

[PATCHv3 00/22] Ion clean up in preparation in moving out of staging

Hi, This is v3 of the series to do some serious Ion cleanup in preparation for moving out of staging. I didn't hear much on v2 so I'm going to assume people are okay with the series as is. I know there were still some open questions about moving away from /dev/ion but in the interest of small

[PATCHv3 01/22] cma: Store a name in the cma structure

Frameworks that may want to enumerate CMA heaps (e.g. Ion) will find it useful to have an explicit name attached to each region. Store the name in each CMA structure. Signed-off-by: Laura Abbott --- v3: Added default name suggestion per Sumit. Fixup powerpc call site. ---

Re: [PATCH] drm/amdgpu: Fix a NULL deref in amdgpu_vm_add_prt_cb()

Reviewed-by: Harry Wentland Harry On 2017-04-03 02:41 PM, Dan Carpenter wrote: We accidentally dereference "cb" if the kmalloc() fails. Fixes: 451bc8eb8fe6 ("drm/amdgpu: fix PRT teardown on VM fini v3") Signed-off-by: Dan Carpenter diff

[PATCH 2/2] drm/amd/powerplay: fix a couple locking issues

We should return unlock on the error path in pp_dpm_dispatch_tasks() and there is a double lock bug in pp_dpm_set_sclk_od(). Fixes: 2a5071056e6a ("drm/amd/powerplay: add global PowerPlay mutex.") Signed-off-by: Dan Carpenter diff --git

[PATCH] drm/amdgpu: Fix a NULL deref in amdgpu_vm_add_prt_cb()

We accidentally dereference "cb" if the kmalloc() fails. Fixes: 451bc8eb8fe6 ("drm/amdgpu: fix PRT teardown on VM fini v3") Signed-off-by: Dan Carpenter diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c index

[PATCH 1/2] drm/amd/powerplay: fix pp_dpm_get_current_power_state()

This switch statement is missing breaks. Fixes: 2a5071056e6a ("drm/amd/powerplay: add global PowerPlay mutex.") Signed-off-by: Dan Carpenter diff --git a/drivers/gpu/drm/amd/powerplay/amd_powerplay.c b/drivers/gpu/drm/amd/powerplay/amd_powerplay.c index

Re: [PATCH 12/15] drm: Add acquire ctx to ->gamma_set hook

vmwgfx part: Reviewed-by: Sinclair Yeh On Mon, Apr 03, 2017 at 10:33:01AM +0200, Daniel Vetter wrote: > Atomic helpers really want this instead of the hacked-up legacy > backoff trick, which unfortunately prevents drivers from using their > own private drm_modeset_locks. > >

[Bug 195231] Continuous messages of "*ERROR* UVD not responding, trying to reset the VCPU!!!" and frozen screen

https://bugzilla.kernel.org/show_bug.cgi?id=195231 --- Comment #8 from Rogério Brito (rbr...@ime.usp.br) --- If you need more information, please let me know and I will try my best to provide anything. Thanks, Rogério. -- You are receiving this mail because: You are watching the assignee of

[Bug 195231] Continuous messages of "*ERROR* UVD not responding, trying to reset the VCPU!!!" and frozen screen

https://bugzilla.kernel.org/show_bug.cgi?id=195231 --- Comment #7 from Rogério Brito (rbr...@ime.usp.br) --- Created attachment 255751 --> https://bugzilla.kernel.org/attachment.cgi?id=255751=edit Xorg log with radeon.runpm=0 -- You are receiving this mail because: You are watching the

[Bug 195231] Continuous messages of "*ERROR* UVD not responding, trying to reset the VCPU!!!" and frozen screen

https://bugzilla.kernel.org/show_bug.cgi?id=195231 --- Comment #6 from Rogério Brito (rbr...@ime.usp.br) --- Created attachment 255749 --> https://bugzilla.kernel.org/attachment.cgi?id=255749=edit dmesg log with radeon.runpm=0 -- You are receiving this mail because: You are watching the

[Bug 195231] Continuous messages of "*ERROR* UVD not responding, trying to reset the VCPU!!!" and frozen screen

https://bugzilla.kernel.org/show_bug.cgi?id=195231 --- Comment #5 from Rogério Brito (rbr...@ime.usp.br) --- Created attachment 255747 --> https://bugzilla.kernel.org/attachment.cgi?id=255747=edit Xorg log when it crashes -- You are receiving this mail because: You are watching the assignee

[Bug 195231] Continuous messages of "*ERROR* UVD not responding, trying to reset the VCPU!!!" and frozen screen

https://bugzilla.kernel.org/show_bug.cgi?id=195231 --- Comment #4 from Rogério Brito (rbr...@ime.usp.br) --- Created attachment 255745 --> https://bugzilla.kernel.org/attachment.cgi?id=255745=edit dmesg log with showing the problem and with oops -- You are receiving this mail because: You are

[Bug 195231] Continuous messages of "*ERROR* UVD not responding, trying to reset the VCPU!!!" and frozen screen

https://bugzilla.kernel.org/show_bug.cgi?id=195231 --- Comment #3 from Rogério Brito (rbr...@ime.usp.br) --- Dear Alex, (In reply to Alex Deucher from comment #2) > Please attach your xorg log and dmesg output. Does appending radeon.runpm=0 > on the kernel command line in grub help? I'm

Re: linux-next: build failure after merge of the drm-misc tree

Thanks for this. This and "drm/vmwgfx: merge fixup for set_config API change": Reviewed-by: Sinclair Yeh On Mon, Apr 03, 2017 at 01:31:29PM +1000, Stephen Rothwell wrote: > Hi all, > > After merging the drm-misc tree, today's linux-next build (x86_64 > allmodconfig) failed

Re: [PATCH libdrm] configure.ac: bring back pthread-stubs check

On 31 March 2017 at 00:17, Eric Engestrom wrote: > On Thursday, 2017-03-30 18:01:12 +0100, Emil Velikov wrote: >> Accidentally removed with earlier commit. Although rather than simply >> adding the check for all platforms, use the same heuristics as we do in >> mesa. >> >>

[Bug 100530] Linking of etnaviv_cmd_stream_test is broken

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

Re: [PATCH libdrm 2/2] tegra: update symbol-check

On 29 March 2017 at 23:24, Erik Faye-Lund wrote: > I get a few more symbols in my build tegra-libraries, so let's > include these in the whitelist as well. > > While we're at it, update the comment at the top. > > Signed-off-by: Erik Faye-Lund R-B and

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

On Sun, Apr 02, 2017 at 08:54:14AM +0200, Øyvind A. Holm wrote: > On 2017-03-27 15:17:54, Sinclair Yeh wrote: > > From: Øyvind A. Holm > > > > This reverts commit 2d8e60e8b074 ("drm/vmwgfx: Replace numeric > > parameter like 0444 with macro") > > [...] > > index

Re: [PATCH libdrm 1/2] tests/tegra: add openclose test to check-target

Hi Erik, On 29 March 2017 at 23:24, Erik Faye-Lund wrote: > This makes the test run under the 'make check'-taget. > The test doesn't do anything useful but open/close the tegra device. Do you see much value in it or we can drop it all together ? Thierry how do you feel on

Re: [PATCH 2/2] Android: disable pointer-arith and enum-conversion

On 22 March 2017 at 19:05, Rob Herring wrote: > Disable some more warnings from clang. These don't appear to be warnings > worth fixing. > Maybe we should, but considering nobody has bothered in a long time let's go with this for now. R-b and pushed the series. -Emil

Re: [PATCHv6 05/10] s5p-cec.txt: document the HDMI controller phandle

On Fri, Mar 31, 2017 at 02:20:31PM +0200, Hans Verkuil wrote: > From: Hans Verkuil > > Update the bindings documenting the new hdmi phandle. > > Signed-off-by: Hans Verkuil > Acked-by: Krzysztof Kozlowski > CC:

[PULL] Synopsys Media Formats

Hi Mauro, Here's the pull for Neil's new media formats. We're using a topic branch in drm-misc, so it will not change. Once you have acked, we'll pull this in and apply the rest of Neil's set. Thanks, Sean The following changes since commit a71c9a1c779f2499fb2afc0553e543f18aff6edf: Linux

Re: [PATCH] dma-buf: align debugfs output

Hi Russell, On 31 March 2017 at 15:33, Russell King wrote: > Align the heading with the values output from debugfs. > > Signed-off-by: Russell King Thanks for your patch; applied to drm-misc-next. > --- > drivers/dma-buf/dma-buf.c | 3

Re: [PATCH libdrm] xf86drm: remove memory leaks in drmGetBusid/drmGetReservedContextList

On 28 March 2017 at 16:35, Nicolai Hähnle wrote: > On 27.03.2017 04:09, Seung-Woo Kim wrote: >> >> In error path of drmGetBusid() and drmGetReservedContextList(), >> there are memory leaks for error path. So this removes them. >> >> Signed-off-by: Seung-Woo Kim

Re: [PATCH 7/7 v2] drm/radeon: Refuse to migrate a prime BO to VRAM. (v2)

Am 03.04.2017 um 17:51 schrieb Alex Deucher: On Mon, Apr 3, 2017 at 4:24 AM, Christian König wrote: Am 03.04.2017 um 05:35 schrieb r...@ubuntu.com: From: Christopher James Halse Rogers BOs shared via dma-buf, either imported

Re: [PATCH libdrm 0/3] remove build warnings for exynos

On 31 March 2017 at 04:30, Seung-Woo Kim wrote: > For exynos module for libdrm, there are some build warnings, so this patch > series remove them. > R-b and pushed the series. Thanks Emil ___ dri-devel mailing list

Re: [PATCH] tests/exynos: fix invalid code of error path in g2d test

On 20 March 2017 at 00:52, Seung-Woo Kim wrote: > This patch fixes invalid code of error path including NULL > deference and leak in g2d test. > Thanks for the update. R-b and pushed to master. For future do add v2 in the subject prefix (git send-email -v2 ...). It makes

Re: [PATCH 3/6] drm/ttm: add TTM_PL_FLAG_CONTIGUOUS v2

On 31.03.2017 11:47, Christian König wrote: From: Christian König This allows drivers to specify if they need a contiguous allocation or not. v2: use space instead of tab Signed-off-by: Christian König Patches 1-3: Reviewed-by: Nicolai

Re: [PATCH 6/6] drm/amdgpu: handle CPU access for split VRAM buffers

On 31.03.2017 11:47, Christian König wrote: From: Christian König This avoids merging them together on page fault. Signed-off-by: Christian König Acked-by: Michel Dänzer ---

Re: [PATCH 5/6] drm/amdgpu: use TTM_PL_FLAG_CONTIGUOUS

On 31.03.2017 11:47, Christian König wrote: From: Christian König Implement AMDGPU_GEM_CREATE_VRAM_CONTIGUOUS using TTM_PL_FLAG_CONTIGUOUS instead of a placement limit. That allows us to better handle CPU accessible placements. Signed-off-by: Christian König

Re: [PATCH libdrm 3/3] amdgpu: add REPLACE and CLEAR checking for VA op (v2)

On 3 April 2017 at 11:54, Marek Olšák wrote: > On Mon, Apr 3, 2017 at 10:27 AM, Nicolai Hähnle wrote: >> From: Junwei Zhang >> >> v2: fix indent >> >> Signed-off-by: Junwei Zhang >> Reviewed-by: Nicolai Hähnle

Re: [ANNOUNCE] libdrm 2.4.76

On 30 March 2017 at 07:04, Jani Nikula wrote: > On Wed, 29 Mar 2017, Marek Olšák wrote: >> libdrm 2.4.76 has been released. >> >> git tag: libdrm-2.4.76 > > Should the release tags be signed? For a couple of years that has been > the practise until

[Bug 195231] Continuous messages of "*ERROR* UVD not responding, trying to reset the VCPU!!!" and frozen screen

https://bugzilla.kernel.org/show_bug.cgi?id=195231 Alex Deucher (alexdeuc...@gmail.com) changed: What|Removed |Added CC|

Re: [PATCHv4 25/29] drm/omap: displays: panel-dpi: Support for handling backlight devices

On Thu, Mar 30, 2017 at 02:15:25PM +0300, Tomi Valkeinen wrote: > From: Peter Ujfalusi > > The associated backlight device can be configured via DT by providing the > phandle to the device. > > If the backlight device is configured, the driver can manage the backligt >

[PATCH] dim: add backmerge tool

Does a few sanity checks to avoid common gotchas: - make sure the backmerge is in drm-tip already - check that git rerere resolves all conflict, and cuation if not - merge commit template. Cc: Sean Paul Signed-off-by: Daniel Vetter ---

Re: [PATCH 7/7 v2] drm/radeon: Refuse to migrate a prime BO to VRAM. (v2)

On Mon, Apr 3, 2017 at 4:24 AM, Christian König wrote: > Am 03.04.2017 um 05:35 schrieb r...@ubuntu.com: >> >> From: Christopher James Halse Rogers >> >> >> BOs shared via dma-buf, either imported or exported, cannot sensibly be >>

  1   2   >