Multiple parents in device driver model and Common Display Framework (CDF)

n be use as inspiration? Was the discussion about handling one device from multiple drivers concluded/implemented? It sounds very much what we are trying to do? Or this was just some f2f discussion? BR Marcus Mobile -- next part -- An HTML attachment was scrubbed... URL: <

compositing broken in -next (idr bug)

On 02/12/2013 11:03 PM, Jiri Slaby wrote: > On 02/12/2013 10:55 PM, Jiri Slaby wrote: >> --- a/drivers/gpu/drm/drm_gem.c >> +++ b/drivers/gpu/drm/drm_gem.c >> @@ -453,7 +453,8 @@ drm_gem_flink_ioctl(struct drm_device *dev, void *data, >> spin_lock(>object_name_lock); >> if

compositing broken in -next (idr bug)

On 02/12/2013 10:55 PM, Jiri Slaby wrote: > --- a/drivers/gpu/drm/drm_gem.c > +++ b/drivers/gpu/drm/drm_gem.c > @@ -453,7 +453,8 @@ drm_gem_flink_ioctl(struct drm_device *dev, void *data, > spin_lock(>object_name_lock); > if (!obj->name) { > ret =

[PATCH v2 1/2] [media] s5p-g2d: Add DT based discovery support

tachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20130212/a3c8cbaa/attachment-0001.html>

compositing broken in -next (idr bug)

On 02/12/2013 10:58 PM, Tejun Heo wrote: > Hello, Jiri. > > On Tue, Feb 12, 2013 at 10:55:37PM +0100, Jiri Slaby wrote: >> this commit in -next causes my KDE to get stuck while starting. I see >> only the splash screen. If I disable effects by alt-shift-f12, it continues. >> >> I bisected it to

[PATCH v2 2/2] drm/exynos: Add device tree based discovery support for G2D

2013/2/12 Sylwester Nawrocki : > On 02/12/2013 02:17 PM, Inki Dae wrote: >> Applied and will go to -next. >> And please post the document(in >> Documentation/devicetree/bindings/gpu/) for it later. > > There is already some old patch applied in the devicetree/next tree: > >

compositing broken in -next (idr bug)

Hi, this commit in -next causes my KDE to get stuck while starting. I see only the splash screen. If I disable effects by alt-shift-f12, it continues. I bisected it to this commit: commit 430440fce7da4ad52c2af06a04a5132e5d19faaf Author: Tejun Heo Date: Thu Feb 7 12:31:37 2013 +1100 drm:

[PATCH 2/2] drm/exynos: Add device tree based discovery support for G2D

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

[PATCH v2 2/2] drm/exynos: Add device tree based discovery support for G2D

Applied and will go to -next. And please post the document(in Documentation/devicetree/bindings/gpu/) for it later. Thanks, Inki Dae 2013/2/6 Sachin Kamat : > From: Ajay Kumar > > This patch adds device tree match table for Exynos G2D controller. > > Signed-off-by: Ajay Kumar > Signed-off-by:

[Bug 59592] Radeon HD 5670: reproducable GPU lockups with htile enabled

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

[Bug 60073] [bisected] Bad rendering in Path of Exile

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

[Bug 53391] nouveau: wrong display output order

https://bugzilla.kernel.org/show_bug.cgi?id=53391 --- Comment #11 from Marcin Slusarz 2013-02-12 21:36:52 --- Created an attachment (id=93171) --> (https://bugzilla.kernel.org/attachment.cgi?id=93171) quirk v3 maybe this one? -- Configure bugmail:

[PATCH] drm/exynos: release resources properly when fb creation is failed.

From: YoungJun Cho This patch releases allocated resources properly when exynos_user_fb_create() is failed. Signed-off-by: YoungJun Cho Signed-off-by: Inki Dae Signed-off-by: Kyungmin Park --- drivers/gpu/drm/exynos/exynos_drm_fb.c | 51

[git pull] drm nouveau fixes.

> > just 3 nouveau fixes, all user visible issues, I have one radeon > regression fix I'm hoping to send tomorrow once I'm happy with it. Okay I've added the radeon regression fix on top as well The following changes since commit ff7c60c580d9722f820d85c9c58ca55ecc1ee7c4: drm/ttm: fix fence

[PATCH] drm/exynos: fix wrong pointer access at vm close.

From: YoungJun Cho This patch fixes wrong pointer access issue to filp->f_op and filp->private_data. The exynos_drm_gem_mmap_ioctl() changes filp->f_op and filp->private_data temporarily and restore them to use original ones in exynos_drm_gem_mmap_buffer() but there was no

Multiple parents in device driver model and Common Display Framework (CDF)

accept it" as you said above, which could be because I'm so accustomed to a certain way of seeing this whole display bus thing. So please continue with this approach, and prove my worries wrong =). Tomi -- next part -- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 899 bytes Desc: OpenPGP digital signature URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20130212/46a819ca/attachment-0001.pgp>

Building DRM for i.MX fails with linux-next 20130212

Dave/Bjorn, On Tue, Feb 12, 2013 at 3:50 PM, Fabio Estevam wrote: > Hi, > > Building imx_v6_v7_defconfig on linux-next 20130212 gives me the > following build error: > > CC drivers/gpu/drm/drm_pci.o > drivers/gpu/drm/drm_pci.c: In function ?drm_pcie_get_speed_cap_mas

[Bug 49981] [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -12!

https://bugzilla.kernel.org/show_bug.cgi?id=49981 J?r?me Glisse changed: What|Removed |Added Status|NEW |RESOLVED Resolution|

[Bug 60236] corruption of text and bottom of screen in xonotic menus since 325422c49449acdd8df1eb2ca8ed81f7696c38cc

ttp://lists.freedesktop.org/archives/dri-devel/attachments/20130212/3c69df66/attachment.html>

[Bug 59592] Radeon HD 5670: reproducable GPU lockups with htile enabled

nee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20130212/db891721/attachment.html>

Multiple parents in device driver model and Common Display Framework (CDF)

On 02/12/2013 04:53 PM, Tomi Valkeinen wrote: > On 2013-02-12 17:04, Marcus Lorentzon wrote: > >> Now we have some different types of panels which are attached on a >> combination of busses: >> >> a) control:DBI, data:DBI >> b) control:I2C/SPI, data:I2C/SPI >> c) control:static setup, data:DPI >>

Multiple parents in device driver model and Common Display Framework (CDF)

rubbed... Name: signature.asc Type: application/pgp-signature Size: 899 bytes Desc: OpenPGP digital signature URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20130212/12f58e3d/attachment-0001.pgp>

[Bug 60503] [r300g] Unigine Heaven 3.0: all objects are black

en is still black. -- 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/20130212/a8317e11/attachment.html>

Multiple parents in device driver model and Common Display Framework (CDF)

Hi Greg, at FOSDEM we had a session on CDF (Common Display Framework). You can read more details about this in the posts from Laurent Pinchart on dridevel: http://lists.freedesktop.org/archives/dri-devel/2012-November/030888.html

[systemd-devel] Someone working on gui for multiseat?

On 02/11/13 21:30, Lennart Poettering wrote: [?] > Of course, doing this via the command line is not user-frienldy, but > maybe this will one day get fixed and somebody writes a proper UI for > it... > Regarding 'loginctl attach seat0 ', the only thing really missing is the 'sys' path

Building DRM for i.MX fails with linux-next 20130212

Hi, Building imx_v6_v7_defconfig on linux-next 20130212 gives me the following build error: CC drivers/gpu/drm/drm_pci.o drivers/gpu/drm/drm_pci.c: In function ?drm_pcie_get_speed_cap_mask?: drivers/gpu/drm/drm_pci.c:485:2: error: implicit declaration of function

[Bug 60503] [r300g] Unigine Heaven 3.0: all objects are black

apply the patches, run make check from src/gallium/drivers/r300 and make sure it passes and then re-test Heaven. -- 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/arc

[PATCH v3 4/4] modetest: Add a command line parameter to select the driver

If the -M parameter is specific, modetest will use the requested device name instead of trying its builtin list of device names. Signed-off-by: Laurent Pinchart Reviewed-by: Jani Nikula --- tests/modetest/modetest.c | 41 - 1 file changed, 28

[PATCH v3 3/4] modetest: Sort command line arguments

The current mostly random sort order hinders code readability. Sort the options alphabetically in the code, and by group in the help message. Signed-off-by: Laurent Pinchart Reviewed-by: Jani Nikula --- tests/modetest/modetest.c | 49 ++- 1 file

[PATCH v3 2/4] modetest: Remove extern declarations of opt(arg|ind|err|opt)

Those variables are declared in unistd.h, there's no need to redeclare them here. Signed-off-by: Laurent Pinchart Reviewed-by: Jani Nikula --- tests/modetest/modetest.c | 2 -- 1 file changed, 2 deletions(-) diff --git a/tests/modetest/modetest.c b/tests/modetest/modetest.c index

[PATCH v3 1/4] modetest: Fix warnings

Enable all standard automake warnings except for -Wpointer-arith (as the test pattern generation code uses void pointer arithmetics) and fix them. Signed-off-by: Laurent Pinchart --- tests/modetest/Makefile.am | 4 +++- tests/modetest/buffers.c | 13 +++-- tests/modetest/buffers.h

[PATCH v3 0/4] modetest enhancements

Hello, Here's the third version of a small patch set that adds an argument to the modetest command line to specify the driver name instead of using the builtin list of drivers. This is particularly handy during development of new DRM/KMS drivers. This version enables compiler warnings for

CDF meeting @FOSDEM report

On Tue, Feb 5, 2013 at 2:27 PM, Laurent Pinchart wrote: > Hello, > > We've hosted a CDF meeting at the FOSDEM on Sunday morning. Here's a summary > of the discussions. > > I would like to start with a big thank to UrLab, the ULB university hacker > space, for providing us with a meeting room. > >

linux-next: Tree for Feb 12 (drm_pci.c)

On Tue, Feb 12, 2013 at 08:06:00AM -0800, Randy Dunlap wrote: > On 02/11/13 21:09, Stephen Rothwell wrote: > > Hi all, > > > > Changes since 20130211: > > > > > when CONFIG_PCI is not enabled (on x86_64): > > CC [M] drivers/gpu/drm/drm_pci.o > drivers/gpu/drm/drm_pci.c: In function

Building DRM for i.MX fails with linux-next 20130212

On Tue, Feb 12, 2013 at 07:20:30PM -0200, Fabio Estevam wrote: > Dave/Bjorn, > > On Tue, Feb 12, 2013 at 3:50 PM, Fabio Estevam wrote: > > Hi, > > > > Building imx_v6_v7_defconfig on linux-next 20130212 gives me the > > following build error: > >

[PATCH v2 2/2] drm/exynos: Add device tree based discovery support for G2D

On 02/12/2013 02:17 PM, Inki Dae wrote: > Applied and will go to -next. > And please post the document(in > Documentation/devicetree/bindings/gpu/) for it later. There is already some old patch applied in the devicetree/next tree:

Multiple parents in device driver model and Common Display Framework (CDF)

On Tue, Feb 12, 2013 at 11:20:04PM +0100, Marcus Lorentzon wrote: > Den 12 feb 2013 23:02 skrev "Greg KH" : > > > > On Tue, Feb 12, 2013 at 04:04:53PM +0100, Marcus Lorentzon wrote: > > > 3) Daniel V hinted that multiple parents (or multiple busses) is > > > something that has been discussed as a

