[Bug 78009] ETQW and TF2 creenshots have alpha=0

art -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20140427/53e04288/attachment.html>

[Bug 78009] New: ETQW and TF2 creenshots have alpha=0

the installed libs? -- 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/20140427/3e6447ba/attachment.html>

[Bug 76564] [AMD Fusion E-350] HDMI refresh rates doesn't match expectations

eiving 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/20140427/4f9fa2b0/attachment.html>

[Bug 74871] ATI radeon support in the kernel (Shutdown problem with ASUS X5DAB (Mobility Radeon HD4570))

https://bugzilla.kernel.org/show_bug.cgi?id=74871 --- Comment #4 from stephanmunsch at web.de --- I assume this is a regression, because I have used this computer already for a longer time without problems. If the given logfiles don't help, I'll try to learn about bisect and help to find out the

[Bug 74871] ATI radeon support in the kernel (Shutdown problem with ASUS X5DAB (Mobility Radeon HD4570))

https://bugzilla.kernel.org/show_bug.cgi?id=74871 --- Comment #3 from stephanmunsch at web.de --- Created attachment 133901 --> https://bugzilla.kernel.org/attachment.cgi?id=133901=edit Xorg logfile -- You are receiving this mail because: You are watching the assignee of the bug.

[Bug 74871] ATI radeon support in the kernel (Shutdown problem with ASUS X5DAB (Mobility Radeon HD4570))

https://bugzilla.kernel.org/show_bug.cgi?id=74871 --- Comment #2 from stephanmunsch at web.de --- Created attachment 133891 --> https://bugzilla.kernel.org/attachment.cgi?id=133891=edit dmesg output -- You are receiving this mail because: You are watching the assignee of the bug.

[Bug 76564] [AMD Fusion E-350] HDMI refresh rates doesn't match expectations

dri-devel/attachments/20140427/cc119c97/attachment-0001.html>

radeon: screen garbled after page allocator change, was: Re: [patch v2 3/3] mm: page_alloc: fair zone allocator policy

On Sat, Apr 26, 2014 at 11:31:11PM -0400, Jerome Glisse wrote: > On Thu, Apr 24, 2014 at 09:37:22AM -0400, Johannes Weiner wrote: > > Hi Thomas, > > > > On Wed, Apr 02, 2014 at 04:26:08PM +0200, Thomas Schwinge wrote: > > > Hi! > > > > > > On Fri, 2 Aug 2013 11:37:26 -0400, Johannes Weiner > >

[Bug 76564] [AMD Fusion E-350] HDMI refresh rates doesn't match expectations

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

[Bug 74911] New: [R9 270X] - Frozen display output and no response from keyboard right after loading kernel image and initramfs

https://bugzilla.kernel.org/show_bug.cgi?id=74911 Bug ID: 74911 Summary: [R9 270X] - Frozen display output and no response from keyboard right after loading kernel image and initramfs Product: Drivers Version:

[Bug 76564] [AMD Fusion E-350] HDMI refresh rates doesn't match expectations

-- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20140427/b272380e/attachment.html>

[Bug 76564] [AMD Fusion E-350] HDMI refresh rates doesn't match expectations

This bug report has made a huge difference for my systems. Garrett -- 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/20140427/d183f263/attachment.html>

[PATCH V2 7/9] drm/bridge: ptn3460: add drm_panel controls

On Fri, Apr 25, 2014 at 8:17 AM, Ajay kumar wrote: > We can call panel_enable/disable at the right point. Even the bridge chips > expect the same. So, I am not ok with combining the bridge and panel and > calling the fxn pointers from crtc_helpers. > So, either we leave it the way it is in this

[RFC PATCH 0/8] component helper improvements

On Sun, Apr 27, 2014 at 1:00 AM, Russell King - ARM Linux wrote: > A while back, Laurent raised some comments about the component helper, > which this patch set starts to address. > > The first point it addresses is the repeated parsing inefficiency when > deferred probing occurs. When DT is

[Bug 76564] [AMD Fusion E-350] HDMI refresh rates doesn't match expectations

-- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20140427/b9730aaf/attachment.html>

[RFC PATCH 0/8] component helper improvements

On Sun, Apr 27, 2014 at 02:51:30PM +0200, Daniel Vetter wrote: > On Sun, Apr 27, 2014 at 1:00 AM, Russell King - ARM Linux > wrote: > > A while back, Laurent raised some comments about the component helper, > > which this patch set starts to address. > > > > The first point it addresses is the

[Bug 76564] [AMD Fusion E-350] HDMI refresh rates doesn't match expectations

as usual. -- 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/20140427/056594de/attachment.html>

[Bug 76564] [AMD Fusion E-350] HDMI refresh rates doesn't match expectations

irq to avoid problems with missed flips. -- 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/20140427/c9474080/attachment.html>

[PATCH RFC 4/8] drm: msm: update to use component match support

