[PATCH V4] drm/exynos: fimd: calculate the correct address offset

Calculate the correct address offset values for alpha and color key control registers based on exynos4 and exynos5 user manuals. Also remove VIDOSD_C_SIZE_W0 macro and fix comments about registers for size and alpha. Signed-off-by: Leela Krishna Amudala Acked-by: Joonyoung Shim ---

[git pull] drm fixes

Hi Linus, misc radeon, nouveau, mgag200 and intel fixes, the intel fixes should contain the fix for the touchpad on the Chromebook - hey I'm an input maintainer now! Dave. The following changes since commit 6dbe51c251a327e012439c4772097a13df43c5b8: Linux 3.9-rc1 (2013-03-03 15:11:05

[PATCH 01/14] x86, ACPI, mm: Kill max_low_pfn_mapped

On 03/07/2013 09:28 PM, Tejun Heo wrote: > On Thu, Mar 7, 2013 at 9:27 PM, Yinghai Lu wrote: >> They are not using memblock_find_in_range(), so 1ULL<< will not help. >> >> Really hope i915 drm guys could clean that hacks. > > The code isn't being used. Just leave it alone. Maybe add a comment.

[Bug 58042] [bisected] Garbled UI in Team Fortress 2 and Counter-Strike: Source

dri-devel/attachments/20130307/e0d3a38a/attachment.html>

[PATCH 01/14] x86, ACPI, mm: Kill max_low_pfn_mapped

On Thu, Mar 7, 2013 at 9:27 PM, Yinghai Lu wrote: > They are not using memblock_find_in_range(), so 1ULL<< will not help. > > Really hope i915 drm guys could clean that hacks. The code isn't being used. Just leave it alone. Maybe add a comment. The change is just making things more confusing.

[PATCH 01/14] x86, ACPI, mm: Kill max_low_pfn_mapped

On Thu, Mar 7, 2013 at 9:25 PM, Tejun Heo wrote: > On Thu, Mar 7, 2013 at 9:22 PM, Yinghai Lu wrote: >> On Thu, Mar 7, 2013 at 9:10 PM, Tejun Heo wrote: >>> On Thu, Mar 07, 2013 at 08:58:27PM -0800, Yinghai Lu wrote: diff --git a/drivers/gpu/drm/i915/i915_gem_stolen.c

[PATCH 01/14] x86, ACPI, mm: Kill max_low_pfn_mapped

On Thu, Mar 7, 2013 at 9:22 PM, Yinghai Lu wrote: > On Thu, Mar 7, 2013 at 9:10 PM, Tejun Heo wrote: >> On Thu, Mar 07, 2013 at 08:58:27PM -0800, Yinghai Lu wrote: >>> diff --git a/drivers/gpu/drm/i915/i915_gem_stolen.c >>> b/drivers/gpu/drm/i915/i915_gem_stolen.c >>> index 69d97cb..7f9380b

[PATCH 01/14] x86, ACPI, mm: Kill max_low_pfn_mapped

On Thu, Mar 7, 2013 at 9:10 PM, Tejun Heo wrote: > On Thu, Mar 07, 2013 at 08:58:27PM -0800, Yinghai Lu wrote: >> diff --git a/drivers/gpu/drm/i915/i915_gem_stolen.c >> b/drivers/gpu/drm/i915/i915_gem_stolen.c >> index 69d97cb..7f9380b 100644 >> --- a/drivers/gpu/drm/i915/i915_gem_stolen.c >>

[PATCH 01/14] x86, ACPI, mm: Kill max_low_pfn_mapped

On Thu, Mar 07, 2013 at 08:58:27PM -0800, Yinghai Lu wrote: > diff --git a/drivers/gpu/drm/i915/i915_gem_stolen.c > b/drivers/gpu/drm/i915/i915_gem_stolen.c > index 69d97cb..7f9380b 100644 > --- a/drivers/gpu/drm/i915/i915_gem_stolen.c > +++ b/drivers/gpu/drm/i915/i915_gem_stolen.c > @@ -81,7

