ALT Linux Sisyphus discussions
 help / color / mirror / Atom feed
From: Michael Shigorin <mike@osdn.org.ua>
To: sisyphus@altlinux.ru
Subject: [sisyphus] Re: Кто-нибудь пробовал r300.sf.net ?
Date: Tue, 24 May 2005 19:36:01 +0300
Message-ID: <20050524163601.GG15617@osdn.org.ua> (raw)
In-Reply-To: <200505241927.16301.ru_classic@gts.lg.ua>

[-- Attachment #1: Type: text/plain, Size: 326 bytes --]

On Tue, May 24, 2005 at 07:27:16PM +0300, Alexander Kuprin wrote:
> Кто-нибудь пробовал драйвер, который предлагается на
> r300.sf.net ? Судя по последним сообщениям драйвера научились
> работать и с ATI Radeon 9600.

Attached.

-- 
 ---- WBR, Michael Shigorin <mike@altlinux.ru>
  ------ Linux.Kiev http://www.linux.kiev.ua/

[-- Attachment #2: Type: message/rfc822, Size: 4676 bytes --]

From: "Konstantin A. Lepikhov" <lakostis@altlinux.ru>
To: ALT Linux Devel Mailing List <devel@altlinux.ru>
Subject: [devel] [Re: [R300] the_perfect_frag snapshot]
Date: Mon, 23 May 2005 17:18:00 +0400
Message-ID: <20050523131800.GB30595@lks.home>

Hi!

В продолжение темы про R300 - оказывается, DRI версия работает даже на
X800.

----- Forwarded message from Rune Petersen <rune@> -----

Date: Sat, 21 May 2005 15:37:13 +0200
From: Rune Petersen <rune@>
To: dri-devel@
Subject: Re: [R300] the_perfect_frag snapshot
User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
X-Accept-Language: en-us, en

Hi,
Vladimir Dergachev wrote:
>    I tagged yesterday "the_perfect_frag" snapshot of R300 driver.
>
>    The code is in CVS at http://r300.sf.net
>
>    As the name suggests I cannot find visible faults with rendering
>    Quake3 levels. Also, PPRacer shows no artifacts either, at least in
>    the first few levels..
>
>    Known issues/help needed:
>
>         * Radeon 9800 cards are still exhibiting an occasional lockup.
>
>         * It would be interesting to know whether the driver works
>           with some of the newer cards (like Radeon X800)

I found to do a little testing on my X800:
    * Quake3: no artifacts, nice menu =)
    * Tuxracer: no artifacts
    * UT 2003: it starts with _many_ artifacts, almost playable in a
      funny kind of way: I can see items and players, what more do
      you need? =)
    * UT 2004: its starts with _many_ artifacts, but locks up in the
      menu. I'll see if I can pin it down.
    * a known issue I have is loosing the z-buffer when resizing
      window -> full screen. (I can't figure out why this happens).


Rune Petersen


----- End forwarded message -----

-- 
WBR, Konstantin	      chat with ==>ICQ: 109916175
     Lepikhov,	      speak  to ==>JID: lakostis@jabber.org
aka L.A. Kostis       write  to ==>mailto:lakostis@pisem.net.nospam

...The information is like the bank... 			  (c) EC8OR
_______________________________________________
Devel mailing list
Devel@altlinux.ru
https://lists.altlinux.ru/mailman/listinfo/devel

[-- Attachment #3: Type: message/rfc822, Size: 6317 bytes --]

[-- Attachment #3.1.1.1: Type: text/plain, Size: 2359 bytes --]

Hi!

JFYI - текущий статус поддержки DRI для R300. Оказывается, она даже
стабильнее, чем для R200 :)

----- Forwarded message from Nicolai Haehnle <prefect_@> -----

Date: Thu, 19 May 2005 16:07:44 +0200
From: Nicolai Haehnle <prefect_@>
To: Keith Whitwell <keith@>
Cc: Vladimir Dergachev <volodya@>,
	Aapo Tahkola <aet@>,
	Jerome Glisse <j.glisse@>,
	Ben Skeggs <d4rk74m4@>, dri-devel@
Subject: Re: [R300] new snapshot ?
X-Authenticated: #5817363
User-Agent: KMail/1.8
X-Y-GMX-Trusted: 0

On Thursday 19 May 2005 09:20, Keith Whitwell wrote:
> Vladimir Dergachev wrote:
> > 
> > Hi Aapo, Ben, Jerome, Nicolai:
> > 
> >    I recently checked fresh code from CVS and was pleasantly surprised 
> > to see that all Quake3 levels that were broken are now perfect - in fact 
> > I cannot find anything that is amiss !
> > 
> >    Do you think it would be a good idea to tag the current code and make 
> > a snapshot ?

Sure, anytime :)

> So have you guys given any consideration to moving the r300 driver into 
> mesa proper?  CVS access shouldn't be a problem, fwiw...

There are two main points that have stopped me from pushing for the 
inclusion of the driver into Mesa proper:

1. Kernel-level security holes
We should take care of full command-stream verification before moving the 
driver into Mesa CVS. It's easy to say "We can do that later", but if we 
say that it's likely that it won't be done in a long time.

2. DRM binary compatibility
We still don't know the meaning of many of the registers. Some registers are 
labelled "dangerous" which means we might have to do some more checks in 
the kernel to make sure user processes can't do harmful stuff. This means 
that we might have to *remove* some of the cmdbuf commands that exist today 
in the future.

If the others believe moving r300 to Mesa is a good idea, then I'll do some 
auditing to the DRM code. Once I (or somebody else) has done this, I'm okay 
with moving the driver as long as we don't enforce DRM binary compatibility 
yet.

cu,
Nicolai



----- End forwarded message -----

-- 
WBR, Konstantin	      chat with ==>ICQ: 109916175
     Lepikhov,	      speak  to ==>JID: lakostis@jabber.org
aka L.A. Kostis       write  to ==>mailto:lakostis@pisem.net.nospam

...The information is like the bank... 			  (c) EC8OR

[-- Attachment #3.1.1.2: Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #3.1.2: Type: text/plain, Size: 133 bytes --]

_______________________________________________
Devel mailing list
Devel@altlinux.ru
https://lists.altlinux.ru/mailman/listinfo/devel

[-- Attachment #4: Type: message/rfc822, Size: 5589 bytes --]

[-- Attachment #4.1.1.1: Type: text/plain, Size: 913 bytes --]

Hi Alexey!

Monday 23, at 05:42:00 PM you wrote:

> * Konstantin A. Lepikhov <lakostis@> [050523 17:15]:
> > JFYI - текущий статус поддержки DRI для R300. Оказывается, она даже
> > стабильнее, чем для R200 :)
> Ну, shrek@ сказал что ему не на чем тестить, а мне как-то не до
> самосбора...  Может соберёшь в /people/? ;-)
а я есть в /people? :)

собственно собрать не проблема - проблема во времени и разруливании
существующих конфликтов с установкой (для этих модулей нужна Mesa из CVS,
DRI из r300 CVS etc, как они будут жить с существущими xorg без
выкидывания последнего непонятно). Конечно, всегда можно сделать tar.bz2,
но его обычно не ставят ;)

