dri-devel September 2012

dri-devel@lists.freedesktop.org

134 participants
706 discussions

[Bug 42490] NUTMEG DP to VGA bridge not working
by bugzilla-daemon＠freedesktop.org 07 Sep '12

07 Sep '12

https://bugs.freedesktop.org/show_bug.cgi?id=42490 diego.abelenda(a)gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #66817|0 |1 is obsolete| | --- Comment #36 from diego.abelenda(a)gmail.com 2012-09-07 21:11:53 UTC --- Created attachment 66819 --> https://bugs.freedesktop.org/attachment.cgi?id=66819 dmesg booting with 2 monitors plugged patch applyed on top of drm-fixes-3.6 drm.debug=4 Sorry... I appended the new log to the last one instead of overwriting it... Now there is only the new dmesg information. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 0

[Bug 42490] NUTMEG DP to VGA bridge not working
by bugzilla-daemon＠freedesktop.org 07 Sep '12

07 Sep '12

https://bugs.freedesktop.org/show_bug.cgi?id=42490 diego.abelenda(a)gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #66817|application/octet-stream |text/plain mime type| | --- Comment #35 from diego.abelenda(a)gmail.com 2012-09-07 21:08:26 UTC --- Comment on attachment 66817 --> https://bugs.freedesktop.org/attachment.cgi?id=66817 dmesg booting with 2 monitors plugged patch applyed on top of drm-fixes-3.6 drm.debug=4 Sorry wrong auto-detect of the type... -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 0

[Bug 42490] NUTMEG DP to VGA bridge not working
by bugzilla-daemon＠freedesktop.org 07 Sep '12

07 Sep '12

https://bugs.freedesktop.org/show_bug.cgi?id=42490 --- Comment #34 from diego.abelenda(a)gmail.com 2012-09-07 21:07:16 UTC --- Created attachment 66817 --> https://bugs.freedesktop.org/attachment.cgi?id=66817 dmesg booting with 2 monitors plugged patch applyed on top of drm-fixes-3.6 drm.debug=4 With the additional patch, I get the DVI screen displaying things when both a plugged-in but the VGA one now says there is no signal (instead of staying black). So the behavior is somewhat similar to the vanilla kernel in that regard. Booting with the VGA unplugged and plugging it later gives the same behavior as without that patch (i.e. better than the vanilla kernel). Attached is the dmesg | grep -e drm -e radeon when the 2 screens are plugged and the VGA says no signal. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 0

[Bug 42490] NUTMEG DP to VGA bridge not working
by bugzilla-daemon＠freedesktop.org 07 Sep '12

07 Sep '12

https://bugs.freedesktop.org/show_bug.cgi?id=42490 --- Comment #33 from Alex Deucher <agd5f(a)yahoo.com> 2012-09-07 19:35:20 UTC --- You might try this patch on top of my 3.6 fixees tree: http://cgit.freedesktop.org/~agd5f/linux/commit/?h=drm-next-3.7-wip&id=46b4… -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 0

[Bug 42490] NUTMEG DP to VGA bridge not working
by bugzilla-daemon＠freedesktop.org 07 Sep '12

07 Sep '12

https://bugs.freedesktop.org/show_bug.cgi?id=42490 --- Comment #32 from diego.abelenda(a)gmail.com 2012-09-07 19:19:10 UTC --- Created attachment 66808 --> https://bugs.freedesktop.org/attachment.cgi?id=66808 dmesg booting with 2 monitors plugged drm.debug=4 This drm-fixes-3.6 branch just gives me two black screens when I have them both plugged during the boot. And when X starts I get a 100% processor usage from the X process and nothing displayed. The Xorg.0.log shows nothing out of the ordinary. But I think there is something really wrong because my X server never starts accepting connection from my login manager. When I boot with only the DVI screen plugged, no problem it boots fine. After having booted with only the DVI plugging the VGA one works just like before. When X puts my screens into DPMS off and I try to wake them up, the VGA goes back on correctly with this branch whereas it didn't with vanilla kernel. So there are some good points and some bad points. Attached is dmesg | grep -e drm -e radeon when both screens are connected, after X is "started". -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 0

