Vladimir Dergachev wrote:
If so, this would suck majorly, especially if there is no
temperature sensor to tell how loaded the card is.
best
Vladimir Dergachev
Well, it seems unlikely that it was/is temperature related (my most
recent test
BTW, i have added some code to do idx buffers in r300_driver. Should i
commit this code or do you want to figure out this first?
Ill post in more details of my findings about idx buffers in case
someone
wants to take a look.
Hi Aapo,
I had take a look at the elt code - great !
On Wed, 16 Feb 2005, Aapo Tahkola wrote:
On Tue, 15 Feb 2005, Adam K Kirchhoff wrote:
I updated to the latest r300 code in cvs tonight in an effort to do
some
testing and noticed an immediate regression. glxgears locked up
almost
immediately, and neverputt locked up within a few minutes.
I
Vladimir Dergachev wrote:
On Wed, 16 Feb 2005, Aapo Tahkola wrote:
On Tue, 15 Feb 2005, Adam K Kirchhoff wrote:
I updated to the latest r300 code in cvs tonight in an effort to do
some
testing and noticed an immediate regression. glxgears locked up
almost
immediately, and neverputt locked up
If so, this would suck majorly, especially if there is no temperature
sensor to tell how loaded the card is.
best
Vladimir Dergachev
Well, it seems unlikely that it was/is temperature related (my most recent
test didn't lock up, so something
I updated to the latest r300 code in cvs tonight in an effort to do some
testing and noticed an immediate regression. glxgears locked up almost
immediately, and neverputt locked up within a few minutes.
I wanted to test each change, step-by-step, from jump_and_click to
today but,
On Tue, 15 Feb 2005, Adam K Kirchhoff wrote:
I updated to the latest r300 code in cvs tonight in an effort to do some
testing and noticed an immediate regression. glxgears locked up almost
immediately, and neverputt locked up within a few minutes.
Even with immediate mode rendering ?
