All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin PERES <martin.peres@free.fr>
To: dri-devel@lists.sourceforge.net
Subject: Re: [PATCH] drm/radeon: fixes for r6xx/r7xx gfx init
Date: Fri, 19 Feb 2010 12:15:35 +0100	[thread overview]
Message-ID: <4B7E72D7.50904@free.fr> (raw)
In-Reply-To: <a728f9f91002182254w792b6454g240bc2161bbcffad@mail.gmail.com>

Le 19/02/2010 07:54, Alex Deucher a écrit :
> > From e69022ade813cb26d64719d7a402459ddfc401b3 Mon Sep 17 00:00:00 2001
> From: Alex Deucher<alexdeucher@gmail.com>
> Date: Fri, 19 Feb 2010 01:51:55 -0500
> Subject: [PATCH] drm/radeon: fixes for r6xx/r7xx gfx init
>
> - RV740 requires a special backend map
> - updated swizzle modes for backend map setup
> - fix programming of a few gfx regs
> - properly handle pipe/backend setup on LE cards
>
> Among other thing this fixes occlusion queries and
> rendering errors on RV740.
>    
It seems to do the trick!

I'm just reactivated the Upload from screen and Download from screen. It 
works great.

However, I still get this in my dmesg:
You have old & broken userspace please consider updating mesa

I'll further my tests and will try to get the chessboard-like screen. 
I'll keep you informed.

Thanks a lot (I've had this problem since september).

PS: I'm using an HD4770 and the radeon-testing branch.

------------------------------------------------------------------------------
Download Intel&#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
--

  reply	other threads:[~2010-02-19 11:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-19  6:54 [PATCH] drm/radeon: fixes for r6xx/r7xx gfx init Alex Deucher
2010-02-19 11:15 ` Martin PERES [this message]
2010-02-19 14:29   ` Jerome Glisse
2010-02-24  6:26     ` Martin PERES
2010-02-19 21:27 ` Alex Deucher

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4B7E72D7.50904@free.fr \
    --to=martin.peres@free.fr \
    --cc=dri-devel@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.