[PATCH 01/14] x86, ACPI, mm: Kill max_low_pfn_mapped

Now we have arch_pfn_mapped array, and max_low_pfn_mapped should not be used anymore. Only user is ACPI_OVERRIDE, and it should not use that, as later accessing is using early_remap. Change to try to 4G below and then 4G above. Other user is in drm/i915, but it is commented out. Should use

[Bug 61979] backlight adjustment doesn't work on HP Pavilion m6-1035dx

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

[PATCH] drm: call drm_device_set_unplugged in drm_put_dev

This prevents the device from being reopened after drm_put_dev is called. Signed-off-by: Maarten Lankhorst driver; + drm_device_set_unplugged(dev); + drm_lastclose(dev); if (drm_core_has_MTRR(dev) && drm_core_has_AGP(dev) && @@ -499,11 +501,10 @@ void drm_unplug_dev(struct

[PATCH RFC] drm/exynos: hdmi: move hdmiphy related code to hdmiphy driver

> -Original Message- > From: ??? [mailto:sw0312.kim at samsung.com] > Sent: Thursday, March 07, 2013 4:04 PM > To: Rahul Sharma > Cc: Inki Dae; linux-samsung-soc at vger.kernel.org; Sean Paul; sunil joshi; > dri-devel at lists.freedesktop.org; Rahul Sharma; sw0312.kim at samsung.com >

[PATCH v12 2/2] drm/exynos: enable OF_VIDEOMODE and FB_MODE_HELPERS for exynos drm fimd

> -Original Message- > From: linux-media-owner at vger.kernel.org [mailto:linux-media- > owner at vger.kernel.org] On Behalf Of Vikas Sajjan > Sent: Thursday, March 07, 2013 4:40 PM > To: dri-devel at lists.freedesktop.org > Cc: linux-media at vger.kernel.org; kgene.kim at samsung.com; >

Wrong vsync offset calculation in drm_edid.c

This patch is a bug fix for the file drm_edid.c of the kernel 3.8. The vsync offset is calculated wrong from the EDID set because of the wrong shift direction. We could measure the bad old setting and also the good new setting after the bug fix. Signed-off-by: Peter Blum diff -Naur

[PATCH] drm/exynos: modify the compatible string for exynos fimd

Already merged. :) > -Original Message- > From: Vikas Sajjan [mailto:vikas.sajjan at linaro.org] > Sent: Thursday, March 07, 2013 4:09 PM > To: InKi Dae > Cc: dri-devel at lists.freedesktop.org; linux-media at vger.kernel.org; > kgene.kim at samsung.com; Joonyoung Shim; sunil joshi >

[PATCH RFC] drm/exynos: hdmi: move hdmiphy related code to hdmiphy driver

On 2013? 03? 07? 15:45, Rahul Sharma wrote: > Thanks Seung Woo, Mr. Dae, > > On Thu, Mar 7, 2013 at 10:13 AM, Inki Dae wrote: >> 2013/3/7 ??? : >>> >>> >>> On 2013? 03? 04? 23:05, Rahul Sharma wrote: Thanks Sean, On Wed, Feb 27, 2013 at 9:47 PM, Sean Paul wrote: > On Wed,

[PATCH RFC] drm/exynos: hdmi: move hdmiphy related code to hdmiphy driver

On Thu, Mar 7, 2013 at 12:37 PM, St?phane Marchesin wrote: > On Wed, Mar 6, 2013 at 8:43 PM, Inki Dae wrote: >> 2013/3/7 ??? : >>> >>> >>> On 2013? 03? 04? 23:05, Rahul Sharma wrote: Thanks Sean, On Wed, Feb 27, 2013 at 9:47 PM, Sean Paul wrote: > On Wed, Feb 27, 2013 at 8:22

[PATCH v5 4/9] video: Add generic HDMI infoframe helpers

r and they are already struggling really hard to keep up with > the pace of Linux. So if you don't care too much it would be nice to use > MIT here. Sure, I'll relicense it under MIT then. Thierry -- next part -- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 836 bytes Desc: not available URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20130307/a8dbd324/attachment.pgp>

[PATCH v5 4/9] video: Add generic HDMI infoframe helpers

Am Montag, den 04.03.2013, 16:02 +0100 schrieb Thierry Reding: > On Mon, Mar 04, 2013 at 04:49:46PM +0200, Ville Syrj?l? wrote: > > On Fri, Feb 22, 2013 at 08:03:26AM +0100, Thierry Reding wrote: > [...] > > > diff --git a/drivers/video/hdmi.c b/drivers/video/hdmi.c > > > new file mode 100644 > >

[PATCH RFC] drm/exynos: hdmi: move hdmiphy related code to hdmiphy driver

2013/3/7 ??? : > > > On 2013? 03? 04? 23:05, Rahul Sharma wrote: >> Thanks Sean, >> >> On Wed, Feb 27, 2013 at 9:47 PM, Sean Paul wrote: >>> On Wed, Feb 27, 2013 at 8:22 AM, Rahul Sharma >>> wrote: Right now hdmiphy operations and configs are kept inside hdmi driver. hdmiphy related

[pull] radeon drm-fixes-3.9

From: Alex Deucher Hi Dave, Radeon fixes pull. Not much to it. - fix some splatter if the interrupt handler isn't registered - Add a quirk for an old R200 board to fix washed out colors on the DAC - Don't try and soft reset the MC when we reset the GPU. It

[PATCH v12 2/2] drm/exynos: enable OF_VIDEOMODE and FB_MODE_HELPERS for exynos drm fimd

patch adds "select OF_VIDEOMODE" and "select FB_MODE_HELPERS" when EXYNOS_DRM_FIMD config is selected. Signed-off-by: Vikas Sajjan --- drivers/gpu/drm/exynos/Kconfig |2 ++ 1 file changed, 2 insertions(+) diff --git a/drivers/gpu/drm/exynos/Kconfig b/drivers/gpu/drm/exynos/Kconfig index

[PATCH v12 1/2] video: drm: exynos: Add display-timing node parsing using video helper function

Add support for parsing the display-timing node using video helper function. The DT node parsing is done only if 'dev.of_node' exists and the NON-DT logic is still maintained under the 'else' part. Signed-off-by: Leela Krishna Amudala Signed-off-by: Vikas Sajjan Acked-by: Joonyoung Shim ---

[PATCH v12 0/2] Add display-timing node parsing to exynos drm fimd

Add display-timing node parsing to drm fimd and depends on the display helper patchset at http://lists.freedesktop.org/archives/dri-devel/2013-January/033998.html changes since v11: - Oops, there was a build error, fixed that. changes since v10: - abandoned the pinctrl patch, as

[PATCH] drm/exynos: modify the compatible string for exynos fimd

Thanks. On 7 March 2013 12:47, Inki Dae wrote: > Already merged. :) > >> -Original Message- >> From: Vikas Sajjan [mailto:vikas.sajjan at linaro.org] >> Sent: Thursday, March 07, 2013 4:09 PM >> To: InKi Dae >> Cc: dri-devel at lists.freedesktop.org; linux-media at vger.kernel.org; >>

