From: Patrick McFarland <diablod3@gmail.com>
To: unlisted-recipients:; (no To-header on input)
Cc: Lee Revell <rlrevell@joe-job.com>,
dri-devel@lists.sf.net,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [BUG] r200 dri driver deadlocks
Date: Tue, 7 Sep 2004 05:07:45 -0400 [thread overview]
Message-ID: <d577e5690409070207448961a4@mail.gmail.com> (raw)
In-Reply-To: <1094494329.31464.187.camel@admin.tel.thor.asgaard.local>
On Mon, 06 Sep 2004 14:12:08 -0400, Michel Dänzer <michel@daenzer.net> wrote:
> You can test the r200_dri.so from the snapshot with the DRM from the
> kernel...
And drum roll please...
The dri cvs snapshot works fine on both it's own kernel module, and
the one that comes
with 2.6.8.1. So now what? (And does this mean it isn't a kernel bug?)
<rant>
Also, what happens to r200 users who happen to use Debian? Using dri
cvs snapshots
obviously isn't an option for everyone (though I don't mind at all)
and upgrading to Xorg
(when Xorg gets this fix if it doesn't already) is even less of an
option. The official word
from the Debian X Strike Force is not to switch to Xorg until debriX
(modular X) gets
somewhere.
</rant>
--
Patrick "Diablo-D3" McFarland || diablod3@gmail.com
"Computer games don't affect kids; I mean if Pac-Man affected us as kids, we'd
all be running around in darkened rooms, munching magic pills and listening to
repetitive electronic music." -- Kristian Wilson, Nintendo, Inc, 1989
next prev parent reply other threads:[~2004-09-07 9:07 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-04 9:16 [BUG] r200 dri driver deadlocks Patrick McFarland
2004-09-04 10:59 ` Dave Airlie
2004-09-05 8:40 ` Patrick McFarland
2004-09-04 18:14 ` Michel Dänzer
2004-09-04 20:36 ` Patrick McFarland
2004-09-05 6:34 ` Michel Dänzer
2004-09-05 8:22 ` Patrick McFarland
2004-09-05 17:40 ` Michel Dänzer
2004-09-05 20:18 ` Patrick McFarland
2004-09-05 20:25 ` Michel Dänzer
2004-09-05 21:47 ` Patrick McFarland
2004-09-06 0:14 ` Lee Revell
2004-09-06 10:51 ` Felix Kühling
2004-09-07 6:34 ` Mike Mestnik
2004-09-07 6:54 ` Dave Airlie
2004-09-07 7:06 ` Mike Mestnik
2004-09-07 9:40 ` Roland Scheidegger
2004-09-06 11:01 ` Patrick McFarland
2004-09-06 18:12 ` Michel Dänzer
2004-09-07 9:07 ` Patrick McFarland [this message]
2004-09-07 9:09 ` Patrick McFarland
2004-09-07 9:41 ` Alan Cox
2004-09-09 4:24 ` Alexander E. Patrakov
[not found] <21d7e997040907013071ebb60d@mail.gmail.com>
2004-09-08 4:13 ` Mike Mestnik
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=d577e5690409070207448961a4@mail.gmail.com \
--to=diablod3@gmail.com \
--cc=dri-devel@lists.sf.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rlrevell@joe-job.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox