[PATCH] drm/radeon/kms: fix up gart setup on rs600

2009-12-05 Thread Alex Deucher
>From 7d300a86142d18cba993718c35a1c14be66c318f Mon Sep 17 00:00:00 2001 From: Alex Deucher Date: Sat, 5 Dec 2009 17:55:37 -0500 Subject: [PATCH] drm/radeon/kms: fix up gart setup on rs600 Set up rs600 gart like r600: - set gart system aperture to vram - inside gart system aperture is unmapped* -

Re: [PATCH 2/3] drm/ttm: Rework validation & memory space allocation

2009-12-05 Thread Thomas Hellström
Jerome Glisse wrote: > On Sat, Dec 05, 2009 at 01:14:29PM +0100, Thomas Hellström wrote: > >> Jerome, >> >> I'm just reviewing the API change here. I'll do a more thorough code >> review when the API is agreed upon. >> >> >>> + >>> +/** >>> + * struct ttm_placement >>> + * >>> + * @fpfn:

[Bug 25463] crash with progs/perf/copytex

2009-12-05 Thread bugzilla-daemon
http://bugs.freedesktop.org/show_bug.cgi?id=25463 --- Comment #1 from Pierre Ossman 2009-12-05 12:32:24 PST --- Looking through things, there are two questions that pop up: 1. Should the texture really be marked as complete when there is no data associated with it? Unfortunately mesa core

Re: drm git branches revisited

2009-12-05 Thread Pekka Paalanen
On Wed, 2 Dec 2009 14:10:11 +1000 Dave Airlie wrote: > So I'm going to change the layout of my git branches again, > because my current plan isn't working for me. > > At the moment drm-next is considered the branch to base new work > off and to also for downstream trees to > pull from, this is c

[Bug 25463] New: crash with progs/perf/copytex

2009-12-05 Thread bugzilla-daemon
http://bugs.freedesktop.org/show_bug.cgi?id=25463 Summary: crash with progs/perf/copytex Product: Mesa Version: git Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: D

Re: [PATCH 2/3] drm/ttm: Rework validation & memory space allocation

2009-12-05 Thread Jerome Glisse
On Sat, Dec 05, 2009 at 01:14:29PM +0100, Thomas Hellström wrote: > Jerome, > > I'm just reviewing the API change here. I'll do a more thorough code > review when the API is agreed upon. > > > + > > +/** > > + * struct ttm_placement > > + * > > + * @fpfn: first valid page frame number t

[OOPS] Radeon KMS with 2.6.31.6

2009-12-05 Thread Chris Rankin
Hi, I tripped over this KMS(?) bug this morning. I have a Radeon 9550, and the userspace environment is Fedora 12. The kernel is vanilla 2.6.31.6. Cheers, Chris BUG: unable to handle kernel NULL pointer dereference at 0028 IP: [] ttm_bo_wait+0x45/0x145 [ttm] *pde = Oops: [#1]

[PATCH 1/2] drm/ttm: Have the TTM code return -ERESTARTSYS instead of -ERESTART.

2009-12-05 Thread Thomas Hellstrom
Return -ERESTARTSYS instead of -ERESTART when interrupted by a signal. The -ERESTARTSYS is converted to an -EINTR by the kernel signal layer before returned to user-space. Signed-off-by: Thomas Hellstrom --- drivers/gpu/drm/ttm/ttm_bo.c| 33 + drivers/gpu/dr

[PATCH 0/2 RESEND] Replace TTM -ERESTART returns with -ERESTARTSYS

2009-12-05 Thread Thomas Hellstrom
Resending, since previous patch emails seem to have been blocked by sf. The reason for this change is twofold: 1) -ERESTART is returned to user-space, but that return-code is not available in *BSD, user-space, and we'd like to be able to reuse user-space-code. 2) -ERESTARTSYS is caught by the li

[PATCH 2/2] drm/radeon: Remove tests for -ERESTART from the TTM code.

2009-12-05 Thread Thomas Hellstrom
Also sets affected TTM calls up to not wait interruptible, since that would cause an in-kernel spin until the TTM call succeeds, since the Radeon code does not return to user-space when a signal is received. Modifies interruptible fence waits to return -ERESTARTSYS rather than -EBUSY when interrup

Re: [PATCH 2/3] drm/ttm: Rework validation & memory space allocation

2009-12-05 Thread Thomas Hellström
Thomas Hellström wrote: > Jerome Glisse wrote: > >> This change allow driver to pass memory space preference >> on buffer object placement. Up to 15 differents places >> which should be enought. The placement order is given >> by the memory type encoded on 4bits in 64bits dword. >> First 4bits i

Re: [PATCH] drm: Disable all the possibles output/crtcs before entering KMS mode

2009-12-05 Thread ykzhao
On Sat, 2009-12-05 at 06:22 +0800, Rafał Miłecki wrote: > 2009/12/4 Dave Airlie : > > On Fri, 2009-12-04 at 20:05 +0800, yakui.z...@intel.com wrote: > >> From: Zhao Yakui > >> > >> Disable all the possible outputs/crtcs before entering KMS mode. > > > > We need a bit more info than this for such a

Re: [PATCH] drm: Disable all the possibles output/crtcs before entering KMS mode

2009-12-05 Thread ykzhao
On Sat, 2009-12-05 at 04:40 +0800, Dave Airlie wrote: > On Fri, 2009-12-04 at 20:05 +0800, yakui.z...@intel.com wrote: > > From: Zhao Yakui > > > > Disable all the possible outputs/crtcs before entering KMS mode. > > We need a bit more info than this for such a large change? The BIOS will selec

Re: [PATCH 2/3] drm/ttm: Rework validation & memory space allocation

2009-12-05 Thread Thomas Hellström
Jerome Glisse wrote: > This change allow driver to pass memory space preference > on buffer object placement. Up to 15 differents places > which should be enought. The placement order is given > by the memory type encoded on 4bits in 64bits dword. > First 4bits is the number of memory placement. Ne

Re: [PATCH 1/3] drm: Add search/get functions to get a block in a specific range

2009-12-05 Thread Thomas Hellström
Jerome Glisse wrote: > Signed-off-by: Jerome Glisse > --- > drivers/gpu/drm/drm_mm.c | 88 > ++ > include/drm/drm_mm.h | 34 ++ > 2 files changed, 122 insertions(+), 0 deletions(-) > > diff --git a/drivers/gpu/drm/drm_mm.c b/dri

Radeon use of -ERESTART

2009-12-05 Thread Thomas Hellström
Hi, Jerome, While moving the ttm core code over to return -ERESTARTSYS in the event of it getting interrupted by a signal, I took a look at the use of the old -ERESTART usage in Radeon. It turns out that in radeon_object.c, -ERESTART return values are caught and the ttm call is reissued. That i