[PATCH] CHROMIUM: dma-buf: restore args on failure of dma_buf_mmap

+dri-devel ML > > > On 12 February 2013 07:20, wrote: >> >> From: John Sheu >> >> Callers to dma_buf_mmap expect to fput() the vma struct's vm_file >> themselves on failure. Not restoring the struct's data on failure >> causes a double-decrement of the vm_file's refcount. >> >> Signed-off-by:

[Bug 60723] Unable to compile Mesa 9.0.2 for radeon

ves/dri-devel/attachments/20130212/dfe19f90/attachment.html>

[PATCH] CHROMIUM: dma-buf: restore args on failure of dma_buf_mmap

;* **? *Open source software for ARM SoCs* *** Follow *Linaro: *Facebook <http://www.facebook.com/pages/Linaro> | Twitter<http://twitter.com/#!/linaroorg> | Blog <http://www.linaro.org/linaro-blog/> -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20130212/fe3d741f/attachment.html>

compositing broken in -next (idr bug)

Hello, Jiri. On Tue, Feb 12, 2013 at 11:08:41PM +0100, Jiri Slaby wrote: > > Oh my, maybe: return ret < 0 ? ret : 0... Let's try. > > Bull's eye. Aieee > --- a/drivers/gpu/drm/drm_gem.c > +++ b/drivers/gpu/drm/drm_gem.c > @@ -459,6 +459,7 @@ drm_gem_flink_ioctl(struct drm_device *dev, void

[Bug 60723] Unable to compile Mesa 9.0.2 for radeon

e full output from configure and make. -- 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/20130212/1863f608/attachment-0001.html>

[Bug 60723] Unable to compile Mesa 9.0.2 for radeon

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

[Bug 60723] Unable to compile Mesa 9.0.2 for radeon

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

Multiple parents in device driver model and Common Display Framework (CDF)

On Tue, Feb 12, 2013 at 04:04:53PM +0100, Marcus Lorentzon wrote: > 3) Daniel V hinted that multiple parents (or multiple busses) is > something that has been discussed as a limitation of device driver > model before. And that maybe now was the time to fix that or at > least sort out how to handle

