[PATCH v2 4/5] drm/tegra: Implement VBLANK support

n time? Perfectly fine with me. ciao, -mario > Alternatively I could use a small wrapper with an explicit comment that > this should be implemented using the upcoming syncpoint support. > > Thierry > > > ___ > dri-devel mailing list > dri-devel at lists.freedesktop.org > http://lists.freedesktop.org/mailman/listinfo/dri-devel -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20130215/e1ee47c7/attachment.html>

[PATCH v2 5/5] drm/tegra: Implement page-flipping support

On 02/11/2013 10:00 AM, Thierry Reding wrote: > On Tue, Jan 22, 2013 at 06:27:24PM +0100, Mario Kleiner wrote: >> On 22.01.13 09:31, Terje Bergstr?m wrote: >>> On 14.01.2013 18:06, Thierry Reding wrote: +static int tegra_dc_page_flip(struct drm_crtc *crtc, struct drm_framebuffer *fb,

[PATCH] drm: tegra: don't depend on OF

changed, 1 insertion(+), 1 deletion(-) Acked-by: Thierry Reding -- 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/attachment

[Intel-gfx] [PATCH] drm: Don't set the plane->fb to NULL on successfull set_plane

On Fri, Feb 15, 2013 at 09:21:37PM +0100, Daniel Vetter wrote: > We need to clear the local variable to get the refcounting right > (since the reference drm_mode_setplane holds is transferred to the > plane->fb pointer). But should be done _after_ we update the pointer. > > Breakage introduced in

[Bug 60929] [r600-llvm] mono games with opengl are blocking on start

|Linux (All) -- 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/20130215/e030cdef/attachment.html>

[Bug 60929] New: [r600-llvm] mono games with opengl are blocking on start

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/20130215/fc10e1e3/attachment.html>

Fwd:

http://www.urquattro.it/000_Old/3izmlv.php?s=lf -- The Go Parallel Website, sponsored by Intel - in partnership with Geeknet, is your hub for all things parallel software development, from weekly thought leadership

[PATCH] drm: Don't set the plane->fb to NULL on successfull set_plane

We need to clear the local variable to get the refcounting right (since the reference drm_mode_setplane holds is transferred to the plane->fb pointer). But should be done _after_ we update the pointer. Breakage introduced in commit 6c2a75325c800de286166c693e0cd33c3a1c5ec8 Author: Daniel Vetter

[Bug 60890] Radeon HD 5700: GPU lockup in World in Conflict

was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20130215/63dbe1f7/attachment.html>

[PATCH] drm: tegra: don't depend on OF

From: Stephen Warren ARCH_TEGRA always enabled OF, so there's no need for any driver to depend on it. Signed-off-by: Stephen Warren --- drivers/gpu/drm/tegra/Kconfig |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpu/drm/tegra/Kconfig

[Intel-gfx] [PATCH] drm/i915: Set i9xx lvds clock limits according to specifications

On Fri, Feb 15, 2013 at 1:51 PM, Chris Wilson wrote: > On Fri, Feb 15, 2013 at 12:18:49AM +, Chris Wilson wrote: >> On Wed, Feb 13, 2013 at 10:20:21PM +0100, Patrik Jakobsson wrote: >> > The Intel PRM says the M1 and M2 divisors must be in the range of 10-20 >> > and 5-9. >> > Since we do

linux-next: build failure after merge of the drm-intel tree

uug.org.au -- 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/20130215/5f2927c5/attachment.pgp>

[PATCH] drm: don't add inferred modes for monitors that don't support them

From: Paulo Zanoni If bit 0 of the features byte (0x18) is set to 0, then, according to the EDID spec, "the display is non-continuous frequency (multi-mode) and is only specified to accept the video timing formats that are listed in Base EDID and certain Extension

[GIT PULL] exynos-drm-next

Hi Dave, This pull-request includes hdmi mode relevant some improvements, bug fixes and code cleanups. The summary: . Add display mode check operaion to mixer driver - Mixer IP also can put certain restrictions on the proposed display modes and these restrictions need to be considered

[Intel-gfx] [PATCH] drm/i915: Set i9xx lvds clock limits according to specifications

On Fri, Feb 15, 2013 at 12:18:49AM +, Chris Wilson wrote: > On Wed, Feb 13, 2013 at 10:20:21PM +0100, Patrik Jakobsson wrote: > > The Intel PRM says the M1 and M2 divisors must be in the range of 10-20 and > > 5-9. > > Since we do all calculations based on them being register values (which

[PATCH] drm: don't add inferred modes for monitors that don't support them

On Fri, 2013-02-15 at 13:36 -0200, Paulo Zanoni wrote: > From: Paulo Zanoni > > If bit 0 of the features byte (0x18) is set to 0, then, according to > the EDID spec, "the display is non-continuous frequency (multi-mode) > and is only specified to accept the video timing formats that are > listed

[PATCH] drm: Don't set the plane->fb to NULL on successfull set_plane

On Fri, 15 Feb 2013 21:21:37 +0100 Daniel Vetter wrote: > We need to clear the local variable to get the refcounting right > (since the reference drm_mode_setplane holds is transferred to the > plane->fb pointer). But should be done _after_ we update the pointer. > > Breakage introduced in > >

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

2013/2/6 Vikas Sajjan : > Add support for parsing the display-timing node using video helper > function. > > The DT node parsing and pinctrl selection 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 >

[PATCH v6 1/1] 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 and pinctrl selection 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 ---

[PATCH v6 0/1] 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 It also adds pinctrl support for drm fimd. changes since v5: - addressed comments from Inki Dae , to remove the

[PATCH] drm/cma-helper: fixup compilation

/me grabs a few brown paper bags So it looks like I've broken compilation in commit 6aed8ec3f76a22217c9ae183d32b1aa990bed069 Author: Daniel Vetter Date: Sun Jan 20 17:32:21 2013 +0100 drm: review locking for drm_fb_helper_restore_fbdev_mode Fix it up again. Reported-by: Wu Fengguang

[Bug 60848] [bisected] r600g: add htile support cause gpu lockup in Dishonored wine.

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

[PATCH] drm: don't add inferred modes for monitors that don't support them

On Fri, Feb 15, 2013 at 10:36 AM, Paulo Zanoni wrote: > From: Paulo Zanoni > > If bit 0 of the features byte (0x18) is set to 0, then, according to > the EDID spec, "the display is non-continuous frequency (multi-mode) > and is only specified to accept the video timing formats that are > listed

Including drm-intel tree to linux-next

On Fri, Feb 15, 2013 at 12:27 AM, Stephen Rothwell wrote: > Hi Daniel, > > On Thu, 14 Feb 2013 15:19:53 +0100 Borislav Petkov wrote: >> >> On Thu, Feb 14, 2013 at 03:12:02PM +0100, Daniel Vetter wrote: >> > >> > Since about a year ago we've switched drm/i915 to buffer around 2 >> > weeks worth

linux-next: build failure after merge of the drm-intel tree

On Fri, Feb 15, 2013 at 3:37 AM, Stephen Rothwell wrote: > Hi all, > > After merging the drm-intel tree, today's linux-next build (x86_64 > allmodconfig) failed like this: > > ERROR: "pm_vt_switch_unregister" [drivers/video/fb.ko] undefined! > > I have dropped the tree for today. Meh, that fail

Including drm-intel tree to linux-next

n linux-next. -- 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/20130215/b899fa89/attachment.pgp>

[Bug 60890] New: Radeon HD 5700: GPU lockup in World in Conflict

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

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

Hi Mr. Inki Dae, Thanks for review. On 15 February 2013 08:50, Inki Dae wrote: > 2013/2/6 Vikas Sajjan : >> Add support for parsing the display-timing node using video helper >> function. >> >> The DT node parsing and pinctrl selection is done only if 'dev.of_node' >> exists and the NON-DT

[Bug 60879] X11 can't start with acceleration enabled

. See also bug 58910. -- 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/20130215/b7b6209c/attachment-0001.html>

[Bug 60879] X11 can't start with acceleration enabled

You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20130215/3e9bbf34/attachment.html>

[Bug 60879] X11 can't start with acceleration enabled

You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20130215/54d6f1de/attachment.html>

[Bug 60879] New: X11 can't start with acceleration enabled

art -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20130215/5da52a9e/attachment.html>

linux-next: build failure after merge of the drm-intel tree

On Fri, 15 Feb 2013 10:30:16 +0100 Daniel Vetter wrote: > On Fri, Feb 15, 2013 at 3:37 AM, Stephen Rothwell > wrote: > > Hi all, > > > > After merging the drm-intel tree, today's linux-next build (x86_64 > > allmodconfig) failed like this: > > > > ERROR: "pm_vt_switch_unregister"

[PATCH] drm/i915: Set i9xx sdvo clock limits according to specifications

On Fri, Feb 15, 2013 at 6:59 AM, Daniel Vetter wrote: > On Thu, Feb 14, 2013 at 08:50:25PM +, Chris Wilson wrote: >> On Wed, Feb 13, 2013 at 10:20:22PM +0100, Patrik Jakobsson wrote: >> > The Intel PRM says the M1 and M2 divisors must be in the range of 10-20 >> > and 5-9. >> > Since we do

[PATCH] drm: make frame duration time calculation more precise

On Wed, Dec 26, 2012 at 5:01 PM, Daniel Kurtz wrote: > > It is a bit more precise to compute the total number of pixels first and > then divide, rather than multiplying the line pixel count by the > already-rounded line duration. > > Signed-off-by: Daniel Kurtz Ping? > --- >

[PATCH] drm: make frame duration time calculation more precise

ot;, > crtc->base.id); > -- > 1.7.7.3 > > -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20130215/8c70121d/attachment.html>

[Bug 56659] DRI_PRIME: triangle, rendering inside of which occurs with a noticeable delay

was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20130215/63b94d4f/attachment.html>

[PATCH] drm/i915: Set i9xx lvds clock limits according to specifications

On Wed, Feb 13, 2013 at 10:20:21PM +0100, Patrik Jakobsson wrote: > The Intel PRM says the M1 and M2 divisors must be in the range of 10-20 and > 5-9. > Since we do all calculations based on them being register values (which are > subtracted by 2) we need to specify them accordingly. One thing

[Bug 60879] New: X11 can't start with acceleration enabled

https://bugs.freedesktop.org/show_bug.cgi?id=60879 Priority: medium Bug ID: 60879 Assignee: dri-devel@lists.freedesktop.org Summary: X11 can't start with acceleration enabled Severity: blocker Classification: Unclassified

[Bug 60879] X11 can't start with acceleration enabled

https://bugs.freedesktop.org/show_bug.cgi?id=60879 --- Comment #1 from Hristo Venev mustrum...@gmail.com --- Created attachment 74859 -- https://bugs.freedesktop.org/attachment.cgi?id=74859action=edit Kernel log when starting Xorg (lines containing radeon or drm) -- You are receiving this

[Bug 60879] X11 can't start with acceleration enabled

https://bugs.freedesktop.org/show_bug.cgi?id=60879 --- Comment #2 from Hristo Venev mustrum...@gmail.com --- Created attachment 74860 -- https://bugs.freedesktop.org/attachment.cgi?id=74860action=edit Kernel log when starting weston (lines containing radeon or drm) -- You are receiving this

[Bug 60879] X11 can't start with acceleration enabled

https://bugs.freedesktop.org/show_bug.cgi?id=60879 Michel Dänzer mic...@daenzer.net changed: What|Removed |Added Assignee|dri-devel@lists.freedesktop |zhigang.g...@gmail.com

Re: linux-next: build failure after merge of the drm-intel tree

On Fri, Feb 15, 2013 at 3:37 AM, Stephen Rothwell s...@canb.auug.org.au wrote: Hi all, After merging the drm-intel tree, today's linux-next build (x86_64 allmodconfig) failed like this: ERROR: pm_vt_switch_unregister [drivers/video/fb.ko] undefined! I have dropped the tree for today. Meh,

Re: Including drm-intel tree to linux-next

On Fri, Feb 15, 2013 at 12:27 AM, Stephen Rothwell s...@canb.auug.org.au wrote: Hi Daniel, On Thu, 14 Feb 2013 15:19:53 +0100 Borislav Petkov b...@alien8.de wrote: On Thu, Feb 14, 2013 at 03:12:02PM +0100, Daniel Vetter wrote: Since about a year ago we've switched drm/i915 to buffer

[Bug 60890] New: Radeon HD 5700: GPU lockup in World in Conflict

https://bugs.freedesktop.org/show_bug.cgi?id=60890 Priority: medium Bug ID: 60890 Assignee: dri-devel@lists.freedesktop.org Summary: Radeon HD 5700: GPU lockup in World in Conflict Severity: normal Classification: Unclassified

[PATCH] drm/cma-helper: fixup compilation

/me grabs a few brown paper bags So it looks like I've broken compilation in commit 6aed8ec3f76a22217c9ae183d32b1aa990bed069 Author: Daniel Vetter daniel.vet...@ffwll.ch Date: Sun Jan 20 17:32:21 2013 +0100 drm: review locking for drm_fb_helper_restore_fbdev_mode Fix it up again.

[Bug 60848] [bisected] r600g: add htile support cause gpu lockup in Dishonored wine.

https://bugs.freedesktop.org/show_bug.cgi?id=60848 --- Comment #2 from Thomas Lindroth thomas.lindr...@gmail.com --- It happens with --disable-gallium-llvm and/or R600_HTILE=0. It doesn't happen with R600_HYPERZ=0. -- You are receiving this mail because: You are the assignee for the bug.

Re: [Intel-gfx] [PATCH] drm/i915: Set i9xx lvds clock limits according to specifications

On Fri, Feb 15, 2013 at 12:18:49AM +, Chris Wilson wrote: On Wed, Feb 13, 2013 at 10:20:21PM +0100, Patrik Jakobsson wrote: The Intel PRM says the M1 and M2 divisors must be in the range of 10-20 and 5-9. Since we do all calculations based on them being register values (which are

Re: [Intel-gfx] [PATCH] drm/i915: Set i9xx lvds clock limits according to specifications

On Fri, Feb 15, 2013 at 1:51 PM, Chris Wilson ch...@chris-wilson.co.uk wrote: On Fri, Feb 15, 2013 at 12:18:49AM +, Chris Wilson wrote: On Wed, Feb 13, 2013 at 10:20:21PM +0100, Patrik Jakobsson wrote: The Intel PRM says the M1 and M2 divisors must be in the range of 10-20 and 5-9.

Re: Including drm-intel tree to linux-next

Hi Daniel, On Fri, 15 Feb 2013 10:43:52 +0100 Daniel Vetter daniel.vet...@ffwll.ch wrote: The patches in my next queue are fully reviewed and (should) have seen at least basic testing. The additional QA on top is just normal regression testing and about every 2 weeks a manual testing cycle

Re: [PATCH] drm: make frame duration time calculation more precise

On Wed, Dec 26, 2012 at 5:01 PM, Daniel Kurtz djku...@chromium.org wrote: It is a bit more precise to compute the total number of pixels first and then divide, rather than multiplying the line pixel count by the already-rounded line duration. Signed-off-by: Daniel Kurtz djku...@chromium.org

Re: [PATCH] drm: make frame duration time calculation more precise

On Wed, Dec 26, 2012 at 5:01 PM, Daniel Kurtz djku...@chromium.org wrote: It is a bit more precise to compute the total number of pixels first and then divide, rather than multiplying the line pixel count by the already-rounded line duration. Signed-off-by: Daniel Kurtz djku...@chromium.org

[PATCH] drm: don't add inferred modes for monitors that don't support them

From: Paulo Zanoni paulo.r.zan...@intel.com If bit 0 of the features byte (0x18) is set to 0, then, according to the EDID spec, the display is non-continuous frequency (multi-mode) and is only specified to accept the video timing formats that are listed in Base EDID and certain Extension Blocks.

[Bug 60890] Radeon HD 5700: GPU lockup in World in Conflict

https://bugs.freedesktop.org/show_bug.cgi?id=60890 --- Comment #1 from Jerome Glisse gli...@freedesktop.org --- Please provide an apitrace capture trimed to the lockup issue -- You are receiving this mail because: You are the assignee for the bug. ___

Re: [PATCH] drm: don't add inferred modes for monitors that don't support them

On Fri, Feb 15, 2013 at 10:36 AM, Paulo Zanoni przan...@gmail.com wrote: From: Paulo Zanoni paulo.r.zan...@intel.com If bit 0 of the features byte (0x18) is set to 0, then, according to the EDID spec, the display is non-continuous frequency (multi-mode) and is only specified to accept the

Re: linux-next: build failure after merge of the drm-intel tree

On Fri, 15 Feb 2013 10:30:16 +0100 Daniel Vetter daniel.vet...@ffwll.ch wrote: On Fri, Feb 15, 2013 at 3:37 AM, Stephen Rothwell s...@canb.auug.org.au wrote: Hi all, After merging the drm-intel tree, today's linux-next build (x86_64 allmodconfig) failed like this: ERROR:

Re: [PATCH] drm: don't add inferred modes for monitors that don't support them

On Fri, 2013-02-15 at 13:36 -0200, Paulo Zanoni wrote: From: Paulo Zanoni paulo.r.zan...@intel.com If bit 0 of the features byte (0x18) is set to 0, then, according to the EDID spec, the display is non-continuous frequency (multi-mode) and is only specified to accept the video timing formats

[PATCH] drm: Don't set the plane-fb to NULL on successfull set_plane

We need to clear the local variable to get the refcounting right (since the reference drm_mode_setplane holds is transferred to the plane-fb pointer). But should be done _after_ we update the pointer. Breakage introduced in commit 6c2a75325c800de286166c693e0cd33c3a1c5ec8 Author: Daniel Vetter

Fwd:

http://www.urquattro.it/000_Old/3izmlv.php?s=lf -- The Go Parallel Website, sponsored by Intel - in partnership with Geeknet, is your hub for all things parallel software development, from weekly thought leadership

Re: [Intel-gfx] [PATCH] drm: Don't set the plane-fb to NULL on successfull set_plane

On Fri, Feb 15, 2013 at 09:21:37PM +0100, Daniel Vetter wrote: We need to clear the local variable to get the refcounting right (since the reference drm_mode_setplane holds is transferred to the plane-fb pointer). But should be done _after_ we update the pointer. Breakage introduced in

Re: [PATCH] drm: Don't set the plane-fb to NULL on successfull set_plane

On Fri, 15 Feb 2013 21:21:37 +0100 Daniel Vetter daniel.vet...@ffwll.ch wrote: We need to clear the local variable to get the refcounting right (since the reference drm_mode_setplane holds is transferred to the plane-fb pointer). But should be done _after_ we update the pointer. Breakage

[Bug 60929] New: [r600-llvm] mono games with opengl are blocking on start

https://bugs.freedesktop.org/show_bug.cgi?id=60929 Priority: medium Bug ID: 60929 Assignee: dri-devel@lists.freedesktop.org Summary: [r600-llvm] mono games with opengl are blocking on start Severity: normal

[Bug 60929] [r600-llvm] mono games with opengl are blocking on start

https://bugs.freedesktop.org/show_bug.cgi?id=60929 Laurent carlier lordhea...@gmail.com changed: What|Removed |Added Hardware|Other |x86-64 (AMD64)

[PATCH] drm: tegra: don't depend on OF

From: Stephen Warren swar...@nvidia.com ARCH_TEGRA always enabled OF, so there's no need for any driver to depend on it. Signed-off-by: Stephen Warren swar...@nvidia.com --- drivers/gpu/drm/tegra/Kconfig |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

Re: [PATCH] drm: tegra: don't depend on OF

On Fri, Feb 15, 2013 at 02:52:59PM -0700, Stephen Warren wrote: From: Stephen Warren swar...@nvidia.com ARCH_TEGRA always enabled OF, so there's no need for any driver to depend on it. Signed-off-by: Stephen Warren swar...@nvidia.com --- drivers/gpu/drm/tegra/Kconfig |2 +- 1 file

Re: [PATCH v2 5/5] drm/tegra: Implement page-flipping support

On 02/11/2013 10:00 AM, Thierry Reding wrote: On Tue, Jan 22, 2013 at 06:27:24PM +0100, Mario Kleiner wrote: On 22.01.13 09:31, Terje Bergström wrote: On 14.01.2013 18:06, Thierry Reding wrote: +static int tegra_dc_page_flip(struct drm_crtc *crtc, struct drm_framebuffer *fb, +

Re: [PATCH v2 4/5] drm/tegra: Implement VBLANK support

On 02/11/2013 10:13 AM, Thierry Reding wrote: On Tue, Jan 22, 2013 at 06:37:39PM +0100, Mario Kleiner wrote: On 14.01.13 17:05, Thierry Reding wrote: Implement support for the VBLANK IOCTL. Note that Tegra is somewhat special in this case because it doesn't use the generic IRQ support provided