linux-alpha.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Oliver Falk <oliver@linux-kernel.at>
To: Michael Cree <mcree@orcon.net.nz>
Cc: Matt Turner <mattst88@gmail.com>,
	Ivan Kokshaysky <ink@jurassic.park.msu.ru>,
	linux-alpha@vger.kernel.org, klausman@schwarzvogel.de,
	Jay Estabrook <Jay.Estabrook@hp.com>
Subject: Re: Need help fixing DRM locking on Alpha
Date: Mon, 16 Feb 2009 23:19:18 +0100	[thread overview]
Message-ID: <4999E666.4080309@linux-kernel.at> (raw)
In-Reply-To: <611416E1-0C62-40A1-9176-31AE4961495E@orcon.net.nz>

Michael Cree schrieb:
> On 13/02/2009, at 11:15 AM, Matt Turner wrote:
>> It would be great to get others to test as well. To do so,
>>
>> 1) patch libdrm using this patch.
>> 2) rebuild libdrm, and at least mesa-7.2, xorg-server-1.5.3
>> 3) patch your kernel (-29_rc series preferably) with patch in
>> http://bugzilla.kernel.org/show_bug.cgi?id=10893
>> 4) startx
> 
> Done. Applied the kernel patch and the DRM patch and installed mesa 7.3 
> and xserver 1.5.3.
> 
> Had the xserver up and going with gnome desktop on my ev67 alpha.  Seems 
> to be working fine.
> 
> Nice to see glxinfo return lots of info, and glxgears actually run 
> without locking up.  But I only got 200 whatevers per second with 
> glxgears.  I recall that it use to do 400.  Makes me wonder if I am 
> really getting hardware acceleration.  This is with a Radeon 9200 
> (RV280) graphics card.

Well. At least the patch applied and the kernel came up:

[oliver@gosa ~]$ uname -a
Linux gosa.beer.linux-kernel.at 2.6.29-0.28.rc4.git6.1axp.fc10.alpha #1 
Sat Feb 14 08:07:29 CET 2009 alpha alpha alpha GNU/Linux

It's headless, so quite hard to say if drm locking is fixed or not, at 
the moment. But it's informative for Jay, that he can try this kernel 
:-) If he has time...

-of

  reply	other threads:[~2009-02-16 22:19 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-09 21:43 Need help fixing DRM locking on Alpha Matt Turner
2009-02-10 15:43 ` Ivan Kokshaysky
2009-02-10 23:18   ` Matt Turner
2009-02-11 15:48     ` Ivan Kokshaysky
     [not found]       ` <b4198de60902111401x62c6eea0u8a0d02d12383ec@mail.gmail.com>
2009-02-11 22:13         ` Fwd: " Matt Turner
     [not found]         ` <b4198de60902111412o79479f6av7740552f5b0e9dc8@mail.gmail.com>
2009-02-11 22:13           ` Matt Turner
2009-02-12 22:15       ` Matt Turner
2009-02-16 20:37         ` Michael Cree
2009-02-16 22:19           ` Oliver Falk [this message]
2009-02-11 21:29     ` Michael Cree
2009-02-12  7:31       ` Oliver Falk
2009-02-12  7:43         ` Michael Cree

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=4999E666.4080309@linux-kernel.at \
    --to=oliver@linux-kernel.at \
    --cc=Jay.Estabrook@hp.com \
    --cc=ink@jurassic.park.msu.ru \
    --cc=klausman@schwarzvogel.de \
    --cc=linux-alpha@vger.kernel.org \
    --cc=mattst88@gmail.com \
    --cc=mcree@orcon.net.nz \
    /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;
as well as URLs for NNTP newsgroup(s).