[Bug 25555] No compositing with firegl v5200

2009-12-09 Thread bugzilla-daemon
http://bugs.freedesktop.org/show_bug.cgi?id=2 --- Comment #2 from Antenore Gatta 2009-12-09 23:26:21 PST --- Created an attachment (id=31916) --> (http://bugs.freedesktop.org/attachment.cgi?id=31916) xorg.conf -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email

[Bug 25555] No compositing with firegl v5200

2009-12-09 Thread bugzilla-daemon
http://bugs.freedesktop.org/show_bug.cgi?id=2 --- Comment #3 from Antenore Gatta 2009-12-09 23:26:44 PST --- Created an attachment (id=31917) --> (http://bugs.freedesktop.org/attachment.cgi?id=31917) xrandr log -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=emai

[Bug 25555] No compositing with firegl v5200

2009-12-09 Thread bugzilla-daemon
http://bugs.freedesktop.org/show_bug.cgi?id=2 --- Comment #1 from Antenore Gatta 2009-12-09 23:25:50 PST --- Created an attachment (id=31915) --> (http://bugs.freedesktop.org/attachment.cgi?id=31915) drm logs in dmesg -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?t

[Bug 25555] New: No compositing with firegl v5200

2009-12-09 Thread bugzilla-daemon
http://bugs.freedesktop.org/show_bug.cgi?id=2 Summary: No compositing with firegl v5200 Product: DRI Version: XOrg CVS Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: minor Priority: medium

Re: [PATCH] drm/radeon/kms: Check module arguments to be valid

2009-12-09 Thread Dave Airlie
On Thu, Dec 10, 2009 at 3:35 AM, Jerome Glisse wrote: > This patch add a function which check module argument to be > valid. On invalid argument it prints a warning and setback > the default value. This seems to screw up here and prints radeon :06:00.0: vram limit (0) must be a power of 2 ra

[PATCH 0/2] RFC: Upstreaming the vmwgfx driver

2009-12-09 Thread Jakob Bornecrantz
This patch series add the vmwgfx driver to the kernel tree inside the staging tree. I split the patch in two parts as the svga headers fail checkpatch quite hard. The svga* headers are shared between a lot of different components but I can understand if they get rejected due to thier uglyness. So I

[PATCH] drm/radeon/kms: add dynamic engine reclocking (v2)

2009-12-09 Thread Rafał Miłecki
Thanks Jerome for your patience and help :) I guess this should be signed-off-by-you as well when we finally get final version of patch. -- Rafał 0001-drm-radeon-kms-add-dynamic-engine-reclocking-v2.patch Description: Binary data -

[PATCH] drm/radeon/kms/avivo: fix typo in new_pll module description

2009-12-09 Thread Alex Deucher
>From 9f5eb726668633e95781fc1868f4a83a0e39475f Mon Sep 17 00:00:00 2001 From: Alex Deucher Date: Wed, 9 Dec 2009 19:38:58 -0500 Subject: [PATCH] drm/radeon/kms/avivo: fix typo in new_pll module description Signed-off-by: Alex Deucher --- drivers/gpu/drm/radeon/radeon_drv.c |2 +- 1 files ch

[PATCH] drm/radeon/kms/r600/r700: fallback gracefully on ucode failure

2009-12-09 Thread Alex Deucher
>From 017f07a5e40908ce91e29b01f6411e5e4cadbd98 Mon Sep 17 00:00:00 2001 From: Alex Deucher Date: Wed, 9 Dec 2009 19:31:44 -0500 Subject: [PATCH] drm/radeon/kms/r600/r700: fallback gracefully on ucode failure Sent the wrong patch earlier. Signed-off-by: Alex Deucher --- drivers/gpu/drm/radeon/r

[RFC] New AVIVO pll algo

2009-12-09 Thread Alex Deucher
New PLL algo for avivo cards. Hopefully will help with blinking/flashing problems due to bad plls. Depends on the fixed point floor and ceil functions provided in the avivo bandwidth patch from earlier today. Please test and let me know how it goes. I haven't seen any regressions here on my har

[Bug 25505] mplayer -vo gl:yuv=2 fails to compile its fragment program

2009-12-09 Thread bugzilla-daemon
http://bugs.freedesktop.org/show_bug.cgi?id=25505 Radosław Szkodziński changed: What|Removed |Added Status|RESOLVED|VERIFIED --- Comment #3 from R

[Bug 25544] New: KMS/R200: CS section size missmatch start at (r200_state_init.c,tex_emit_mm,703) 5 vs 9