-- 
WBR, Konstantin	      chat with ==>ICQ: 109916175
     Lepikhov,	      speak  to ==>JID: lakostis@jabber.org
aka L.A. Kostis       write  to ==>mailto:lakostis@pisem.net.nospam

...The information is like the bank... 			  (c) EC8OR

[-- Attachment #4.1.1.2: Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #4.1.2: Type: text/plain, Size: 133 bytes --]

_______________________________________________
Devel mailing list
Devel@altlinux.ru
https://lists.altlinux.ru/mailman/listinfo/devel

  reply	other threads:[~2005-05-24 16:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-24 16:27 [sisyphus] " Alexander Kuprin
2005-05-24 16:36 ` Michael Shigorin [this message]
2005-05-25  5:56 ` Alexey I. Froloff
2005-05-25  6:27   ` Alexander Kuprin
2005-05-25  8:22     ` [sisyphus] " Michael Shigorin
2005-05-25 15:18       ` Alexander Kuprin

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=20050524163601.GG15617@osdn.org.ua \
    --to=mike@osdn.org.ua \
    --cc=sisyphus@altlinux.ru \
    /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

ALT Linux Sisyphus discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror http://lore.altlinux.org/sisyphus/0 sisyphus/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 sisyphus sisyphus/ http://lore.altlinux.org/sisyphus \
		sisyphus@altlinux.ru sisyphus@altlinux.org sisyphus@lists.altlinux.org sisyphus@lists.altlinux.ru sisyphus@lists.altlinux.com sisyphus@linuxteam.iplabs.ru sisyphus@list.linux-os.ru
	public-inbox-index sisyphus

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://lore.altlinux.org/org.altlinux.lists.sisyphus


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git