compositing broken in -next (idr bug)

Hello, Jiri. On Tue, Feb 12, 2013 at 10:55:37PM +0100, Jiri Slaby wrote: > this commit in -next causes my KDE to get stuck while starting. I see > only the splash screen. If I disable effects by alt-shift-f12, it continues. > > I bisected it to this commit: > commit

[Bug 60723] Unable to compile Mesa 9.0.2 for radeon

for the bug. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20130212/700fbfb6/attachment.html>

[Bug 44341] Radeon HD6990M: HDMI audio output works now! Kernel gives new warning

https://bugzilla.kernel.org/show_bug.cgi?id=44341 --- Comment #11 from Alex Deucher 2013-02-12 13:42:26 --- Created an attachment (id=93151) --> (https://bugzilla.kernel.org/attachment.cgi?id=93151) remove overzealous warning This patch should fix the issue. -- Configure bugmail:

[PATCH] drm/radeon: remove overzealous warning in hdmi handling

On Tue, Feb 12, 2013 at 8:40 AM, wrote: > From: Alex Deucher > > hdmi audio works fine. The warning just confuses users. > > fixes: > https://bugzilla.kernel.org/show_bug.cgi?id=44341 > > Signed-off-by: Alex Deucher Reviewed-by: Jerome Glisse > Cc: stable at vger.kernel.org > --- >