[PATCH 3/4] drm/omap: Make fixed resolution panels work

On Wednesday 06 March 2013 06:15 AM, Rob Clark wrote: > On Tue, Mar 5, 2013 at 9:17 AM, Archit Taneja wrote: >> The omapdrm driver requires omapdss panel drivers to expose ops like detect, >> set_timings and check_timings. These can be NULL for fixed panel DPI, DBI, >> DSI >> and SDI drivers. At

[PATCH] drm/exynos: modify the compatible string for exynos fimd

Hi Mr Inki Dae, On 28 February 2013 08:12, Joonyoung Shim wrote: > On 02/27/2013 07:32 PM, Vikas Sajjan wrote: >> >> modified compatible string for exynos4 fimd as "exynos4210-fimd" and >> exynos5 fimd as "exynos5250-fimd" to stick to the rule that compatible >> value should be named after first

nouveau lockdep splat

On 03/04/13 22:16, Borislav Petkov wrote: > New -rc1, so let the stabilization games begin. > > I see the following on rc1, let me know if you need more info. > > > [0.633617] = > [0.633618] [ INFO: possible recursive locking detected ] > [

[PATCH v11 2/2] drm/exynos: enable OF_VIDEOMODE and FB_MODE_HELPERS for exynos drm fimd

patch adds "select OF_VIDEOMODE" and "select FB_MODE_HELPERS" when EXYNOS_DRM_FIMD config is selected. Signed-off-by: Vikas Sajjan --- drivers/gpu/drm/exynos/Kconfig |2 ++ 1 file changed, 2 insertions(+) diff --git a/drivers/gpu/drm/exynos/Kconfig b/drivers/gpu/drm/exynos/Kconfig index

[PATCH v11 1/2] video: drm: exynos: Add display-timing node parsing using video helper function

Add support for parsing the display-timing node using video helper function. The DT node parsing is done only if 'dev.of_node' exists and the NON-DT logic is still maintained under the 'else' part. Signed-off-by: Leela Krishna Amudala Signed-off-by: Vikas Sajjan Acked-by: Joonyoung Shim ---

[PATCH v11 0/2] Add display-timing node parsing to exynos drm fimd

Add display-timing node parsing to drm fimd and depends on the display helper patchset at http://lists.freedesktop.org/archives/dri-devel/2013-January/033998.html changes since v10: - abandoned the pinctrl patch, as commented by Linus Walleij - added new patch to enable

[PATCH RFC] drm/exynos: hdmi: move hdmiphy related code to hdmiphy driver

Thanks Seung Woo, Mr. Dae, On Thu, Mar 7, 2013 at 10:13 AM, Inki Dae wrote: > 2013/3/7 ??? : >> >> >> On 2013? 03? 04? 23:05, Rahul Sharma wrote: >>> Thanks Sean, >>> >>> On Wed, Feb 27, 2013 at 9:47 PM, Sean Paul wrote: On Wed, Feb 27, 2013 at 8:22 AM, Rahul Sharma >>> samsung.com> wrote:

[Bug 61965] Kernel panics drm_fb_helper_restore_fbdev_mode when using Chromium

ttp://lists.freedesktop.org/archives/dri-devel/attachments/20130307/7af66445/attachment.html>

[Bug 61965] Kernel panics drm_fb_helper_restore_fbdev_mode when using Chromium

- am I reporting this bug to the right place? -- 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/20130307/0ce11d57/attachment.html>

[Bug 61965] Kernel panics drm_fb_helper_restore_fbdev_mode when using Chromium

vel/attachments/20130307/67d880a6/attachment.html>

[Bug 61965] Kernel panics drm_fb_helper_restore_fbdev_mode when using Chromium

|| -- 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/20130307/21fcc3d6/attachment.html>

[PATCH RFC] drm/exynos: hdmi: move hdmiphy related code to hdmiphy driver

On 2013? 03? 04? 23:05, Rahul Sharma wrote: > Thanks Sean, > > On Wed, Feb 27, 2013 at 9:47 PM, Sean Paul wrote: >> On Wed, Feb 27, 2013 at 8:22 AM, Rahul Sharma >> wrote: >>> Right now hdmiphy operations and configs are kept inside hdmi driver. >>> hdmiphy related >>> code is tightly

[Bug 61965] New: Kernel panics drm_fb_helper_restore_fbdev_mode when using Chromium

bug. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20130307/db38645e/attachment-0001.html>

[PATCH 2/2] drm: Documentation typo fixes

Signed-off-by: Christopher Harvey --- include/drm/drm_crtc.h | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/include/drm/drm_crtc.h b/include/drm/drm_crtc.h index 00d78b5..7294403 100644 --- a/include/drm/drm_crtc.h +++ b/include/drm/drm_crtc.h @@ -429,12 +429,12 @@

[PATCH 1/2] drm/mgag200: Bug fix: Renesas board now selects native resolution.

Renesas boards were consistently defaulting to the 1024x768 resolution, regardless of the native resolution of the monitor plugged in. It was determined that the EDID of the monitor was not being read. Since the DAC is a shared line, in order to read from or write to it we must take control of

[PATCH 0/2] mgag200 fix plus documentation typo fixes

This is a fix for mgag200 cards that is well documented in the commit message. Also includes some typo fixes that were bugging me. Christopher Harvey (1): drm: Documentation typo fixes Julia Lemire (1): drm/mgag200: Bug fix: Renesas board now selects native resolution.

[PATCH] drm/mgag200: Reject modes that are too big for VRAM

On Wed, Feb 27, 2013 at 1:55 AM, Christopher Harvey wrote: > A monitor or a user could request a resolution greater than the > available VRAM for the backing framebuffer. This change checks the > required framebuffer size against the max VRAM size and rejects modes > if they are too big. This

Black screen with nouveau in 3.8.x (regression)

org/archives/dri-devel/attachments/20130307/56055089/attachment.bin>

[Intel-gfx] [PATCH 6/8] drm/i915: Enable/Disable PSR

On Tue, 26 Feb 2013 14:48:33 +0200 Ville Syrj?l? wrote: > On Mon, Feb 25, 2013 at 07:55:20PM -0300, Rodrigo Vivi wrote: > > Adding Enable and Disable PSR functionalities. This includes setting the > > PSR configuration over AUX, sending SDP VSC DIP over the eDP PIPE config, > > enabling PSR in

[PATCH] mgag200: some cleanup and a fix for corrupted output

On Thu, Mar 7, 2013 at 4:51 AM, Christopher Harvey wrote: > On Tue, Feb 26, 2013 at 10:52:55AM -0500, Christopher Harvey wrote: >> Patches 1 to 4 are just cleanup. Maybe these should should be rolled >> into one patch? >> >> Patch 5 is a bit more complicated. >> On cards with very little video

[PATCH V3] drm/exynos: fimd: calculate the correct address offset

Calculate the correct address offset values for alpha and color key control registers based on exynos4 and exynos5 user manuals. Signed-off-by: Leela Krishna Amudala --- drivers/gpu/drm/exynos/exynos_drm_fimd.c | 17 + 1 file changed, 9 insertions(+), 8 deletions(-) diff --git

RE: [PATCH RFC] drm/exynos: hdmi: move hdmiphy related code to hdmiphy driver

-Original Message- From: 김승우 [mailto:sw0312@samsung.com] Sent: Thursday, March 07, 2013 4:04 PM To: Rahul Sharma Cc: Inki Dae; linux-samsung-...@vger.kernel.org; Sean Paul; sunil joshi; dri-devel@lists.freedesktop.org; Rahul Sharma; sw0312@samsung.com Subject: Re: [PATCH

Re: [PATCH RFC] drm/exynos: hdmi: move hdmiphy related code to hdmiphy driver

On Thu, Mar 7, 2013 at 12:37 PM, Stéphane Marchesin stephane.marche...@gmail.com wrote: On Wed, Mar 6, 2013 at 8:43 PM, Inki Dae inki@samsung.com wrote: 2013/3/7 김승우 sw0312@samsung.com: On 2013년 03월 04일 23:05, Rahul Sharma wrote: Thanks Sean, On Wed, Feb 27, 2013 at 9:47 PM, Sean

[Bug 61965] New: Kernel panics drm_fb_helper_restore_fbdev_mode when using Chromium

https://bugs.freedesktop.org/show_bug.cgi?id=61965 Priority: medium Bug ID: 61965 Assignee: dri-devel@lists.freedesktop.org Summary: Kernel panics drm_fb_helper_restore_fbdev_mode when using Chromium Severity: normal

[Bug 61965] Kernel panics drm_fb_helper_restore_fbdev_mode when using Chromium

https://bugs.freedesktop.org/show_bug.cgi?id=61965 Chris Wilson ch...@chris-wilson.co.uk changed: What|Removed |Added Attachment #76113|text/plain |image/jpeg

[Bug 61965] Kernel panics drm_fb_helper_restore_fbdev_mode when using Chromium

https://bugs.freedesktop.org/show_bug.cgi?id=61965 --- Comment #2 from Mike Lothian m...@fireburn.co.uk --- I'm going to hazzard a guess that either 4d53233a36fdda567cd4d080e27e1ee4b669ddd1 and / or 2e928815c1886fe628ed54623aa98d0889cf5509 are most probably where the problem lies I can't seem

[Bug 61965] Kernel panics drm_fb_helper_restore_fbdev_mode when using Chromium

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

Re: [PATCH v5 4/9] video: Add generic HDMI infoframe helpers

Am Montag, den 04.03.2013, 16:02 +0100 schrieb Thierry Reding: On Mon, Mar 04, 2013 at 04:49:46PM +0200, Ville Syrjälä wrote: On Fri, Feb 22, 2013 at 08:03:26AM +0100, Thierry Reding wrote: [...] diff --git a/drivers/video/hdmi.c b/drivers/video/hdmi.c new file mode 100644 index

Re: [PATCH v5 4/9] video: Add generic HDMI infoframe helpers

On Thu, Mar 07, 2013 at 02:32:51PM +0100, Lucas Stach wrote: Am Montag, den 04.03.2013, 16:02 +0100 schrieb Thierry Reding: On Mon, Mar 04, 2013 at 04:49:46PM +0200, Ville Syrjälä wrote: On Fri, Feb 22, 2013 at 08:03:26AM +0100, Thierry Reding wrote: [...] diff --git

[PATCH v11 0/2] Add display-timing node parsing to exynos drm fimd

Add display-timing node parsing to drm fimd and depends on the display helper patchset at http://lists.freedesktop.org/archives/dri-devel/2013-January/033998.html changes since v10: - abandoned the pinctrl patch, as commented by Linus Walleij linus.wall...@linaro.org -

[PATCH v11 1/2] video: drm: exynos: Add display-timing node parsing using video helper function

Add support for parsing the display-timing node using video helper function. The DT node parsing is done only if 'dev.of_node' exists and the NON-DT logic is still maintained under the 'else' part. Signed-off-by: Leela Krishna Amudala l.kris...@samsung.com Signed-off-by: Vikas Sajjan

[PATCH v11 2/2] drm/exynos: enable OF_VIDEOMODE and FB_MODE_HELPERS for exynos drm fimd

patch adds select OF_VIDEOMODE and select FB_MODE_HELPERS when EXYNOS_DRM_FIMD config is selected. Signed-off-by: Vikas Sajjan vikas.saj...@linaro.org --- drivers/gpu/drm/exynos/Kconfig |2 ++ 1 file changed, 2 insertions(+) diff --git a/drivers/gpu/drm/exynos/Kconfig

Re: [PATCH] drm/exynos: modify the compatible string for exynos fimd

Hi Mr Inki Dae, On 28 February 2013 08:12, Joonyoung Shim jy0922.s...@samsung.com wrote: On 02/27/2013 07:32 PM, Vikas Sajjan wrote: modified compatible string for exynos4 fimd as exynos4210-fimd and exynos5 fimd as exynos5250-fimd to stick to the rule that compatible value should be named

Re: [PATCH] drm/exynos: modify the compatible string for exynos fimd

Thanks. On 7 March 2013 12:47, Inki Dae inki@samsung.com wrote: Already merged. :) -Original Message- From: Vikas Sajjan [mailto:vikas.saj...@linaro.org] Sent: Thursday, March 07, 2013 4:09 PM To: InKi Dae Cc: dri-devel@lists.freedesktop.org; linux-me...@vger.kernel.org;

[PATCH v12 0/2] Add display-timing node parsing to exynos drm fimd

Add display-timing node parsing to drm fimd and depends on the display helper patchset at http://lists.freedesktop.org/archives/dri-devel/2013-January/033998.html changes since v11: - Oops, there was a build error, fixed that. changes since v10: - abandoned the pinctrl patch, as

[PATCH v12 1/2] video: drm: exynos: Add display-timing node parsing using video helper function

Add support for parsing the display-timing node using video helper function. The DT node parsing is done only if 'dev.of_node' exists and the NON-DT logic is still maintained under the 'else' part. Signed-off-by: Leela Krishna Amudala l.kris...@samsung.com Signed-off-by: Vikas Sajjan

[PATCH v12 2/2] drm/exynos: enable OF_VIDEOMODE and FB_MODE_HELPERS for exynos drm fimd

patch adds select OF_VIDEOMODE and select FB_MODE_HELPERS when EXYNOS_DRM_FIMD config is selected. Signed-off-by: Vikas Sajjan vikas.saj...@linaro.org --- drivers/gpu/drm/exynos/Kconfig |2 ++ 1 file changed, 2 insertions(+) diff --git a/drivers/gpu/drm/exynos/Kconfig

[PATCH V3] drm/exynos: fimd: calculate the correct address offset

Calculate the correct address offset values for alpha and color key control registers based on exynos4 and exynos5 user manuals. Signed-off-by: Leela Krishna Amudala l.kris...@samsung.com --- drivers/gpu/drm/exynos/exynos_drm_fimd.c | 17 + 1 file changed, 9 insertions(+), 8

Black screen with nouveau in 3.8.x (regression)

Hi folks, Yesterday I upgraded one of my machines to 3.8.2 from 3.6.6. This machine has an old NV36 AGP board. With the new kernel, as soon as nouveau takes over the console the display connected via DVI goes dark (the monitor goes into standby mode). The display connected via VGA continues to

[PATCH 0/2] mgag200 fix plus documentation typo fixes

This is a fix for mgag200 cards that is well documented in the commit message. Also includes some typo fixes that were bugging me. Christopher Harvey (1): drm: Documentation typo fixes Julia Lemire (1): drm/mgag200: Bug fix: Renesas board now selects native resolution.

[PATCH 2/2] drm: Documentation typo fixes

Signed-off-by: Christopher Harvey char...@matrox.com --- include/drm/drm_crtc.h | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/include/drm/drm_crtc.h b/include/drm/drm_crtc.h index 00d78b5..7294403 100644 --- a/include/drm/drm_crtc.h +++ b/include/drm/drm_crtc.h @@

[PATCH 1/2] drm/mgag200: Bug fix: Renesas board now selects native resolution.

Renesas boards were consistently defaulting to the 1024x768 resolution, regardless of the native resolution of the monitor plugged in. It was determined that the EDID of the monitor was not being read. Since the DAC is a shared line, in order to read from or write to it we must take control of

Wrong vsync offset calculation in drm_edid.c

This patch is a bug fix for the file drm_edid.c of the kernel 3.8. The vsync offset is calculated wrong from the EDID set because of the wrong shift direction. We could measure the bad old setting and also the good new setting after the bug fix. Signed-off-by: Peter Blum peter.b...@lxco.com

[pull] radeon drm-fixes-3.9

From: Alex Deucher alexander.deuc...@amd.com Hi Dave, Radeon fixes pull. Not much to it. - fix some splatter if the interrupt handler isn't registered - Add a quirk for an old R200 board to fix washed out colors on the DAC - Don't try and soft reset the MC when we reset the GPU. It

[Bug 58042] [bisected] Garbled UI in Team Fortress 2 and Counter-Strike: Source

https://bugs.freedesktop.org/show_bug.cgi?id=58042 d...@stuffit.at changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|---

Re: [PATCH V3] drm/exynos: fimd: calculate the correct address offset

On 03/07/2013 06:42 PM, Leela Krishna Amudala wrote: Calculate the correct address offset values for alpha and color key control registers based on exynos4 and exynos5 user manuals. + remove VIDOSD_C_SIZE_W0 macro and fix comments about registers for size and alpha. Signed-off-by: Leela

[PATCH 01/14] x86, ACPI, mm: Kill max_low_pfn_mapped

Now we have arch_pfn_mapped array, and max_low_pfn_mapped should not be used anymore. Only user is ACPI_OVERRIDE, and it should not use that, as later accessing is using early_remap. Change to try to 4G below and then 4G above. Other user is in drm/i915, but it is commented out. Should use

Re: [PATCH 01/14] x86, ACPI, mm: Kill max_low_pfn_mapped

On Thu, Mar 07, 2013 at 08:58:27PM -0800, Yinghai Lu wrote: diff --git a/drivers/gpu/drm/i915/i915_gem_stolen.c b/drivers/gpu/drm/i915/i915_gem_stolen.c index 69d97cb..7f9380b 100644 --- a/drivers/gpu/drm/i915/i915_gem_stolen.c +++ b/drivers/gpu/drm/i915/i915_gem_stolen.c @@ -81,7 +81,7 @@

Re: [PATCH 01/14] x86, ACPI, mm: Kill max_low_pfn_mapped

On Thu, Mar 7, 2013 at 9:10 PM, Tejun Heo t...@kernel.org wrote: On Thu, Mar 07, 2013 at 08:58:27PM -0800, Yinghai Lu wrote: diff --git a/drivers/gpu/drm/i915/i915_gem_stolen.c b/drivers/gpu/drm/i915/i915_gem_stolen.c index 69d97cb..7f9380b 100644 --- a/drivers/gpu/drm/i915/i915_gem_stolen.c

Re: [PATCH 01/14] x86, ACPI, mm: Kill max_low_pfn_mapped

On Thu, Mar 7, 2013 at 9:22 PM, Yinghai Lu ying...@kernel.org wrote: On Thu, Mar 7, 2013 at 9:10 PM, Tejun Heo t...@kernel.org wrote: On Thu, Mar 07, 2013 at 08:58:27PM -0800, Yinghai Lu wrote: diff --git a/drivers/gpu/drm/i915/i915_gem_stolen.c b/drivers/gpu/drm/i915/i915_gem_stolen.c index

Re: [PATCH 01/14] x86, ACPI, mm: Kill max_low_pfn_mapped

On Thu, Mar 7, 2013 at 9:25 PM, Tejun Heo t...@kernel.org wrote: On Thu, Mar 7, 2013 at 9:22 PM, Yinghai Lu ying...@kernel.org wrote: On Thu, Mar 7, 2013 at 9:10 PM, Tejun Heo t...@kernel.org wrote: On Thu, Mar 07, 2013 at 08:58:27PM -0800, Yinghai Lu wrote: diff --git

Re: [PATCH 01/14] x86, ACPI, mm: Kill max_low_pfn_mapped

On Thu, Mar 7, 2013 at 9:27 PM, Yinghai Lu ying...@kernel.org wrote: They are not using memblock_find_in_range(), so 1ULL will not help. Really hope i915 drm guys could clean that hacks. The code isn't being used. Just leave it alone. Maybe add a comment. The change is just making things

Re: [PATCH v12 2/2] drm/exynos: enable OF_VIDEOMODE and FB_MODE_HELPERS for exynos drm fimd

Hi Mr. Dae, On 7 March 2013 13:34, Inki Dae inki@samsung.com wrote: -Original Message- From: linux-media-ow...@vger.kernel.org [mailto:linux-media- ow...@vger.kernel.org] On Behalf Of Vikas Sajjan Sent: Thursday, March 07, 2013 4:40 PM To: dri-devel@lists.freedesktop.org Cc:

[PATCH V4] drm/exynos: fimd: calculate the correct address offset

Calculate the correct address offset values for alpha and color key control registers based on exynos4 and exynos5 user manuals. Also remove VIDOSD_C_SIZE_W0 macro and fix comments about registers for size and alpha. Signed-off-by: Leela Krishna Amudala l.kris...@samsung.com Acked-by: Joonyoung

Re: [PATCH 01/14] x86, ACPI, mm: Kill max_low_pfn_mapped

On 03/07/2013 09:28 PM, Tejun Heo wrote: On Thu, Mar 7, 2013 at 9:27 PM, Yinghai Lu ying...@kernel.org wrote: They are not using memblock_find_in_range(), so 1ULL will not help. Really hope i915 drm guys could clean that hacks. The code isn't being used. Just leave it alone. Maybe add a