Since Felix implemented a different heuristics for texture allocation, I
decided to do some measurements on the r100 how fast agp texturing
actually is.
Test conditions are as follows:
Celeron Tualatin [EMAIL PROTECTED] on bx-133 (note this has consequences for AGP
speed, AGP 1x will actually ha
--- Adam K Kirchhoff <[EMAIL PROTECTED]> wrote:
> Jacek Rosik wrote:
>
> >Hi,
> >
> >Dnia 28-01-2005, pi± o godzinie 16:27 +0100, Roland Scheidegger
> >napisa³(a):
> >
> >
> >>Jacek Rosik wrote:
> >>
> >>
> >>>Hi,
> >>>
> >>>I have some questions about r200 depth tiling. Generally I'm als
On Sun, 06 Feb 2005 13:45:47 -0500, Michel Dänzer <[EMAIL PROTECTED]> wrote:
> Does it also happen without either or all of the options in the radeon
> device section?
I just removed the AGPFastWrite and DynamicClocks options. The crashes
still happen though.
First I played some gish. I was able
Jacek Rosik wrote:
Hi,
Dnia 28-01-2005, pią o godzinie 16:27 +0100, Roland Scheidegger
napisał(a):
Jacek Rosik wrote:
Hi,
I have some questions about r200 depth tiling. Generally I'm also
interested in r100 tiling too, but currently i work on r200.
First of all in functions r200_mba_z16|
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=1648
[EMAIL PROTECTED] changed:
What|Removed |Added
-
On Sun, 2005-02-06 at 19:29 +0100, Richard Stellingwerff wrote:
>
> When using OpenGL applications I get frequent X crashes as well as
> complete system locks. They happen totally random.
>
> My hardware is an Ati Radeon Mobility 9200 M9+.
>
> I'm using archlinux 0.7 with X.org 6.8.1 using the
Hi,
When using OpenGL applications I get frequent X crashes as well as
complete system locks. They happen totally random.
My hardware is an Ati Radeon Mobility 9200 M9+.
I'm using archlinux 0.7 with X.org 6.8.1 using the "radeon" driver. It
might be a configuration error on my part, so my xorg.
On Sun, 2005-02-06 at 19:32 +0500, Dimitry Naldayev wrote:
> Michel DÃnzer <[EMAIL PROTECTED]> writes:
>
> > FWIW, the infamous radeon DRI reinit patch is at
> > http://penguinppc.org/~daenzer/DRI/radeon-reinit.diff
> >
> look like it is realy not best way do things right...
>
> so couple of ques
On Sun, 06 Feb 2005 11:52:54 -0500, Adam K Kirchhoff <[EMAIL PROTECTED]> wrote:
>
> At one point someone posted to the dri-devel list an idea on how to
> overcome the 2048x2048 limitation on 3D rendering (for r200
> hardware)... I'm curious if it could be explained again and if anyone
> has alrea
On Sun, 06 Feb 2005 17:35:31 +0100, Felix Kühling <[EMAIL PROTECTED]> wrote:
> Am Sonntag, den 06.02.2005, 19:19 +0500 schrieb Dimitry Naldayev:
> > What about XvMC on savage MX chip?
> > as I remember, the driver from S3 had support for XvMC, and what current
> > status of the code?
>
> It never
At one point someone posted to the dri-devel list an idea on how to
overcome the 2048x2048 limitation on 3D rendering (for r200
hardware)... I'm curious if it could be explained again and if anyone
has already begun work on this?
Adam
---
Thi
> Lessons 1 through 12 work...
You see correct texture ? (like nehe screenshot).
I guess you have done this with lastest cvs checkout.
For warning message about stencil this is normal,
simply means that no one have found the place to
enable it. Same for others functionalities.
> Any of the ones
Am Sonntag, den 06.02.2005, 19:19 +0500 schrieb Dimitry Naldayev:
> What about XvMC on savage MX chip?
> as I remember, the driver from S3 had support for XvMC, and what current
> status of the code?
It never worked. AFAIK only Savage4 and later hardware can do it. So
your Savage MX won't ever su
This is on a Radeon 9800 Pro, on a dual xeon rig.
Lessons 1 through 12 work...
Lesson 13 give me a black screen... I tried using indirect rendering to
see what it should look like, but that gave me an X Error "Bad
Font"... I've even modified the source file to use a font that I know
exists on
Michel Dänzer <[EMAIL PROTECTED]> writes:
[ eatted by /dev/null ]
>> > Is this patch included in CVS?
>>
>> You mean the radeon patch? No. I'm not sure why.
>
> Because it's a hack with a couple of limitations and issues? :)
>
> FWIW, the infamous radeon DRI reinit patch is at
> http://penguinpp
What about XvMC on savage MX chip?
as I remember, the driver from S3 had support for XvMC, and what current
status of the code?
Felix Kühling <[EMAIL PROTECTED]> writes:
> Am Mittwoch, den 02.02.2005, 22:06 +0500 schrieb Dimitry Naldayev:
>> Felix Kühling <[EMAIL PROTECTED]> writes:
>>
>> > Am
Hi,
I got little prob on ppc i get unknown texture format for
nehe lesson 6-7 (haven't tested other but i guess they have
the same prob). I think that somewhere there is a little
big endian issue (always this :)) because with previous
version i have got the texture working well.
I have looked a b
Hello Vladimir,
I've attached a patch which implements the RADOEN_CMD_DMA_DISCARD ioctl from
the radeon/r200 drm. I thought I'd post here before commiting to cvs in
case I've
done something bad.
Without this, eventually r300AllocDmaRegion will get stuck in a loop
continually calling
drmDMA (r30
18 matches
Mail list logo