[Bug 53391] nouveau: wrong display output order

https://bugzilla.kernel.org/show_bug.cgi?id=53391 --- Comment #10 from Stijn Tintel 2013-02-12 12:54:22 --- Unfortunately with the first patch and #if 0 -> #if 1 nouveau and X start on the 2nd monitor again (with DVI cables). shall I test with vga cables again

[PATCH] drm/fb-helper: improve kerneldoc

Hi Daniel, Thanks for the patch. Just one last small comment. On Tuesday 05 February 2013 22:43:48 Daniel Vetter wrote: > Now that the fbdev helper interface for drivers is trimmed down, > update the kerneldoc for all the remaining exported functions. > > I've tried to beat the DocBook a bit by

[Bug 60723] New: Unable to compile Mesa 9.0.2 for radeon

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

[Bug 49981] On HD6850, Power Profile doesn't change if 2 screen is attached.

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

[PATCH RESEND] drm: fix drm_local_map allocation size

list->map is struct drm_local_map *, not struct drm_map_list *. Signed-off-by: Jani Nikula --- Found this small snippet laying around, I guess it fell between the cracks. --- drivers/gpu/drm/drm_gem.c |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH v2 3/3] modetest: Add a command line parameter to select the driver

On Mon, 11 Feb 2013, Laurent Pinchart wrote: > On Monday 11 February 2013 21:13:45 Laurent Pinchart wrote: >> If the -M parameter is specific, modetest will use the requested device >> name instead of trying its builtin list of device names. >> >> Signed-off-by: Laurent Pinchart >> --- >>