[Bug 53490] New: [bisected] bump map corruption from kernel 3.5
by bugzilla-daemon＠freedesktop.org 07 Sep '12

07 Sep '12

https://bugs.freedesktop.org/show_bug.cgi?id=53490 Bug #: 53490 Summary: [bisected] bump map corruption from kernel 3.5 Classification: Unclassified Product: Mesa Version: 7.11 Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/r600 AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: joeri(a)capens.net Created attachment 65540 --> https://bugs.freedesktop.org/attachment.cgi?id=65540 Portal 2 screenshot - good After updating my Linux kernel to 3.5.0 I'm seeing bump map corruption in Portal 2. See attachments. I bisected it down to commit 416a2bd274566a6f607a271f524b2dc0b84d9106 - drm/radeon: fixup tiling group size and backendmap on r6xx-r9xx (v4) My GPU is a Radeon HD 5670 (Evergreen, Redwood) and I'm using Gallium (for R600) on Gentoo Linux AMD64. If I disable bump mapping in Portal 2 (command "mat_bumpmap 0") the corruption goes away, but obviously the walls and objects appear flatter. Mesa, libdrm, xf86-video-ati or Wine versions don't seem to matter. I tested some combinations of Mesa 7.11.2 and 8.0.4, libdrm 2.4.27, 2.4.33 and 2.4.38, xf86-video-ati 6.14.4 and 6.14.6, Wine 1.5.9 and 1.5.10. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 14

[PATCH] drm/exynos: remove DRM_FORMAT_NV12M from plane module
by Inki Dae 07 Sep '12

07 Sep '12

this patch removes DRM_FORMAT_NV12M from plane module because this format is same as DRM_FORMAT_NV12. DRM_FORMAT_NV12M will be identified by mode_cmd->handles and mode_cmd->offsets fields internally. Signed-off-by: Inki Dae <inki.dae(a)samsung.com> Signed-off-by: Kyungmin.park <kyungmin.park(a)samsung.com> --- drivers/gpu/drm/exynos/exynos_drm_plane.c | 1 - 1 files changed, 0 insertions(+), 1 deletions(-) diff --git a/drivers/gpu/drm/exynos/exynos_drm_plane.c b/drivers/gpu/drm/exynos/exynos_drm_plane.c index b89829e..e1f94b7 100644 --- a/drivers/gpu/drm/exynos/exynos_drm_plane.c +++ b/drivers/gpu/drm/exynos/exynos_drm_plane.c @@ -29,7 +29,6 @@ static const uint32_t formats[] = { DRM_FORMAT_XRGB8888, DRM_FORMAT_ARGB8888, DRM_FORMAT_NV12, - DRM_FORMAT_NV12M, DRM_FORMAT_NV12MT, }; -- 1.7.4.1

1 0

[PATCH V5 0/2] video: drm: Add Device tree support to DRM-FIMD
by Leela Krishna Amudala 07 Sep '12

07 Sep '12

This patch set adds device tree support for DRM-FIMD for Samsung's Exynos5250. It includes parsing platform data from dts file. Also, adds the driver data for exynos4 and exynos5 devices. This patchset is based and tested on top of v3.6-rc4 on smdk5250 board Also depends on below patchset http://lists.freedesktop.org/archives/dri-devel/2012-August/026076.html Changes since V4: - Changed the compatible string from "samsung,exynos4-fb" to "samsung,exynos4-fimd". Changes since V3: - Removed the fimd version from driver data and using timing base address instead - Removed the drm_ prefixes to the structures and fucntions Changes since V2: - Added driver data to exynos5-drm-fimd as per Marek Szyprowski suggestion Changes since V1: - Corrected typo errors and changed compatibility string Leela Krishna Amudala (2): drm/exynos: add platform_device_id table and driver data for drm fimd video: drm: exynos: Add device tree support Documentation/devicetree/bindings/fb/drm-fimd.txt | 80 ++++++++++++ drivers/gpu/drm/exynos/exynos_drm_fimd.c | 138 ++++++++++++++++++++- 2 files changed, 212 insertions(+), 6 deletions(-) create mode 100644 Documentation/devicetree/bindings/fb/drm-fimd.txt

