[Bug 73320] [radeonsi] LLVM runs out of registers during register allocation in Painkiller Hell & Damnation

. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20140509/2dd4332a/attachment.html>

[Bug 73320] [radeonsi] LLVM runs out of registers during register allocation in Painkiller Hell & Damnation

. -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20140509/704a31e7/attachment.html>

[Bug 78453] [HAWAII] Get acceleration working

Option "ColorTiling" "false" Option "ColorTiling2D" "false" -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20140509/f8629a47/attachment.html>

[Bug 75112] Meta Bug for HyperZ issues on r600g and radeonsi

), glmark2 2014.03 (515 points -> 717). Thank you -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20140509/d2c0346b/attachment.html>

[RFC V2 0/3] drm/bridge: panel and chaining

On Fri, May 9, 2014 at 7:29 PM, Rob Clark wrote: > On Fri, May 9, 2014 at 5:08 AM, Andrzej Hajda wrote: >> On 05/08/2014 08:24 PM, Rob Clark wrote: >>> On Thu, May 8, 2014 at 2:41 AM, Andrzej Hajda >>> wrote: On 05/05/2014 09:52 PM, Ajay Kumar wrote: > This patchset is based on

[RFC V3 3/3] drm: create and demonstrate bridge chaining using exynos_dp

use drm_bridge helpers to demonstrate chaining of bridges(ptn3460 and bridge_panel) with exynos_dp encoder. Signed-off-by: Ajay Kumar --- drivers/gpu/drm/bridge/ptn3460.c| 60 +++ drivers/gpu/drm/exynos/exynos_dp_core.c | 25 -

[RFC V3 2/3] drm/bridge: add a dummy panel driver to support lvds bridges

implement basic panel controls as a drm_bridge so that the existing bridges can make use of it. The driver assumes that it is the last entity in the bridge chain. Signed-off-by: Ajay Kumar --- .../bindings/drm/bridge/bridge_panel.txt | 45 drivers/gpu/drm/bridge/Kconfig

[RFC V3 1/3] drm/bridge: add helper functions to support bridge chain

Add helper functions to create bridge chain and to call the corresponding next_bridge functions. Signed-off-by: Ajay Kumar Suggested-by: Rob Clark --- include/drm/drm_crtc.h | 72 1 file changed, 72 insertions(+) diff --git

[RFC V3 0/3] drm/bridge: panel and chaining

This patchset is based on exynos-drm-next-todo branch of Inki Dae's tree at: git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos.git Inital discussion can be found at: http://www.mail-archive.com/linux-samsung-soc at vger.kernel.org/msg30008.html As Rob suggested, I have added few

CIK hangs with kernel 3.15, bisected

On 9 May 2014 20:03, Marek Ol??k wrote: > This commit which first appeared in 3.15-rc1 causes hangs on Bonaire: > > commit 6d2f2944e95e504a7d33385eeeb9bb7fcca72592 > Author: Christian K?nig > Date: Thu Feb 20 13:42:17 2014 +0100 > > drm/radeon: use normal BOs for the page tables v4 Also

CIK hangs with kernel 3.15, bisected

Hi Christian, This commit which first appeared in 3.15-rc1 causes hangs on Bonaire: commit 6d2f2944e95e504a7d33385eeeb9bb7fcca72592 Author: Christian K?nig Date: Thu Feb 20 13:42:17 2014 +0100 drm/radeon: use normal BOs for the page tables v4 No need to make it more complicated than

[PATCH] drm/exynos: hdmi: remove unnecessary dedicated i2c drivers

The i2c drivers for ddc and hdmiphy are already removed from build and instead, i2c clients registered via devicetree are used. So this patch removes the unnecessary i2c drivers. Signed-off-by: Seung-Woo Kim --- drivers/gpu/drm/exynos/exynos_ddc.c | 63 --

[Bug 66281] DRI_PRIME=1 glxinfo crashes and causes session to restart

https://bugzilla.kernel.org/show_bug.cgi?id=66281 Ilia Mirkin changed: What|Removed |Added CC||imirkin at alum.mit.edu --- Comment #5

[PATCH] drm/exynos: hdmi: consider legacy dt binding

This patch considers legacy dt binding, and resolves the issue that the use of existing dtb is broken. To resove the dt broken issue, this path tries to get legacy dt nodes from existing dtb directly prior to getting new dt nodes. Signed-off-by: Inki Dae Acked-by: Kyungmin Park ---

[PATCH 2/2] drm/exynos: Fix double locks at PM resume

Hi, On 2014? 05? 09? 15:14, Takashi Iwai wrote: > The recent commit [3ea87855: drm/helper: lock all around force mode > restore] introduced drm_modeset_lock_all() in > drm_helper_resume_force_mode() itself, while exynos driver takes this > lock before calling it. Move the function call outside

[Bug 66281] DRI_PRIME=1 glxinfo crashes and causes session to restart