[PATCH] drm: missing idr_preload_end in drm_gem_flink_ioctl

(cc'ing Andrew) Hello, On Sun, Feb 10, 2013 at 03:49:05PM +0400, Artem Savkov wrote: > Added missing idr_preload_end calls in drm_gem_flink_ioctl(). > Without those preemption stays disabled resulting in lots of "scheduling while > atomic" BUGs. > > Introduced in

[PATCH linux-next] drm/radeon: Avoid NULL pointer dereference from atom_index_iio() allocation failure

On Mon, Feb 11, 2013 at 4:34 PM, Tim Gardner wrote: > Smatch anlysis: > > drivers/gpu/drm/radeon/atom.c:1242 atom_index_iio() error: potential null > dereference 'ctx->iio'. (kzalloc returns null) > > Also cleaned up some checks before calls to kfree(). kfree(NULL) is OK. > > Cc: David Airlie

[PATCH] drm/radeon: remove overzealous warning in hdmi handling

From: Alex Deucher hdmi audio works fine. The warning just confuses users. fixes: https://bugzilla.kernel.org/show_bug.cgi?id=44341 Signed-off-by: Alex Deucher Cc: stable at vger.kernel.org --- drivers/gpu/drm/radeon/r600_hdmi.c |1 - 1 files changed, 0

linux-next: Tree for Feb 12 (drm_pci.c)

On 02/11/13 21:09, Stephen Rothwell wrote: > Hi all, > > Changes since 20130211: > when CONFIG_PCI is not enabled (on x86_64): CC [M] drivers/gpu/drm/drm_pci.o drivers/gpu/drm/drm_pci.c: In function 'drm_pcie_get_speed_cap_mask': drivers/gpu/drm/drm_pci.c:485:2: error: implicit declaration

[PATCH 1/5] radeon: Remove redundant NULL check before radeon_i2c_destroy().

radeon_i2c_destroy on a NULL pointer is a no-op. Signed-off-by: Cyril Roelandt --- drivers/gpu/drm/radeon/radeon_i2c.c |6 ++ 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/drivers/gpu/drm/radeon/radeon_i2c.c b/drivers/gpu/drm/radeon/radeon_i2c.c index fc60b74..850df44

[Bug 44341] Radeon HD6990M: HDMI audio output works now! Kernel gives new warning

https://bugzilla.kernel.org/show_bug.cgi?id=44341 Christopher Fr?mmel changed: What|Removed |Added Kernel Version|3.7.5 |3.7.7 --- Comment #10 from

[PATCH 13/16] drm/fb-helper: streamline drm_fb_helper_single_fb_probe

On Tue, Feb 12, 2013 at 1:24 AM, Rob Clark wrote: > On Thu, Jan 24, 2013 at 10:20 AM, Daniel Vetter > wrote: >> No need to check whether we've allocated a new fb since we're not >> always doing that. Also, we always need to register the fbdev and add >> it to the panic notifier. > > hmm, how is

[PATCH] drm/fb-helper: fixup set_config semantics

While doing the modeset rework for drm/i915 I've noticed that the fb helper is very liberal with the semantics of the ->set_config interface: - It doesn't bother clearing stale modes (e.g. when unplugging a screen). - It unconditionally sets the fb, even if no mode will be set on a given crtc.

[PATCH] drm/fb-helper: remove unused members of struct drm_fb_helper

Spotted by Rob Clark. Signed-off-by: Daniel Vetter --- include/drm/drm_fb_helper.h |2 -- 1 file changed, 2 deletions(-) diff --git a/include/drm/drm_fb_helper.h b/include/drm/drm_fb_helper.h index a60311c..8ef4c63 100644 --- a/include/drm/drm_fb_helper.h +++ b/include/drm/drm_fb_helper.h

[PATCH] drm/fb-helper: fixup set_config semantics

While doing the modeset rework for drm/i915 I've noticed that the fb helper is very liberal with the semantics of the ->set_config interface: - It doesn't bother clearing stale modes (e.g. when unplugging a screen). - It unconditionally sets the fb, even if no mode will be set on a given crtc.

[Bug 60200] radeon_bo with virtual address referencing mismatch

was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20130212/4754413d/attachment.html>

[PATCH RESEND] drm: fix drm_local_map allocation size

list-map is struct drm_local_map *, not struct drm_map_list *. Signed-off-by: Jani Nikula jani.nik...@intel.com --- Found this small snippet laying around, I guess it fell between the cracks. --- drivers/gpu/drm/drm_gem.c |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

Re: [git pull] drm nouveau fixes.

just 3 nouveau fixes, all user visible issues, I have one radeon regression fix I'm hoping to send tomorrow once I'm happy with it. Okay I've added the radeon regression fix on top as well The following changes since commit ff7c60c580d9722f820d85c9c58ca55ecc1ee7c4: drm/ttm: fix fence

Re: [PATCH] drm/fb-helper: improve kerneldoc

Hi Daniel, Thanks for the patch. Just one last small comment. On Tuesday 05 February 2013 22:43:48 Daniel Vetter wrote: Now that the fbdev helper interface for drivers is trimmed down, update the kerneldoc for all the remaining exported functions. I've tried to beat the DocBook a bit by

[Bug 49981] On HD6850, Power Profile doesn't change if 2 screen is attached.

https://bugs.freedesktop.org/show_bug.cgi?id=49981 --- Comment #29 from Ludovic Watteaux lucky...@free.fr --- No luck for me, the patch fix multi-head stability apply on linux 3.9-DRM-next-WIP, doesn't change anything on 6750m, boot with linux efi stub. -- You are receiving this mail because:

Re: [PATCH] CHROMIUM: dma-buf: restore args on failure of dma_buf_mmap

+dri-devel ML On 12 February 2013 07:20, s...@google.com wrote: From: John Sheu s...@google.com Callers to dma_buf_mmap expect to fput() the vma struct's vm_file themselves on failure. Not restoring the struct's data on failure causes a double-decrement of the vm_file's refcount.

Re: [PATCH] CHROMIUM: dma-buf: restore args on failure of dma_buf_mmap

+dri-devel ML On 12 February 2013 07:20, s...@google.com wrote: From: John Sheu s...@google.com Callers to dma_buf_mmap expect to fput() the vma struct's vm_file themselves on failure. Not restoring the struct's data on failure causes a double-decrement of the vm_file's refcount.

[PATCH] drm/exynos: fix wrong pointer access at vm close.

From: YoungJun Cho yj44@samsung.com This patch fixes wrong pointer access issue to filp-f_op and filp-private_data. The exynos_drm_gem_mmap_ioctl() changes filp-f_op and filp-private_data temporarily and restore them to use original ones in exynos_drm_gem_mmap_buffer() but there was no lock

[Bug 60723] New: Unable to compile Mesa 9.0.2 for radeon

https://bugs.freedesktop.org/show_bug.cgi?id=60723 Priority: medium Bug ID: 60723 Assignee: dri-devel@lists.freedesktop.org Summary: Unable to compile Mesa 9.0.2 for radeon Severity: normal Classification: Unclassified OS:

[Bug 53391] nouveau: wrong display output order

https://bugzilla.kernel.org/show_bug.cgi?id=53391 --- Comment #10 from Stijn Tintel stijn+b...@linux-ipv6.be 2013-02-12 12:54:22 --- Unfortunately with the first patch and #if 0 - #if 1 nouveau and X start on the 2nd monitor again (with DVI cables). shall I test with vga cables again too ?

Re: [PATCH v2 2/2] drm/exynos: Add device tree based discovery support for G2D

Applied and will go to -next. And please post the document(in Documentation/devicetree/bindings/gpu/) for it later. Thanks, Inki Dae 2013/2/6 Sachin Kamat sachin.ka...@linaro.org: From: Ajay Kumar ajaykumar...@samsung.com This patch adds device tree match table for Exynos G2D controller.

Re: [PATCH v2 2/2] drm/exynos: Add device tree based discovery support for G2D

On 02/12/2013 02:17 PM, Inki Dae wrote: Applied and will go to -next. And please post the document(in Documentation/devicetree/bindings/gpu/) for it later. There is already some old patch applied in the devicetree/next tree:

[PATCH] drm/radeon: remove overzealous warning in hdmi handling

From: Alex Deucher alexander.deuc...@amd.com hdmi audio works fine. The warning just confuses users. fixes: https://bugzilla.kernel.org/show_bug.cgi?id=44341 Signed-off-by: Alex Deucher alexander.deuc...@amd.com Cc: sta...@vger.kernel.org --- drivers/gpu/drm/radeon/r600_hdmi.c |1 - 1

[Bug 44341] Radeon HD6990M: HDMI audio output works now! Kernel gives new warning

https://bugzilla.kernel.org/show_bug.cgi?id=44341 --- Comment #11 from Alex Deucher alexdeuc...@gmail.com 2013-02-12 13:42:26 --- Created an attachment (id=93151) -- (https://bugzilla.kernel.org/attachment.cgi?id=93151) remove overzealous warning This patch should fix the issue. --

[Bug 60723] Unable to compile Mesa 9.0.2 for radeon

https://bugs.freedesktop.org/show_bug.cgi?id=60723 --- Comment #1 from Michel Dänzer mic...@daenzer.net --- Does it work if you add --enable-shared-glapi to the configure arguments? If not, please attach the full output from configure and make. -- You are receiving this mail because: You are

[PATCH v3 0/4] modetest enhancements

Hello, Here's the third version of a small patch set that adds an argument to the modetest command line to specify the driver name instead of using the builtin list of drivers. This is particularly handy during development of new DRM/KMS drivers. This version enables compiler warnings for

[PATCH v3 1/4] modetest: Fix warnings

Enable all standard automake warnings except for -Wpointer-arith (as the test pattern generation code uses void pointer arithmetics) and fix them. Signed-off-by: Laurent Pinchart laurent.pinch...@ideasonboard.com --- tests/modetest/Makefile.am | 4 +++- tests/modetest/buffers.c | 13

[PATCH v3 2/4] modetest: Remove extern declarations of opt(arg|ind|err|opt)

Those variables are declared in unistd.h, there's no need to redeclare them here. Signed-off-by: Laurent Pinchart laurent.pinch...@ideasonboard.com Reviewed-by: Jani Nikula jani.nik...@intel.com --- tests/modetest/modetest.c | 2 -- 1 file changed, 2 deletions(-) diff --git

[PATCH v3 3/4] modetest: Sort command line arguments

The current mostly random sort order hinders code readability. Sort the options alphabetically in the code, and by group in the help message. Signed-off-by: Laurent Pinchart laurent.pinch...@ideasonboard.com Reviewed-by: Jani Nikula jani.nik...@intel.com --- tests/modetest/modetest.c | 49

[PATCH v3 4/4] modetest: Add a command line parameter to select the driver

If the -M parameter is specific, modetest will use the requested device name instead of trying its builtin list of device names. Signed-off-by: Laurent Pinchart laurent.pinch...@ideasonboard.com Reviewed-by: Jani Nikula jani.nik...@intel.com --- tests/modetest/modetest.c | 41

Re: [PATCH v2 2/2] drm/exynos: Add device tree based discovery support for G2D

2013/2/12 Sylwester Nawrocki s.nawro...@samsung.com: On 02/12/2013 02:17 PM, Inki Dae wrote: Applied and will go to -next. And please post the document(in Documentation/devicetree/bindings/gpu/) for it later. There is already some old patch applied in the devicetree/next tree:

Re: [PATCH linux-next] drm/radeon: Avoid NULL pointer dereference from atom_index_iio() allocation failure

On Mon, Feb 11, 2013 at 4:34 PM, Tim Gardner tim.gard...@canonical.com wrote: Smatch anlysis: drivers/gpu/drm/radeon/atom.c:1242 atom_index_iio() error: potential null dereference 'ctx-iio'. (kzalloc returns null) Also cleaned up some checks before calls to kfree(). kfree(NULL) is OK.

[Bug 60723] Unable to compile Mesa 9.0.2 for radeon

https://bugs.freedesktop.org/show_bug.cgi?id=60723 --- Comment #2 from Vincenzo Abate gogolan...@gmail.com --- Created attachment 74682 -- https://bugs.freedesktop.org/attachment.cgi?id=74682action=edit configure log -- You are receiving this mail because: You are the assignee for the bug.

[Bug 60723] Unable to compile Mesa 9.0.2 for radeon

https://bugs.freedesktop.org/show_bug.cgi?id=60723 --- Comment #3 from Vincenzo Abate gogolan...@gmail.com --- Created attachment 74683 -- https://bugs.freedesktop.org/attachment.cgi?id=74683action=edit make log -- You are receiving this mail because: You are the assignee for the bug.

[Bug 60723] Unable to compile Mesa 9.0.2 for radeon

https://bugs.freedesktop.org/show_bug.cgi?id=60723 --- Comment #4 from Vincenzo Abate gogolan...@gmail.com --- It didn't worked. I attached logs from configure and make as asked... (In reply to comment #1) Does it work if you add --enable-shared-glapi to the configure arguments? If not, please

[Bug 60723] Unable to compile Mesa 9.0.2 for radeon

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

Re: [systemd-devel] Someone working on gui for multiseat?

On 02/11/13 21:30, Lennart Poettering wrote: […] Of course, doing this via the command line is not user-frienldy, but maybe this will one day get fixed and somebody writes a proper UI for it... Regarding 'loginctl attach seat0 sysfs', the only thing really missing is the 'sys' path

Multiple parents in device driver model and Common Display Framework (CDF)

Hi Greg, at FOSDEM we had a session on CDF (Common Display Framework). You can read more details about this in the posts from Laurent Pinchart on dridevel: http://lists.freedesktop.org/archives/dri-devel/2012-November/030888.html

[Bug 60503] [r300g] Unigine Heaven 3.0: all objects are black

https://bugs.freedesktop.org/show_bug.cgi?id=60503 --- Comment #9 from Tom Stellard tstel...@gmail.com --- (In reply to comment #8) Created attachment 74525 [details] RADEON_DEBUG=fp log with patch v2 applied (In reply to comment #7) Created attachment 74520 [details] Fix v2 This

Re: Multiple parents in device driver model and Common Display Framework (CDF)

On 02/12/2013 04:53 PM, Tomi Valkeinen wrote: On 2013-02-12 17:04, Marcus Lorentzon wrote: Now we have some different types of panels which are attached on a combination of busses: a) control:DBI, data:DBI b) control:I2C/SPI, data:I2C/SPI c) control:static setup, data:DPI d) control:I2C/SPI,