On Sat, Apr 26, 2014 at 7:02 PM, Russell King wrote: > Update MSM's DRM driver to use the component match support rather than > add_components. Looks like the component helper improvements make things nicer for the driver. Let me know when you are ready to merge

[Bug 75649] Glitchy output using only HDMI on laptop with AMD Mobility Radeon HD 3450/3470

modes. -- 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/20140427/5348922a/attachment.html>

[RFC v2 PATCH 08/14] drm/exynos: dsi: add driver data to support Exynos5420

Hi Andrzej, On 04/24/2014 10:23 AM, YoungJun Cho wrote: > Hi Andrzej, > > Thank you for comments. > > On 04/23/2014 05:29 PM, Andrzej Hajda wrote: >> On 04/21/2014 02:28 PM, YoungJun Cho wrote: >>> The offset of register DSIM_PLLTMR_REG in Exynos5420 is different >>> from the one in Exynos4 SoC.

[RFC v3 PATCH 16/16] ARM: dts: exynos5420: add dsi node

This patch adds common part of dsi node. Changelog v2: - Uses clock macros instead of numbers (commented by Sachin Kamat) Signed-off-by: YoungJun Cho Acked-by: Inki Dae Acked-by: Kyungmin Park --- arch/arm/boot/dts/exynos5420.dtsi | 15 +++ 1 file changed, 15 insertions(+)

[RFC v3 PATCH 15/16] ARM: dts: exynos5420: add mipi-phy node

This patch adds mipi-phy node for MIPI-DSI device. Signed-off-by: YoungJun Cho Acked-by: Inki Dae Acked-by: Kyungmin Park --- arch/arm/boot/dts/exynos5420.dtsi |6 ++ 1 file changed, 6 insertions(+) diff --git a/arch/arm/boot/dts/exynos5420.dtsi b/arch/arm/boot/dts/exynos5420.dtsi

[RFC v3 PATCH 14/16] ARM: dts: exynos5: add system register support

This patch adds sysreg device node, and sysreg property to fimd device node which is required to use I80 interface. Signed-off-by: YoungJun Cho Acked-by: Inki Dae Acked-by: Kyungmin Park --- arch/arm/boot/dts/exynos5.dtsi |6 ++ 1 file changed, 6 insertions(+) diff --git

[RFC v3 PATCH 13/16] ARM: dts: exynos4: add system register node

This patch adds sysreg property to fimd device node which is required to use I80 interface. Signed-off-by: YoungJun Cho Acked-by: Inki Dae Acked-by: Kyungmin Park --- arch/arm/boot/dts/exynos4.dtsi |1 + 1 file changed, 1 insertion(+) diff --git a/arch/arm/boot/dts/exynos4.dtsi

[RFC v3 PATCH v4 12/16] drm/panel: add S6E3FA0 driver

This patch adds MIPI-DSI command mode based S6E3FA0 AMOLED LCD Panel driver. Changelog v2: - Declares delay, size properties in probe routine instead of DT Changelog v3: - Moves CPU timings relevant properties from FIMD DT (commented by Laurent Pinchart, Andrzej Hajda) Changelog v4: - Enhances

[RFC v3 PATCH v6 11/16] ARM: dts: s6e3fa0: add DT bindings

This patch adds DT bindings for s6e3fa0 panel. The bindings describes panel resources, display timings and cpu mode timings. Changelog v2: - Adds unit address (commented by Sachin Kamat) Changelog v3: - Removes optional delay, size properties (commented by Laurent Pinchart) - Adds OLED detection,

[RFC v3 PATCH v2 10/16] drm/exynos: dsi: add driver data to support Exynos5420

The offset of register DSIM_PLLTMR_REG in Exynos5420 is different from the one in Exynos4 SoC. In case of Exynos5420 SoC, there is no frequency band bit in DSIM_PLLCTRL_REG, and it uses DSIM_PHYCTRL_REG and DSIM_PHYTIMING*_REG instead. So this patch adds driver data to distinguish it. Changelog

[RFC v3 PATCH v2 09/16] ARM: dts: exynos_dsim: add exynos5420 compatible to DT bindings

This patch adds relevant to exynos5420 compatible for exynos5420 SoC support. Changelog v2: - Changes title, description and fixes typo (commented by Sachin Kamat) Signed-off-by: YoungJun Cho Acked-by: Inki Dae Acked-by: Kyungmin Park --- .../devicetree/bindings/video/exynos_dsim.txt |

[RFC v3 PATCH 08/16] drm/exynos: fimd: support I80 interface

To support MIPI DSI command mode interface, FIMD should do followings: - Sets LCD block configuration for I80 interface. - Uses "lcd_sys" as an IRQ resource and sets relevant IRQ configuration. - Implements trigger feature which transfers image date if there is page flip request, and implements

[RFC v3 PATCH 07/16] drm/exynos: dsi: add TE handler to support command mode interface

