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
---
drivers/gpu/
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.
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 -0800)
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
---
drivers/gpu/
Hi Mr. Dae,
On 7 March 2013 13:34, Inki Dae 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: linux-me
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.
dri-devel/attachments/20130307/e0d3a38a/attachment.html>
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.
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.
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
b/drivers/gpu/dr
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
b/drivers/gpu/dr
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 1006
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 1006
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
>> +++
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
>> +++
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,
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,
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 arch_
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 arch_
.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20130307/c95adb66/attachment.html>
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
> -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
> Sub
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 Krish
> -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;
>
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 a/driver
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
> Subje
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, Fe
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
> lot harder 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>
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 -0800)
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
> > >
https://bugs.freedesktop.org/show_bug.cgi?id=58042
d...@stuffit.at changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Resolution|---
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
>
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 usually doesn't
need it a
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 046
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
---
d
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 c
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;
>> kge
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
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
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 ]
> [0.6
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 046
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
---
d
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 th
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:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20130307/7af66445/attachment.html>
Tejun Heo - 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>
vel/attachments/20130307/67d880a6/attachment.html>
||
--
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>
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 couple
re the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20130307/db38645e/attachment-0001.html>
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 @@ stru
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 th
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.
drivers/gpu/drm/mgag2
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 cha
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 usually doesn't
need it a
https://bugs.freedesktop.org/show_bug.cgi?id=61979
Alex Deucher changed:
What|Removed |Added
Assignee|xorg-driver-...@lists.x.org |dri-devel@lists.freedesktop
available
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20130307/56055089/attachment.bin>
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 th
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 th
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(struc
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 a/driv
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 th
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 @@ stru
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.
drivers/gpu/drm/mgag2
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
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 me
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 a
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 046
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
---
d
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 c
Thanks.
On 7 March 2013 12:47, Inki Dae 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;
>> kgene@sa
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
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 046
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
---
d
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 th
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 a/drive
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
> > >
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 a
https://bugs.freedesktop.org/show_bug.cgi?id=61965
Mike Lothian changed:
What|Removed |Added
CC||m...@fireburn.co.uk
--- Comment #3 from M
https://bugs.freedesktop.org/show_bug.cgi?id=61965
--- Comment #2 from Mike Lothian ---
I'm going to hazzard a guess that either
4d53233a36fdda567cd4d080e27e1ee4b669ddd1 and / or
2e928815c1886fe628ed54623aa98d0889cf5509 are most probably where the problem
lies
I can't seem to CC Tejun Heo - a
https://bugs.freedesktop.org/show_bug.cgi?id=61965
Chris Wilson changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=61965
Chris Wilson changed:
What|Removed |Added
Attachment #76113|text/plain |image/jpeg
mime type|
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
Clas
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
> -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: [P
> -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: linux-me...@vger.kernel.org; kgene@samsung.com;
> inki@samsun
87 matches
Mail list logo
