--- Chris Ison [EMAIL PROTECTED] wrote:
I know you can't give details under NDA, but do the specs for the
r200
show any API for PCI, or has the PCI work on the driver been done by
trial and error.
I'll have to check the docs when I get home. The original PCI GART
work does done for HP for
On Fri, 2003-11-28 at 07:37, Alex Deucher wrote:
I'd say the best supported cards are r200 based radeons (8500 to 9200 cards).
And which one is the fastest?
--
Torgeir Veimo [EMAIL PROTECTED]
---
This SF.net email is sponsored by: SF.net
Torgeir Veimo wrote:
On Fri, 2003-11-28 at 07:37, Alex Deucher wrote:
I'd say the best supported cards are r200 based radeons (8500 to 9200 cards).
And which one is the fastest?
Arguably the Radeon 9100.
Just make sure you don't get some crappy card with a 64-bit memory
interface;
On Fri, 2003-11-28 at 08:49, David Bronaugh wrote:
Torgeir Veimo wrote:
On Fri, 2003-11-28 at 07:37, Alex Deucher wrote:
I'd say the best supported cards are r200 based radeons (8500 to 9200 cards).
And which one is the fastest?
Arguably the Radeon 9100.
Just
hello
unfortunately your mail got lost somehow.
In the meantime I searched bugs.xfree86.org and found bugs #787
and #788 which I think are related to this problem.
I added some info to bug #788.
Later I noticed that his problem was on *BSD, not on Linux.
Maybe you could have a look at it.
On Fri, 2003-11-28 at 22:36, Chris Ison wrote:
I'd say the best supported cards are r200 based radeons (8500 to 9200 cards).
well thats just great, I was hopeing to see something different other
than r200 as I have had nothing but trouble and poor performance with
them with DRI. I have
Today another funny guy decided to tamper with the Wiki (this time by
applying rot13 to a full page). Thankfully this doesn't happen often (I
recall only 3 times so far). Still, since I'm the only one monitoring
I'm afraid I could let attacks like pass though. I'm even more concerned
about minor
Today another funny guy decided to tamper with the Wiki (this time by
applying rot13 to a full page). Thankfully this doesn't happen often (I
recall only 3 times so far). Still, since I'm the only one monitoring
I'm afraid I could let attacks like pass though. I'm even more concerned
about minor
On Fri, 2003-11-28 at 13:00, Andreas Stenglein wrote:
I found another program using scissors that triggers
(maybe) the same bug: lesson24 from nehe.gamedev.net
http://nehe.gamedev.net/data/lessons/lesson.asp?lesson=24
(glut and sdl source)
The difference is: when triggering the bug with q3a
José Fonseca wrote:
Today another funny guy decided to tamper with the Wiki (this time by
applying rot13 to a full page). Thankfully this doesn't happen often (I
recall only 3 times so far). Still, since I'm the only one monitoring
I'm afraid I could let attacks like pass though. I'm even more
for several hours, now.
ri-trunk/xc cvs update
cvs [update aborted]: connect to dri.freedesktop.org(131.252.208.82):2401
failed: Connection timed out
dri-trunk/xc ping dri.freedesktop.org
PING dri.freedesktop.org (131.252.208.82) 56(84) bytes of data.
--- dri.freedesktop.org ping statistics ---
Dieter Nützel wrote:
for several hours, now.
ri-trunk/xc cvs update
cvs [update aborted]: connect to dri.freedesktop.org(131.252.208.82):2401
failed: Connection timed out
dri-trunk/xc ping dri.freedesktop.org
PING dri.freedesktop.org (131.252.208.82) 56(84) bytes of data.
Seems down from here
Which patch should I test?
VTK demos are slower.
Haven't ipers et. al (MesaDemos, Q3A etc.) at the moment 'cause my whole
system was over the Jordan.
Greetings,
Dieter
---
This SF.net email is sponsored by: SF.net Giveback Program.
./PipelineParallelism
./ParallelIso
./ParallelIsoTest
etc.
Do not show _any_ colors.
Only LIBGL_ALWAYS_INDIRECT works.
Some weeks ago, R200_NO_TCL worked.
Any hints?
-Dieter
---
This SF.net email is sponsored by: SF.net Giveback Program.
Dieter Nützel wrote:
./PipelineParallelism
./ParallelIso
./ParallelIsoTest
etc.
Do not show _any_ colors.
Only LIBGL_ALWAYS_INDIRECT works.
Some weeks ago, R200_NO_TCL worked.
Any hints?
In general, these sorts of regressions are much easier to fix if they can be
tracked down to a specific change
Am 2003.11.28 16:15:55 +0100 schrieb(en) Michel Dänzer:
On Fri, 2003-11-28 at 13:00, Andreas Stenglein wrote:
I found another program using scissors that triggers
(maybe) the same bug: lesson24 from nehe.gamedev.net
http://nehe.gamedev.net/data/lessons/lesson.asp?lesson=24
(glut and
On Fri, 2003-11-28 at 18:44, Keith Whitwell wrote:
Dieter Ntzel wrote:
for several hours, now.
ri-trunk/xc cvs update
cvs [update aborted]: connect to dri.freedesktop.org(131.252.208.82):2401
failed: Connection timed out
dri-trunk/xc ping dri.freedesktop.org
PING
When I bring X up dual headed (two cards, not one card two heads) on my system
the secondary adapter needs to be initialized. Where does this happen in the code?
=
Jon Smirl
[EMAIL PROTECTED]
__
Do you Yahoo!?
Free Pop-Up Blocker - Get it now
On Fri, 28 Nov 2003 18:58:46 +0100
Dieter Nützel [EMAIL PROTECTED] wrote:
./PipelineParallelism
./ParallelIso
./ParallelIsoTest
etc.
Do not show _any_ colors.
Only LIBGL_ALWAYS_INDIRECT works.
Some weeks ago, R200_NO_TCL worked.
With recent drivers either use the configuration file or
On Fri, 2003-11-28 at 00:35, Dmitri Katchalov wrote:
Quoting Michel Dnzer [EMAIL PROTECTED]:
On Thu, 2003-11-27 at 15:47, Dmitri Katchalov wrote:
I've made this quick and dirty patch for Radeon driver only.
I understand that it is not perfect as it has to be copied
into every
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter your comments there.
http://bugs.xfree86.org/show_bug.cgi?id=271
[EMAIL PROTECTED] changed:
What|Removed |Added
the 2048 limitation of the scissor registers can be worked around.
check the dri-devel archives for messages with 2048 in the subject.
basically what we need to do is look at the cliprects in the client
driver and everytime they are a multiple of 2048 divide into a zone.
then when you are
22 matches
Mail list logo