https://bugzilla.kernel.org/show_bug.cgi?id=66281 --- Comment #4 from Gaurav Shukla --- (In reply to Ilia Mirkin from comment #3) > Make sure that > > (a) You're using a kernel 3.14 or higher (3.13 introduced modesetting but > not the firmware required for acceleration for the gk208) > (b)

[Bug 66281] DRI_PRIME=1 glxinfo crashes and causes session to restart

https://bugzilla.kernel.org/show_bug.cgi?id=66281 --- Comment #3 from Ilia Mirkin --- Make sure that (a) You're using a kernel 3.14 or higher (3.13 introduced modesetting but not the firmware required for acceleration for the gk208) (b) You're not using bumblebee (3.12 introduced runtime pm

[Bug 66281] DRI_PRIME=1 glxinfo crashes and causes session to restart

https://bugzilla.kernel.org/show_bug.cgi?id=66281 Gaurav Shukla changed: What|Removed |Added CC||areyaargaurav at gmail.com --- Comment

[Bug 77677] HDMI audio on ati7750 choppy with ALSA multi-channel apps

are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20140509/18b17f1e/attachment-0001.html>

[PATCH] drm/gk20a/fb: fix NULL dereference

gk20a_ram_put() can be called with a NULL nouveau_mem in case of error. Handle that case the way is it done in other RAM drivers. Signed-off-by: Alexandre Courbot --- drivers/gpu/drm/nouveau/core/subdev/fb/ramgk20a.c | 2 ++ 1 file changed, 2 insertions(+) diff --git

[RFC PATCH 2/2] drm/panel: update simple-panel DT bindings doc with panel desc properties

Document simple-panel description properties and subnodes. The display-timings definition is the one described in Documentation/devicetree/bindings/video/display-timing.txt. Signed-off-by: Boris BREZILLON --- .../devicetree/bindings/panel/simple-panel.txt | 34 ++ 1

[RFC PATCH 1/2] drm/panel: add support for simple-panel description definition using DT

Currently, the only way to add new panel descriptions to the simple panel driver is to add new entries in the platform_of_match table. Add support for panel description retrieval from the DT. Signed-off-by: Boris BREZILLON --- drivers/gpu/drm/panel/Kconfig| 1 +

[RFC PATCH 0/2] drm/panel: add simple-panel description using DT

Hello Thierry, I noticed you're describing each new panel with a new entry in the of_platform_match table and a new compatible string. I guess you have a good reason to do it this way, because retrieving panel description from DT would be pretty easy (see this series ;-)). Could tell me why you

[Bug 75401] vgaswitcheroo doesn't work for AMD Radeon 8870m (possibly due to "wrong" PCI class)

https://bugzilla.kernel.org/show_bug.cgi?id=75401 --- Comment #11 from Alex Deucher --- Looks like it works fine without the patch as well. That said, the ATRM patch shouldn't hurt anything if there ever ends up being a case where the ATRM method is hung off a non-VGA display device. -- You

OMAPDSS: omap5 SYNC_LOST error with DPI/LCD

Hi, On Friday 09 May 2014 02:07 PM, Patil, Vikash wrote: > Hi Archit, > > With CONFIG_OMAP2_DSS_MIN_FCK_PER_PCK to 4, mode becomes invalid and can't > launch kmscube. > > [0.847015] [drm:omap_connector_mode_valid], connector: mode invalid: > 14:"1280x480" 60 40500 1280 1350 1365 1366 480

[Bug 75401] vgaswitcheroo doesn't work for AMD Radeon 8870m (possibly due to "wrong" PCI class)

https://bugzilla.kernel.org/show_bug.cgi?id=75401 --- Comment #10 from drill87 at gmail.com --- Created attachment 135561 --> https://bugzilla.kernel.org/attachment.cgi?id=135561=edit dmesg before applying "fix for rom fetching" patch -- You are receiving this mail because: You are watching

[Bug 75401] vgaswitcheroo doesn't work for AMD Radeon 8870m (possibly due to "wrong" PCI class)

https://bugzilla.kernel.org/show_bug.cgi?id=75401 --- Comment #9 from drill87 at gmail.com --- Oh, I'm sorry, it seems I didn't write it clear enough. I mentioned file "radeon_bios.c" only because I saw there too goes PCI class checl only against PCI_CLASS_DISPLAY_VGA, but there wasn't additional

[PATCH 01/12] drm: Move DRM_ROTATE bits out of omapdrm into drm_crtc.h

From: Ville Syrj?l? The rotation property stuff should be standardized among all drivers. Move the bits to drm_crtc.h from omap_drv.h. Cc: David Airlie Cc: Tomi Valkeinen Cc: Dave Airlie Cc: Rob Clark Cc: Daniel Vetter Cc: Archit Taneja Cc: dri-devel at

OMAPDSS: omap5 SYNC_LOST error with DPI/LCD

