dri-devel June 2015

dri-devel@lists.freedesktop.org

188 participants
1140 discussions

[PATCH] drm/atomic: Handle vblank events in atomic ioctl correctly.
by Maarten Lankhorst 15 Jun '15

15 Jun '15

All users of async updates seem to clear clear crtc_state->event correctly, so move destroying vblank event to crtc_destroy_state. This is better than manually free'ing it in the atomic ioctl, since this code seems to do it wrong. While we're at it handle -EDEADLK from atomic_commit correctly, because the check might fail otherwise if it takes additional state. Signed-off-by: Maarten Lankhorst <maarten.lankhorst(a)linux.intel.com> Reviewed-by: Daniel Stone <daniels(a)collabora.com> --- drivers/gpu/drm/drm_atomic.c | 44 +++++++++---------------------------- drivers/gpu/drm/drm_atomic_helper.c | 15 +++++++++++++ 2 files changed, 25 insertions(+), 34 deletions(-) diff --git a/drivers/gpu/drm/drm_atomic.c b/drivers/gpu/drm/drm_atomic.c index c7e59b074e62..097aa6d9a8c7 100644 --- a/drivers/gpu/drm/drm_atomic.c +++ b/drivers/gpu/drm/drm_atomic.c @@ -1328,17 +1328,6 @@ out: return e; } -static void destroy_vblank_event(struct drm_device *dev, - struct drm_file *file_priv, struct drm_pending_vblank_event *e) -{ - unsigned long flags; - - spin_lock_irqsave(&dev->event_lock, flags); - file_priv->event_space += sizeof e->event; - spin_unlock_irqrestore(&dev->event_lock, flags); - kfree(e); -} - static int atomic_set_prop(struct drm_atomic_state *state, struct drm_mode_object *obj, struct drm_property *prop, uint64_t prop_value) @@ -1534,13 +1523,18 @@ retry: if (arg->flags & DRM_MODE_ATOMIC_TEST_ONLY) { ret = drm_atomic_check_only(state); /* _check_only() does not free state, unlike _commit() */ - drm_atomic_state_free(state); + if (!ret) + drm_atomic_state_free(state); } else if (arg->flags & DRM_MODE_ATOMIC_NONBLOCK) { ret = drm_atomic_async_commit(state); } else { ret = drm_atomic_commit(state); } +fail: + if (ret == -EDEADLK) + goto backoff; + /* if succeeded, fixup legacy plane crtc/fb ptrs before dropping * locks (ie. while it is still safe to deref plane->state). We * need to do this here because the driver entry points cannot @@ -1553,32 +1547,14 @@ retry: drm_framebuffer_reference(new_fb); plane->fb = new_fb; plane->crtc = plane->state->crtc; - } else { - plane->old_fb = NULL; - } - if (plane->old_fb) { - drm_framebuffer_unreference(plane->old_fb); - plane->old_fb = NULL; - } - } - - drm_modeset_drop_locks(&ctx); - drm_modeset_acquire_fini(&ctx); - return ret; - -fail: - if (ret == -EDEADLK) - goto backoff; - - if (arg->flags & DRM_MODE_PAGE_FLIP_EVENT) { - for_each_crtc_in_state(state, crtc, crtc_state, i) { - destroy_vblank_event(dev, file_priv, crtc_state->event); - crtc_state->event = NULL; + drm_framebuffer_unreference(plane->old_fb); } + plane->old_fb = NULL; } - drm_atomic_state_free(state); + if (ret) + drm_atomic_state_free(state); drm_modeset_drop_locks(&ctx); drm_modeset_acquire_fini(&ctx); diff --git a/drivers/gpu/drm/drm_atomic_helper.c b/drivers/gpu/drm/drm_atomic_helper.c index 536ae4da4665..0bb70c4da77a 100644 --- a/drivers/gpu/drm/drm_atomic_helper.c +++ b/drivers/gpu/drm/drm_atomic_helper.c @@ -2101,6 +2101,18 @@ drm_atomic_helper_crtc_duplicate_state(struct drm_crtc *crtc) } EXPORT_SYMBOL(drm_atomic_helper_crtc_duplicate_state); +static void destroy_vblank_event(struct drm_device *dev, + struct drm_pending_vblank_event *e) +{ + struct drm_file *file_priv = e->base.file_priv; + unsigned long flags; + + spin_lock_irqsave(&dev->event_lock, flags); + file_priv->event_space += sizeof e->event; + spin_unlock_irqrestore(&dev->event_lock, flags); + kfree(e); +} + /** * __drm_atomic_helper_crtc_destroy_state - release CRTC state * @crtc: CRTC object @@ -2115,6 +2127,9 @@ void __drm_atomic_helper_crtc_destroy_state(struct drm_crtc *crtc, { if (state->mode_blob) drm_property_unreference_blob(state->mode_blob); + + if (state->event) + destroy_vblank_event(crtc->dev, state->event); } EXPORT_SYMBOL(__drm_atomic_helper_crtc_destroy_state); -- 2.1.0

3 4

[PATCH] drm: Turn off Legacy Context Functions
by Peter Antoine 15 Jun '15

15 Jun '15

The context functions are not used by the i915 driver and should not be used by modeset drivers. These driver functions contain several bugs and security holes. This change makes these functions optional can be turned on by a setting, they are turned off by default for modeset driver with the exception of the Nova driver that may require them with an old version of libdrm. Signed-off-by: Peter Antoine <peter.antoine(a)intel.com> --- drivers/gpu/drm/drm_context.c | 48 +++++++++++++++++++++++++++++++++++ drivers/gpu/drm/drm_drv.c | 13 ++++++---- drivers/gpu/drm/drm_lock.c | 8 ++++++ drivers/gpu/drm/nouveau/nouveau_drm.c | 3 ++- include/drm/drmP.h | 23 +++++++++-------- 5 files changed, 78 insertions(+), 17 deletions(-) diff --git a/drivers/gpu/drm/drm_context.c b/drivers/gpu/drm/drm_context.c index 9b23525..f3ea657 100644 --- a/drivers/gpu/drm/drm_context.c +++ b/drivers/gpu/drm/drm_context.c @@ -53,6 +53,10 @@ struct drm_ctx_list { */ void drm_legacy_ctxbitmap_free(struct drm_device * dev, int ctx_handle) { + if (!drm_core_check_feature(dev, DRIVER_KMS_LEGACY_CONTEXT) && + drm_core_check_feature(dev, DRIVER_MODESET)) + return -EINVAL; + mutex_lock(&dev->struct_mutex); idr_remove(&dev->ctx_idr, ctx_handle); mutex_unlock(&dev->struct_mutex); @@ -87,6 +91,10 @@ static int drm_legacy_ctxbitmap_next(struct drm_device * dev) */ int drm_legacy_ctxbitmap_init(struct drm_device * dev) { + if (!drm_core_check_feature(dev, DRIVER_KMS_LEGACY_CONTEXT) && + drm_core_check_feature(dev, DRIVER_MODESET)) + return -EINVAL; + idr_init(&dev->ctx_idr); return 0; } @@ -101,6 +109,10 @@ int drm_legacy_ctxbitmap_init(struct drm_device * dev) */ void drm_legacy_ctxbitmap_cleanup(struct drm_device * dev) { + if (!drm_core_check_feature(dev, DRIVER_KMS_LEGACY_CONTEXT) && + drm_core_check_feature(dev, DRIVER_MODESET)) + return -EINVAL; + mutex_lock(&dev->struct_mutex); idr_destroy(&dev->ctx_idr); mutex_unlock(&dev->struct_mutex); @@ -119,6 +131,10 @@ void drm_legacy_ctxbitmap_flush(struct drm_device *dev, struct drm_file *file) { struct drm_ctx_list *pos, *tmp; + if (!drm_core_check_feature(dev, DRIVER_KMS_LEGACY_CONTEXT) && + drm_core_check_feature(dev, DRIVER_MODESET)) + return -EINVAL; + mutex_lock(&dev->ctxlist_mutex); list_for_each_entry_safe(pos, tmp, &dev->ctxlist, head) { @@ -161,6 +177,10 @@ int drm_legacy_getsareactx(struct drm_device *dev, void *data, struct drm_local_map *map; struct drm_map_list *_entry; + if (!drm_core_check_feature(dev, DRIVER_KMS_LEGACY_CONTEXT) && + drm_core_check_feature(dev, DRIVER_MODESET)) + return -EINVAL; + mutex_lock(&dev->struct_mutex); map = idr_find(&dev->ctx_idr, request->ctx_id); @@ -205,6 +225,10 @@ int drm_legacy_setsareactx(struct drm_device *dev, void *data, struct drm_local_map *map = NULL; struct drm_map_list *r_list = NULL; + if (!drm_core_check_feature(dev, DRIVER_KMS_LEGACY_CONTEXT) && + drm_core_check_feature(dev, DRIVER_MODESET)) + return -EINVAL; + mutex_lock(&dev->struct_mutex); list_for_each_entry(r_list, &dev->maplist, head) { if (r_list->map @@ -305,6 +329,10 @@ int drm_legacy_resctx(struct drm_device *dev, void *data, struct drm_ctx ctx; int i; + if (!drm_core_check_feature(dev, DRIVER_KMS_LEGACY_CONTEXT) && + drm_core_check_feature(dev, DRIVER_MODESET)) + return -EINVAL; + if (res->count >= DRM_RESERVED_CONTEXTS) { memset(&ctx, 0, sizeof(ctx)); for (i = 0; i < DRM_RESERVED_CONTEXTS; i++) { @@ -335,6 +363,10 @@ int drm_legacy_addctx(struct drm_device *dev, void *data, struct drm_ctx_list *ctx_entry; struct drm_ctx *ctx = data; + if (!drm_core_check_feature(dev, DRIVER_KMS_LEGACY_CONTEXT) && + drm_core_check_feature(dev, DRIVER_MODESET)) + return -EINVAL; + ctx->handle = drm_legacy_ctxbitmap_next(dev); if (ctx->handle == DRM_KERNEL_CONTEXT) { /* Skip kernel's context and get a new one. */ @@ -378,6 +410,10 @@ int drm_legacy_getctx(struct drm_device *dev, void *data, { struct drm_ctx *ctx = data; + if (!drm_core_check_feature(dev, DRIVER_KMS_LEGACY_CONTEXT) && + drm_core_check_feature(dev, DRIVER_MODESET)) + return -EINVAL; + /* This is 0, because we don't handle any context flags */ ctx->flags = 0; @@ -400,6 +436,10 @@ int drm_legacy_switchctx(struct drm_device *dev, void *data, { struct drm_ctx *ctx = data; + if (!drm_core_check_feature(dev, DRIVER_KMS_LEGACY_CONTEXT) && + drm_core_check_feature(dev, DRIVER_MODESET)) + return -EINVAL; + DRM_DEBUG("%d\n", ctx->handle); return drm_context_switch(dev, dev->last_context, ctx->handle); } @@ -420,6 +460,10 @@ int drm_legacy_newctx(struct drm_device *dev, void *data, { struct drm_ctx *ctx = data; + if (!drm_core_check_feature(dev, DRIVER_KMS_LEGACY_CONTEXT) && + drm_core_check_feature(dev, DRIVER_MODESET)) + return -EINVAL; + DRM_DEBUG("%d\n", ctx->handle); drm_context_switch_complete(dev, file_priv, ctx->handle); @@ -442,6 +486,10 @@ int drm_legacy_rmctx(struct drm_device *dev, void *data, { struct drm_ctx *ctx = data; + if (!drm_core_check_feature(dev, DRIVER_KMS_LEGACY_CONTEXT) && + drm_core_check_feature(dev, DRIVER_MODESET)) + return -EINVAL; + DRM_DEBUG("%d\n", ctx->handle); if (ctx->handle != DRM_KERNEL_CONTEXT) { if (dev->driver->context_dtor) diff --git a/drivers/gpu/drm/drm_drv.c b/drivers/gpu/drm/drm_drv.c index 3b3c4f5..e571711 100644 --- a/drivers/gpu/drm/drm_drv.c +++ b/drivers/gpu/drm/drm_drv.c @@ -584,11 +584,14 @@ struct drm_device *drm_dev_alloc(struct drm_driver *driver, if (drm_ht_create(&dev->map_hash, 12)) goto err_minors; - ret = drm_legacy_ctxbitmap_init(dev); - if (ret) { - DRM_ERROR("Cannot allocate memory for context bitmap.\n"); - goto err_ht; - } + if (drm_core_check_feature(dev, DRIVER_KMS_LEGACY_CONTEXT) || + !drm_core_check_feature(dev, DRIVER_MODESET)) + ret = drm_legacy_ctxbitmap_init(dev); + if (ret) { + DRM_ERROR( + "Cannot allocate memory for context bitmap.\n"); + goto err_ht; + } if (drm_core_check_feature(dev, DRIVER_GEM)) { ret = drm_gem_init(dev); diff --git a/drivers/gpu/drm/drm_lock.c b/drivers/gpu/drm/drm_lock.c index f861361..e73687e 100644 --- a/drivers/gpu/drm/drm_lock.c +++ b/drivers/gpu/drm/drm_lock.c @@ -61,6 +61,10 @@ int drm_legacy_lock(struct drm_device *dev, void *data, struct drm_master *master = file_priv->master; int ret = 0; + if (!drm_core_check_feature(dev, DRIVER_KMS_LEGACY_CONTEXT) && + drm_core_check_feature(dev, DRIVER_MODESET)) + return -EINVAL; + ++file_priv->lock_count; if (lock->context == DRM_KERNEL_CONTEXT) { @@ -153,6 +157,10 @@ int drm_legacy_unlock(struct drm_device *dev, void *data, struct drm_file *file_ struct drm_lock *lock = data; struct drm_master *master = file_priv->master; + if (!drm_core_check_feature(dev, DRIVER_KMS_LEGACY_CONTEXT) && + drm_core_check_feature(dev, DRIVER_MODESET)) + return -EINVAL; + if (lock->context == DRM_KERNEL_CONTEXT) { DRM_ERROR("Process %d using kernel context %d\n", task_pid_nr(current), lock->context); diff --git a/drivers/gpu/drm/nouveau/nouveau_drm.c b/drivers/gpu/drm/nouveau/nouveau_drm.c index 8904933..9624b38 100644 --- a/drivers/gpu/drm/nouveau/nouveau_drm.c +++ b/drivers/gpu/drm/nouveau/nouveau_drm.c @@ -941,7 +941,8 @@ static struct drm_driver driver_stub = { .driver_features = DRIVER_USE_AGP | - DRIVER_GEM | DRIVER_MODESET | DRIVER_PRIME | DRIVER_RENDER, + DRIVER_GEM | DRIVER_MODESET | DRIVER_PRIME | DRIVER_RENDER | + DRIVER_KMS_LEGACY_CONTEXT, .load = nouveau_drm_load, .unload = nouveau_drm_unload, diff --git a/include/drm/drmP.h b/include/drm/drmP.h index 9fa6366..654ed7c 100644 --- a/include/drm/drmP.h +++ b/include/drm/drmP.h @@ -137,17 +137,18 @@ void drm_err(const char *format, ...); /*@{*/ /* driver capabilities and requirements mask */ -#define DRIVER_USE_AGP 0x1 -#define DRIVER_PCI_DMA 0x8 -#define DRIVER_SG 0x10 -#define DRIVER_HAVE_DMA 0x20 -#define DRIVER_HAVE_IRQ 0x40 -#define DRIVER_IRQ_SHARED 0x80 -#define DRIVER_GEM 0x1000 -#define DRIVER_MODESET 0x2000 -#define DRIVER_PRIME 0x4000 -#define DRIVER_RENDER 0x8000 -#define DRIVER_ATOMIC 0x10000 +#define DRIVER_USE_AGP 0x1 +#define DRIVER_PCI_DMA 0x8 +#define DRIVER_SG 0x10 +#define DRIVER_HAVE_DMA 0x20 +#define DRIVER_HAVE_IRQ 0x40 +#define DRIVER_IRQ_SHARED 0x80 +#define DRIVER_GEM 0x1000 +#define DRIVER_MODESET 0x2000 +#define DRIVER_PRIME 0x4000 +#define DRIVER_RENDER 0x8000 +#define DRIVER_ATOMIC 0x10000 +#define DRIVER_KMS_LEGACY_CONTEXT 0x20000 /***********************************************************************/ /** \name Macros to make printk easier */ -- 1.9.1

2 1

[Bug 90728] dvd playback with vlc and vdpau causes segmentation fault
by bugzilla-daemon＠freedesktop.org 15 Jun '15

15 Jun '15

https://bugs.freedesktop.org/show_bug.cgi?id=90728 --- Comment #18 from Michel Dänzer <michel(a)daenzer.net> --- (In reply to mehmet.giritli from comment #17) > So, you mean if I can start X without gnome at all and then try running vlc > with basic X server, right? Will try... That's another possibility, but I meant that you can run your GNOME session with the same Mesa version as before. > > > Jun 13 13:43:54 frodo gnome-session[814]: gnome-shell: > > > /tmp/portage/media-libs/mesa-9999/work/mesa-9999/src/gallium/drivers/r600/ > > > r600_pipe.h:902: r600_conv_prim_to_gs_out: Assertion `mode < > > > (sizeof(prim_conv)/sizeof((prim_conv)[0]))' failed. > > > > Can you get a backtrace for this with gdb? > > Sure, but you have to tell me how. I can get backtrace for apps like vlc > from the terminal but for which app shall I get this bt? gnome-shell? Yes. Probably best if you can run gnome-shell from gdb from a remote shell. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 90728] dvd playback with vlc and vdpau causes segmentation fault
by bugzilla-daemon＠freedesktop.org 15 Jun '15

15 Jun '15

https://bugs.freedesktop.org/show_bug.cgi?id=90728 --- Comment #17 from mehmet.giritli(a)gmail.com --- (In reply to Michel Dänzer from comment #16) > (In reply to mehmet.giritli from comment #15) > > Christian, I've been trying in whatever free time I have to run mesa git on > > my laptop but my gnome shell does not seem to be working with it. > > Note that you technically don't need to run anything but vlc with Mesa Git. > You can point libvdpau to the Mesa Git build of libvdpau_r600.so via the > environment variable VDPAU_DRIVER_PATH. So, you mean if I can start X without gnome at all and then try running vlc with basic X server, right? Will try... > > > > Jun 13 13:43:54 frodo gnome-session[814]: gnome-shell: > > /tmp/portage/media-libs/mesa-9999/work/mesa-9999/src/gallium/drivers/r600/ > > r600_pipe.h:902: r600_conv_prim_to_gs_out: Assertion `mode < > > (sizeof(prim_conv)/sizeof((prim_conv)[0]))' failed. > > Can you get a backtrace for this with gdb? Sure, but you have to tell me how. I can get backtrace for apps like vlc from the terminal but for which app shall I get this bt? gnome-shell? Even then I am pretty clueless how to do it...Sorry...But if you give me some tips I'll do my best.. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[PATCH] drm/cma: Fix 64-bit size_t build warnings
by Geert Uytterhoeven 15 Jun '15

15 Jun '15

From: Magnus Damm <damm+renesas(a)opensource.se> Fix warnings related to size_t when building for 64-bit architectures: drivers/gpu/drm/drm_gem_cma_helper.c: In function ‘drm_gem_cma_create’: drivers/gpu/drm/drm_gem_cma_helper.c:114:4: warning: format ‘%d’ expects argument of type ‘int’, but argument 3 has type ‘size_t’ [-Wformat=] size); ^ drivers/gpu/drm/drm_gem_cma_helper.c: In function ‘drm_gem_cma_describe’: drivers/gpu/drm/drm_gem_cma_helper.c:393:4: warning: format ‘%d’ expects argument of type ‘int’, but argument 8 has type ‘size_t’ [-Wformat=] off, &cma_obj->paddr, cma_obj->vaddr, obj->size); Signed-off-by: Magnus Damm <damm+renesas(a)opensource.se> Signed-off-by: Geert Uytterhoeven <geert+renesas(a)glider.be> --- drivers/gpu/drm/drm_gem_cma_helper.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/gpu/drm/drm_gem_cma_helper.c b/drivers/gpu/drm/drm_gem_cma_helper.c index e419eedf751de6cb..bd75f303da63d9c6 100644 --- a/drivers/gpu/drm/drm_gem_cma_helper.c +++ b/drivers/gpu/drm/drm_gem_cma_helper.c @@ -110,7 +110,7 @@ struct drm_gem_cma_object *drm_gem_cma_create(struct drm_device *drm, cma_obj->vaddr = dma_alloc_writecombine(drm->dev, size, &cma_obj->paddr, GFP_KERNEL | __GFP_NOWARN); if (!cma_obj->vaddr) { - dev_err(drm->dev, "failed to allocate buffer with size %d\n", + dev_err(drm->dev, "failed to allocate buffer with size %zu\n", size); ret = -ENOMEM; goto error; @@ -388,7 +388,7 @@ void drm_gem_cma_describe(struct drm_gem_cma_object *cma_obj, off = drm_vma_node_start(&obj->vma_node); - seq_printf(m, "%2d (%2d) %08llx %pad %p %d", + seq_printf(m, "%2d (%2d) %08llx %pad %p %zu", obj->name, obj->refcount.refcount.counter, off, &cma_obj->paddr, cma_obj->vaddr, obj->size); -- 1.9.1

3 2

[PATCH v3] ARM: dts: fix the clock-frequency of rinato board's panel
by Hyungwon Hwang 15 Jun '15

15 Jun '15

From: Hyungwon Hwang <human.hwang(a)samsung.com> After the commit abc0b1447d4974963548777a5ba4a4457c82c426 ("drm: Perform basic sanity checks on probed modes"), proper clock-frequency becomes mandatory for validating the mode of panel. The display does not work if there is no mode validated. Also, this clock-frequency must be set appropriately for getting required frame rate. Fixes: abc0b1447d49 ("drm: Perform basic sanity checks on probed modes") Cc: <stable(a)vger.kernel.org> Signed-off-by: Hyungwon Hwang <human.hwang(a)samsung.com> --- arch/arm/boot/dts/exynos3250-rinato.dts | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/arm/boot/dts/exynos3250-rinato.dts b/arch/arm/boot/dts/exynos3250-rinato.dts index 0b99068..75aba40 100644 --- a/arch/arm/boot/dts/exynos3250-rinato.dts +++ b/arch/arm/boot/dts/exynos3250-rinato.dts @@ -181,7 +181,7 @@ display-timings { timing-0 { - clock-frequency = <0>; + clock-frequency = <4600000>; hactive = <320>; vactive = <320>; hfront-porch = <1>; -- 1.8.1.2

2 1

[Bug 90728] dvd playback with vlc and vdpau causes segmentation fault
by bugzilla-daemon＠freedesktop.org 15 Jun '15

15 Jun '15

https://bugs.freedesktop.org/show_bug.cgi?id=90728 --- Comment #16 from Michel Dänzer <michel(a)daenzer.net> --- (In reply to mehmet.giritli from comment #15) > Christian, I've been trying in whatever free time I have to run mesa git on > my laptop but my gnome shell does not seem to be working with it. Note that you technically don't need to run anything but vlc with Mesa Git. You can point libvdpau to the Mesa Git build of libvdpau_r600.so via the environment variable VDPAU_DRIVER_PATH. > Jun 13 13:43:54 frodo gnome-session[814]: gnome-shell: > /tmp/portage/media-libs/mesa-9999/work/mesa-9999/src/gallium/drivers/r600/ > r600_pipe.h:902: r600_conv_prim_to_gs_out: Assertion `mode < > (sizeof(prim_conv)/sizeof((prim_conv)[0]))' failed. Can you get a backtrace for this with gdb? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 98751] New: radeon: multihead "no signal" on one of the monitors - regression
by bugzilla-daemon＠bugzilla.kernel.org 14 Jun '15

14 Jun '15

https://bugzilla.kernel.org/show_bug.cgi?id=98751 Bug ID: 98751 Summary: radeon: multihead "no signal" on one of the monitors - regression Product: Drivers Version: 2.5 Kernel Version: 4.0.3+ Hardware: All OS: Linux Tree: Mainline Status: NEW Severity: high Priority: P1 Component: Video(DRI - non Intel) Assignee: drivers_video-dri(a)kernel-bugs.osdl.org Reporter: mikkeloscar(a)gmail.com Regression: No Since this commit: https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit… one of my two monitors doesn't get a signal (it just says "no signal"). The monitors are connected to a Radeon HD 6990 card. One is connected through HDMI and one through DVI. I'm using the radeon driver. Most of the time it is the monitor connected through HDMI which doesn't get a signal, but I was able to switch it around somehow by messing around with screen orientation in X (not quite sure how to replicate or if it's even relevant). I tried to revert the commit in kernel 4.0.4 (latest I tried) and that solves the problem for me. -- You are receiving this mail because: You are watching the assignee of the bug.

1 22

[Bug 90728] dvd playback with vlc and vdpau causes segmentation fault
by bugzilla-daemon＠freedesktop.org 13 Jun '15

13 Jun '15

https://bugs.freedesktop.org/show_bug.cgi?id=90728 --- Comment #15 from mehmet.giritli(a)gmail.com --- (In reply to Christian König from comment #14) > (In reply to mehmet.giritli from comment #13) > > Hey Christian, thank you for the patch but it wont compile with a missing > > header util/list.h, here is the output from compilation barking about it: > > > > FYI: I'm trying this on mesa 10.4.6 source > > Development patches like that one are usually against the master branch, > please use this one for testing. > > In general if you have a specific (and easy to reproduce) bug it's usually a > good idea to test master first if the bug isn't already fixed there. > > Regards, > Christian. Christian, I've been trying in whatever free time I have to run mesa git on my laptop but my gnome shell does not seem to be working with it. I dont see anything weird in the logs except: Jun 13 13:43:54 frodo gnome-session[814]: gnome-shell: /tmp/portage/media-libs/mesa-9999/work/mesa-9999/src/gallium/drivers/r600/r600_pipe.h:902: r600_conv_prim_to_gs_out: Assertion `mode < (sizeof(prim_conv)/sizeof((prim_conv)[0]))' failed. Does this mean anything to you? As a result I have not been able to get a desktop on mesa-git running. I also tried updating to xorg-server git thinking may be it is a compatibility issue between the two but there was no difference whatsoever. If you can give me some tips as to what the problem might be, I'd like to get it running and then continue the patch testing... By the way, I'm on gentoo and using the live ebuilds from x11 overlay if you happen to use gentoo...They compile fine by the way.. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[PATCH v2] ARM: dts: fix the clock-frequency of rinato board's panel
by Hyungwon Hwang 13 Jun '15

13 Jun '15

After the commit abc0b1447d4974963548777a5ba4a4457c82c426 ("drm: Perform basic sanity checks on probed modes"), proper clock-frequency becomes mandatory for validating the mode of panel. The display does not work if there is no mode validated. Also, this clock-frequency must be set appropriately for getting required frame rate. Signed-off-by: Hyungwon Hwang <human.hwang(a)samsung.com> --- arch/arm/boot/dts/exynos3250-rinato.dts | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/arm/boot/dts/exynos3250-rinato.dts b/arch/arm/boot/dts/exynos3250-rinato.dts index 0b99068..75aba40 100644 --- a/arch/arm/boot/dts/exynos3250-rinato.dts +++ b/arch/arm/boot/dts/exynos3250-rinato.dts @@ -181,7 +181,7 @@ display-timings { timing-0 { - clock-frequency = <0>; + clock-frequency = <4600000>; hactive = <320>; vactive = <320>; hfront-porch = <1>; -- 1.9.1

3 2

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel June 2015