2 3

[PATCH] drm/exynos: fix double call of drm_prime_(init/destroy)_file_private
by Mandeep Singh Baines 07 Sep '12

07 Sep '12

The double invocations are incorrect but seem to be safe so I don't think this will fix any bugs. Before: [ 7.639366] drm_prime_init_file ee3675d0 [ 7.639377] drm_prime_init_file ee3675d0 [ 7.639507] drm_prime_destroy_file ee3675d0 [ 7.639518] drm_prime_destroy_file ee3675d0 [ 7.639802] drm_prime_init_file ee372390 [ 7.639810] drm_prime_init_file ee372390 [ 8.473316] drm_prime_init_file ee356390 [ 8.473331] drm_prime_init_file ee356390 After: [ 6.363842] drm_prime_init_file edc2e5d0 [ 6.363994] drm_prime_destroy_file edc2e5d0 [ 6.364260] drm_prime_init_file edc2e750 [ 8.004837] drm_prime_init_file ee36ded0 Signed-off-by: Mandeep Singh Baines <msb(a)chromium.org> CC: Stéphane Marchesin <marcheu(a)chromium.org> CC: Pawel Osciak <posciak(a)google.com> CC: Inki Dae <inki.dae(a)samsung.com> CC: Joonyoung Shim <jy0922.shim(a)samsung.com> CC: Seung-Woo Kim <sw0312.kim(a)samsung.com> CC: Kyungmin Park <kyungmin.park(a)samsung.com> CC: David Airlie <airlied(a)linux.ie> CC: dri-devel(a)lists.freedesktop.org --- drivers/gpu/drm/exynos/exynos_drm_drv.c | 2 -- 1 files changed, 0 insertions(+), 2 deletions(-) diff --git a/drivers/gpu/drm/exynos/exynos_drm_drv.c b/drivers/gpu/drm/exynos/exynos_drm_drv.c index ebacec6..a27b8ff 100644 --- a/drivers/gpu/drm/exynos/exynos_drm_drv.c +++ b/drivers/gpu/drm/exynos/exynos_drm_drv.c @@ -160,7 +160,6 @@ static int exynos_drm_open(struct drm_device *dev, struct drm_file *file) if (!file_priv) return -ENOMEM; - drm_prime_init_file_private(&file->prime); file->driver_priv = file_priv; return exynos_drm_subdrv_open(dev, file); @@ -184,7 +183,6 @@ static void exynos_drm_preclose(struct drm_device *dev, e->base.destroy(&e->base); } } - drm_prime_destroy_file_private(&file->prime); spin_unlock_irqrestore(&dev->event_lock, flags); exynos_drm_subdrv_close(dev, file); -- 1.7.7.3

5 6

[Bug 54527] New: Crash, kernel BUG ttm/ttm_bo.c:1659!, when running gnibbles
by bugzilla-daemon＠freedesktop.org 06 Sep '12

06 Sep '12

https://bugs.freedesktop.org/show_bug.cgi?id=54527 Bug #: 54527 Summary: Crash, kernel BUG ttm/ttm_bo.c:1659!, when running gnibbles Classification: Unclassified Product: DRI Version: XOrg CVS Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: DRM/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: BryanQuigley(a)Ubuntu.com Created attachment 66652 --> https://bugs.freedesktop.org/attachment.cgi?id=66652 kern log cutout System completely crashes to panic screen when attempting to play gnibbles. Usually at the end of the first level. Steps to reproduce: 1. Set options, Speed: Finger-twitching good, Human players 1, AI Players 5 2. Game -> New Game 3. Wait for about 30 seconds till crash I have yet to be able to recreate the crash on a 3.2 kernel (although it eventually fails to continue playing). The crash is easily reproduced on 3.5 (from Ubuntu's xorg-edgers). -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 4

← Newer
1
...
62
63
64
65
66
67
68
...
71
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel September 2012