2009-12-09 Thread bugzilla-daemon
http://bugs.freedesktop.org/show_bug.cgi?id=25544 Summary: KMS/R200: CS section size missmatch start at (r200_state_init.c,tex_emit_mm,703) 5 vs 9 Product: Mesa Version: git Platform: x86 (IA32) OS/Version: Linux (All)

Re: [RFC] Radeon simplify GPU address space initialization

2009-12-09 Thread Alex Deucher
On Wed, Dec 9, 2009 at 4:21 PM, Jerome Glisse wrote: > Attached patch try to simplify gpu address space initialization. > By default it will place the VRAM range to cover the PCI aperture > range corresponding to VRAM. > > Patch lack support for AGP and likely need to be twicked for IGP. > I am se

[PATCH] drm/radeon/kms/avivo: fix some bugs in the display bandwidth setup

2009-12-09 Thread Alex Deucher
>From f788a80732f6e8fa90dc5447e52baf719ebe09f7 Mon Sep 17 00:00:00 2001 From: Alex Deucher Date: Wed, 9 Dec 2009 14:40:06 -0500 Subject: [PATCH] drm/radeon/kms/avivo: fix some bugs in the display bandwidth setup Signed-off-by: Alex Deucher --- drivers/gpu/drm/radeon/radeon_fixed.h | 17 ++

Re: 945GM crash

2009-12-09 Thread Svilen
Hi Ian, > I should be able to look at it this weekend. I'll see if I can > reproduce it here. > Did you have a chance to look at the issue? Any success reproducing it? -- Return on Information: Google Enterprise Sear

Re: [RFC] Radeon simplify GPU address space initialization

2009-12-09 Thread Dave Airlie
> Attached patch try to simplify gpu address space initialization. > By default it will place the VRAM range to cover the PCI aperture > range corresponding to VRAM. > > Patch lack support for AGP and likely need to be twicked for IGP. > I am sending it for early review. The most important thing i

[PATCH] drm/radeon/kms: Simplify GPU address space initialization

2009-12-09 Thread Jerome Glisse
This patch simplify the GPU address space initialization, it always try to put VRAM at same address as the CPU PCI aperture for the VRAM. Sadly it seems that the memory controller of radeon got too many bugs to safely put it at others place (especialy on IGP). This patch also kill some duplicated

[RFC] Radeon simplify GPU address space initialization

2009-12-09 Thread Jerome Glisse
Attached patch try to simplify gpu address space initialization. By default it will place the VRAM range to cover the PCI aperture range corresponding to VRAM. Patch lack support for AGP and likely need to be twicked for IGP. I am sending it for early review. The most important thing is mc_vram_si

[PATCH] drm/ttm: Initialize eviction placement in case the driver callback doesn't

2009-12-09 Thread Jerome Glisse
This would allow to catch driver callback error of not properly setting the eviction placement structure. Signed-off-by: Jerome Glisse --- drivers/gpu/drm/ttm/ttm_bo.c |4 1 files changed, 4 insertions(+), 0 deletions(-) diff --git a/drivers/gpu/drm/ttm/ttm_bo.c b/drivers/gpu/drm/ttm/t

[PATCH 3/3] drm/radeon/kms: actualy set the eviction placements we choose

2009-12-09 Thread Jerome Glisse
Stupid bug, somehow copying the eviction placements into the result structure was missing. Signed-off-by: Jerome Glisse --- drivers/gpu/drm/radeon/radeon_ttm.c |1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/drivers/gpu/drm/radeon/radeon_ttm.c b/drivers/gpu/drm/radeon/r

Fix bug introduced by ttm validation rework

2009-12-09 Thread Jerome Glisse
Dave do you prefer me to roll a version 3 of the radeon ttm validation change or do you prefer this one liner patch (so my stupid mistake can show up in git history ;)). Cheers, Jerome -- Return on Information: Google En

[RFC] Add verbose debug information when eviction fails

2009-12-09 Thread Jerome Glisse
This patch series add printing of all informations necessary to understand why getting memory space fails. I have mixed feeling on letting this enabled by default or only enabling it with debug compile flags. Cheers, Jerome

[PATCH 2/3] drm/ttm: Print debug information on memory manager when eviction fails

2009-12-09 Thread Jerome Glisse
This add helper function to print information on eviction placements and memory manager status when eviction fails to allocate memory space. Signed-off-by: Jerome Glisse --- drivers/gpu/drm/ttm/ttm_bo.c | 70 ++ 1 files changed, 57 insertions(+), 13 dele