o set the value of CONFIG_OMAP2_DSS_MIN_FCK_PER_PCK to 4, > and tell what happens? The correct solution would be to figure out why > it isn't using the DSI PLL, but we could start with changing the config > above. > > Archit > > __

[Bug 75401] vgaswitcheroo doesn't work for AMD Radeon 8870m (possibly due to "wrong" PCI class)

https://bugzilla.kernel.org/show_bug.cgi?id=75401 --- Comment #8 from Alex Deucher --- ATRM is an acpi method for fetching the rom on certain systems. If your system was able to fetch the rom via another method, it may not use ATRM. I'm not sure if the ATRM method is required in drill87's case

[Bug 75401] vgaswitcheroo doesn't work for AMD Radeon 8870m (possibly due to "wrong" PCI class)

https://bugzilla.kernel.org/show_bug.cgi?id=75401 Pali Roh?r changed: What|Removed |Added CC||pali.rohar at gmail.com --- Comment #7 from

OMAPDSS: omap5 SYNC_LOST error with DPI/LCD

Hi Vikas, On Friday 09 May 2014 11:54 AM, Vikas Patil wrote: > Hi, > > Forgot to mention, DPI pins are connected to TDF19988 chip for HDMI > conversion. > I have build the driver for it from >

[RFC V2 0/3] drm/bridge: panel and chaining

On 05/08/2014 08:24 PM, Rob Clark wrote: > On Thu, May 8, 2014 at 2:41 AM, Andrzej Hajda wrote: >> On 05/05/2014 09:52 PM, Ajay Kumar wrote: >>> This patchset is based on exynos-drm-next-todo branch of Inki Dae's tree at: >>> git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos.git

OMAPDSS: omap5 SYNC_LOST error with DPI/LCD

Hi Archit, With CONFIG_OMAP2_DSS_MIN_FCK_PER_PCK to 4, mode becomes invalid and can't launch kmscube. [0.847015] [drm:omap_connector_mode_valid], connector: mode invalid: 14:"1280x480" 60 40500 1280 1350 1365 1366 480 491 492 494 0x48 0x0 [0.847045] [drm:drm_mode_debug_printmodeline],

[RFC V2 0/3] drm/bridge: panel and chaining

On Fri, May 9, 2014 at 5:08 AM, Andrzej Hajda wrote: > On 05/08/2014 08:24 PM, Rob Clark wrote: >> On Thu, May 8, 2014 at 2:41 AM, Andrzej Hajda wrote: >>> On 05/05/2014 09:52 PM, Ajay Kumar wrote: This patchset is based on exynos-drm-next-todo branch of Inki Dae's tree at:

[PATCH V2 1/9] drm/exynos: dp: support hotplug detection via GPIO

On Tuesday, April 22, 2014 4:14 PM, Jingoo Han wrote: > On Tuesday, April 22, 2014 7:39 AM, Ajay Kumar wrote: > > > > From: Andrew Bresticker > > > > Certain bridge chips use a GPIO to indicate the cable status instead > > of the I_DP_HPD pin. This adds an optional device-tree property, > >

[PATCH 2/2] drm/exynos: Fix double locks at PM resume

The recent commit [3ea87855: drm/helper: lock all around force mode restore] introduced drm_modeset_lock_all() in drm_helper_resume_force_mode() itself, while exynos driver takes this lock before calling it. Move the function call outside the lock for avoiding a deadlock. Signed-off-by: Takashi

[PATCH 1/2] drm/ast: Fix double lock at PM resume

The recent commit [3ea87855: drm/helper: lock all around force mode restore] introduced drm_modeset_lock_all() in drm_helper_resume_force_mode() itself, while ast driver still takes this lock before calling it. Remove the caller side lock for avoid a fatal deadlock. Signed-off-by: Takashi Iwai

[Bug 75401] vgaswitcheroo doesn't work for AMD Radeon 8870m (possibly due to "wrong" PCI class)

https://bugzilla.kernel.org/show_bug.cgi?id=75401 --- Comment #6 from drill87 at gmail.com --- Created attachment 135541 --> https://bugzilla.kernel.org/attachment.cgi?id=135541=edit dmesg after applying "fix for rom fetching" patch -- You are receiving this mail because: You are watching the

[Bug 75401] vgaswitcheroo doesn't work for AMD Radeon 8870m (possibly due to "wrong" PCI class)

https://bugzilla.kernel.org/show_bug.cgi?id=75401 --- Comment #5 from drill87 at gmail.com --- I guess it fixes. At least, I can see no errors for radeon module in dmesg. Vgaswitcheroo, as I aforementioned, works too (I can turn off the card, so notebook heats less). However, I cannot say any

[Bug 78453] [HAWAII] Get acceleration working

#6. The hardware doesn't support linear depth/stencil buffers. -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20140509/30

[Bug 76919] Random junk at the bottom of non-multiple-of-4 compressed textures (original or mipmapped)

. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20140509/7ef28de0/attachment.html>