[Bug 60503] [r300g] Unigine Heaven 3.0: all objects are black

https://bugs.freedesktop.org/show_bug.cgi?id=60503 --- Comment #10 from Pavel Ondračka pavel.ondra...@email.cz --- (In reply to comment #9) (In reply to comment #8) Created attachment 74525 [details] RADEON_DEBUG=fp log with patch v2 applied (In reply to comment #7) Created

Building DRM for i.MX fails with linux-next 20130212

Hi, Building imx_v6_v7_defconfig on linux-next 20130212 gives me the following build error: CC drivers/gpu/drm/drm_pci.o drivers/gpu/drm/drm_pci.c: In function ‘drm_pcie_get_speed_cap_mask’: drivers/gpu/drm/drm_pci.c:485:2: error: implicit declaration of function

Re: [PATCH] drm/radeon: remove overzealous warning in hdmi handling

On Tue, Feb 12, 2013 at 8:40 AM, alexdeuc...@gmail.com wrote: From: Alex Deucher alexander.deuc...@amd.com hdmi audio works fine. The warning just confuses users. fixes: https://bugzilla.kernel.org/show_bug.cgi?id=44341 Signed-off-by: Alex Deucher alexander.deuc...@amd.com Reviewed-by:

[Bug 60236] corruption of text and bottom of screen in xonotic menus since 325422c49449acdd8df1eb2ca8ed81f7696c38cc

https://bugs.freedesktop.org/show_bug.cgi?id=60236 Jerome Glisse gli...@freedesktop.org changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 49981] [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -12!

https://bugzilla.kernel.org/show_bug.cgi?id=49981 Jérôme Glisse gli...@freedesktop.org changed: What|Removed |Added Status|NEW |RESOLVED

  1   2   >