[PATCH 1/3] drm: Add memory manager debug function

2009-12-09 Thread Jerome Glisse
drm_mm_debug_table will print the memory manager state in table allowing to give a snapshot of the manager at given point in time. Usefull for debugging. Signed-off-by: Jerome Glisse --- drivers/gpu/drm/drm_mm.c | 20 include/drm/drm_mm.h |1 + 2 files changed, 21

[PATCH] drm/radeon/kms: Check module arguments to be valid

2009-12-09 Thread Jerome Glisse
This patch add a function which check module argument to be valid. On invalid argument it prints a warning and setback the default value. Signed-off-by: Jerome Glisse --- drivers/gpu/drm/radeon/radeon_device.c | 66 +-- 1 files changed, 61 insertions(+), 5 deletions

[PATCH] drm/radeon/kms: cleanup structure and module if initialization fails

2009-12-09 Thread Jerome Glisse
This would allow us to properly unload others module like TTM if initialization fails after we initiliazed TTM structure. Signed-off-by: Jerome Glisse --- drivers/gpu/drm/radeon/radeon_kms.c | 42 -- 1 files changed, 20 insertions(+), 22 deletions(-) diff --git

[PATCH 1/2] drm/radeon/kms: Fix NULL ptr dereference

2009-12-09 Thread Jerome Glisse
radeon_atombios_fini might be call while there is not valid atombios structure allocated, thus test for a not null ptr before trying to access this structure. Signed-off-by: Jerome Glisse --- drivers/gpu/drm/radeon/radeon_device.c |6 -- 1 files changed, 4 insertions(+), 2 deletions(-)

Re: [PATCH] drm/radeon/kms: Initialize some value to safe default

2009-12-09 Thread Jerome Glisse
On Wed, Dec 09, 2009 at 02:50:26PM +1000, Dave Airlie wrote: > On Wed, Dec 9, 2009 at 4:29 AM, Jerome Glisse wrote: > > Initialize some value to safe default in case we hit an > > error path which would leads to uninitialized value. > > > > NAK, > > this crashes stuff fairly badly I can see it w

[Bug 25514] Warn once after mesa dc0777d3e3b760d7faa5fb99a189919bde07ca0b

2009-12-09 Thread bugzilla-daemon
http://bugs.freedesktop.org/show_bug.cgi?id=25514 --- Comment #4 from Alex Deucher 2009-12-09 07:58:22 PST --- (In reply to comment #3) > Happens in the master branch as well. Can you please push the patch there. > 7.6 and 7.7 branches get merged into master on a regular basis. -- Confi

[Bug 24322] mesa-7.6 & 7.7 show bogus rendering wih boswars game

2009-12-09 Thread bugzilla-daemon
http://bugs.freedesktop.org/show_bug.cgi?id=24322 Thierry Vignaud changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED

[Bug 25514] Warn once after mesa dc0777d3e3b760d7faa5fb99a189919bde07ca0b

2009-12-09 Thread bugzilla-daemon
http://bugs.freedesktop.org/show_bug.cgi?id=25514 --- Comment #3 from Kevin DeKorte 2009-12-09 05:44:05 PST --- Happens in the master branch as well. Can you please push the patch there. -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving t

Re: [PATCH] drm/ttm: Rework validation & memory space allocation (V3)

2009-12-09 Thread Jerome Glisse
On Wed, Dec 09, 2009 at 11:31:24AM +1000, Ben Skeggs wrote: > On Tue, 2009-12-08 at 15:33 +0100, Jerome Glisse wrote: > > This change allow driver to pass sorted memory placement, > > from most prefered placement to least prefered placement. > > In order to avoid long function prototype a structure

Re: drm/*/kms: how to prepare driver for modesetting

2009-12-09 Thread Jerome Glisse
On Tue, Dec 08, 2009 at 11:36:50PM +0100, Rafał Miłecki wrote: > Jerome Glisse napisał: > > func_set_clock is call after func_compute_clock (if we need to > > upclock gpu to have enough bandwidth for a new video mode) or > > from func_irq_powersave. > > > My solution is correst i said that you ne

[Bug 25514] Warn once after mesa dc0777d3e3b760d7faa5fb99a189919bde07ca0b

2009-12-09 Thread bugzilla-daemon
http://bugs.freedesktop.org/show_bug.cgi?id=25514 Andre Maasikas changed: What|Removed |Added Status|NEW |RESOLVED Resolution|