To support command mode interface, the DSI host calls this handler to notify the panel tearing effect synchronization signal to the CRTC device manager to trigger to transfer video image. Signed-off-by: YoungJun Cho Acked-by: Inki Dae Acked-by: Kyungmin Park ---

[RFC v3 PATCH 06/16] drm/exynos: add TE handler to support MIPI DSI command mode interface

To support MIPI DSI command mode interface, the panel should generates Tearing Effect synchronization signal between MCU and FB to display video images. And the display controller should trigger to transfer video image at this signal. So the panel receives the TE IRQ, then calls this handler

[RFC v3 PATCH 05/16] drm/panel: add CPU mode timings structure

To support MIPI DSI command mode interface, the display controller requires the CPU mode timings which is the panel specific data. Signed-off-by: YoungJun Cho Acked-by: Inki Dae Acked-by: Kyungmin Park --- include/drm/drm_panel.h | 18 ++ 1 file changed, 18 insertions(+)

[RFC v3 PATCH v3 04/16] ARM: dts: samsung-fimd: add I80 specific properties

In case of using CPU interface panel, the relevant registers should be set. So this patch adds relevant dt bindings. Changelog v2: - Changes "samsung,sysreg-phandle" to "samsung,sysreg" Changelog v3: - Moves CPU timings relevant properties to panel DT (commented by Laurent Pinchart, Andrzej

[RFC v3 PATCH v2 03/16] ARM: dts: sysreg: add exynos5 compatible to DT bindings

This patch adds relevant to exynos5 compatible for exynos5 SoCs. Changelog v2: - Changes title and description (commented by Sachin Kamat) Signed-off-by: YoungJun Cho Acked-by: Inki Dae Acked-by: Kyungmin Park --- .../devicetree/bindings/arm/samsung/sysreg.txt |1 + 1 file changed, 1

[RFC v3 PATCH 02/16] drm/exynos: use wait_event_timeout() for safety usage

There could be the case that the page flip operation isn't finished correctly with some abnormal condition such as panel reset. So this patch replaces wait_event() with wait_event_timeout() to avoid waiting for page flip completion infinitely. Signed-off-by: YoungJun Cho Acked-by: Inki Dae

[RFC v3 PATCH 01/16] drm/exynos: dsi: move the Eot packets configuration point

This configuration could be used in MIPI DSI command mode also. Signed-off-by: YoungJun Cho Acked-by: Inki Dae Acked-by: Kyungmin Park --- drivers/gpu/drm/exynos/exynos_drm_dsi.c |5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git

[RFC v3 PATCH 00/16] drm/exynos: support MIPI DSI command mode display

This patch series includes the followings: - FIMD I80 interface - DSI command mode interface for Exynos5420 SoC - S6E3FA0 command mode type panel driver This patch series is based on exynos-drm-next branch. Previous patch set, RFC v1: http://www.spinics.net/lists/dri-devel/msg57513.html RFC v2:

[Bug 71891] 3.13 fails to boot with the radeon module

https://bugzilla.kernel.org/show_bug.cgi?id=71891 --- Comment #27 from sdh --- (In reply to Christian K?nig from comment #25) > Please provide the content of the registers CG_UPLL_FUNC_CNTL, > CG_UPLL_FUNC_CNTL_2 and CG_UPLL_FUNC_CNTL_3. E.g. install radeontool and > execute: > > radeonreg

[Bug 71891] 3.13 fails to boot with the radeon module

https://bugzilla.kernel.org/show_bug.cgi?id=71891 --- Comment #26 from Dieter N?tzel --- 0x718 0x20010002 (536936450) 0x71c 0x021f2111 (35594513) 0x720 0x102774da (271021274) Only for 3.15.0-rc2-1-desktop-lower-clocks. Do you need more? --- Need some sleep, badly! Cheers, Dieter. --

[PATCH RFC 4/8] drm: msm: update to use component match support

Update MSM's DRM driver to use the component match support rather than add_components. Signed-off-by: Russell King --- drivers/gpu/drm/msm/msm_drv.c | 81 ++- 1 file changed, 34 insertions(+), 47 deletions(-) diff --git

[RFC PATCH 0/8] component helper improvements

A while back, Laurent raised some comments about the component helper, which this patch set starts to address. The first point it addresses is the repeated parsing inefficiency when deferred probing occurs. When DT is used, the structure of the component helper today means that masters end up

radeon: screen garbled after page allocator change, was: Re: [patch v2 3/3] mm: page_alloc: fair zone allocator policy

On Thu, Apr 24, 2014 at 09:37:22AM -0400, Johannes Weiner wrote: > Hi Thomas, > > On Wed, Apr 02, 2014 at 04:26:08PM +0200, Thomas Schwinge wrote: > > Hi! > > > > On Fri, 2 Aug 2013 11:37:26 -0400, Johannes Weiner > > wrote: > > > Each zone that holds userspace pages of one workload must be