> > driUpdateTextureLRU( (driTextureObject *) t ); /* XXX: should be locked */
> > I've taken this approach as well.. but should it be locked? if so how? is
> > the i830 correct should I try to do something similiar?
>
> Because this function call modifies the global (ie shared memory) LRU, it
> s
> >
> > If I use a lot of textures my program should still run but run slower? it
> > shouldn't show white textures.. which is what it does if I lower the
> > videoram to 16MB, I got this before the texmem change as well if I ran
> > with a low VideoRam setting ..
>
> Yes, it should just run slowe
I recently got from ATI Embedded, an eval kit for the M7 and M9 and these
cards have dual DVI, granted they don't fit in a PC case too well ( one
connector comes out the top of the card :-), but they are only eval boards
for embedded designers..
Dave.
On Mon, 1 Sep 2003, Alex Deucher wrote:
> L
Dave Airlie wrote:
driUpdateTextureLRU( (driTextureObject *) t ); /* XXX: should be locked */
I've taken this approach as well.. but should it be locked? if so how? is
the i830 correct should I try to do something similiar?
Because this function call modifies the global (ie shared memory) LRU, it
s
On Sun, 2003-08-31 at 03:47, Michael Schreckenbauer wrote:
> Am Samstag, 30. August 2003 00:02 schrieb Eric Anholt:
> > My current diff is at:
> > http://people.freebsd.org/~anholt/dri/files/sis-14.diff
> >
> > It's against DRI CVS. Should work fine on Linux/FreeBSD, with or
> > without sisfb. I
On Mon, 2003-09-01 at 20:41, Jouni Tulkki wrote:
>
> I tried enabling AGP Fast Writes and the performance increased. But my system
> also got unstable. After reading about Fast Writes I came to the conclusion
> that it is quite a problematic feature sometimes.
Indeed, that's why it's disabled i
Linus,
Some dell OEM radeon cards offered Dual DVI ports and I believe there
are some other oems (tyan?) that will be offering Dual DVI cards. the
radeon 9000s and newer only have one tdms trandsmitter built in, but an
additional external one can be added on to drive the second DVI port.
for mu
On Sun, 31 Aug 2003 12:35:22 +0200
smitty <[EMAIL PROTECTED]> wrote:
>
> > I updated the configuration design document to reflect the current
> > state of the implementation. The new document is available at
> > http://user.cs.tu-berlin.de/~felixyz/dri/dri_config_design_rev4.txt if
> > anyone is
Linus Torvalds wrote:
The thing is a 3840x2400 pixel monster, and to drive it at reasonable
frequencies you actually need to support a quad DVI setup where it
looks basically like four monitors running at 1920x1200. And from
what I can gather by googling, the outputs need to be synchronized,
so
> Damn, but it's a drool-inducing piece of hardware.
Indeed - Tim has one on his desk and it's virtually impossible to spot
single pixels on it :) Be warned though if you plan to get one, the low
refresh rate can be very annoying.
-- Daniel, Epic Games Inc.
---
Ok, this is pretty off-topic, but I'm wondering what the status is for
open-source support of 3D-capable drivers for such studly monitors as the
IBM T221.
Yes, it's still expensive as hell, but it isn't nearly as bad as it was a
few years ago when it was very limited availability, and cost USD $2
Hello
I tried enabling AGP Fast Writes and the performance increased. But my system
also got unstable. After reading about Fast Writes I came to the conclusion
that it is quite a problematic feature sometimes.
If I understood right, Fast Writes works so that cpu can send data directly to
the g
This is just a friendly reminder that the weekly dri-devel IRC meeting will
be starting in the #dri-devel channel on irc.freenode.net at 2100 UTC (or
5:00PM EDT or 2:00PM PDT, if you prefer).
Time zone conversion available at:
http://www.timezoneconverter.com/cgi-bin/tzc.tzc
Logs of previous IR
On Mon, 2003-09-01 at 16:28, Keith Whitwell wrote:
> > r200_maos_arrays.c:298: emit_vector: Assertion `0' failed.
> > and the spplication died.
> Can you provide me a backtrace from gdb of the crash?
This is part of the backtrace:
#5 0x458e59b2 in __assert_fail () from /lib/libc.so.6
#6 0x4678f
Thomas Emmel wrote:
Hi together,
recently I sended an email to Keith who directed me to this list.
My application (ABAQUS, see below for details) crashes if I use
your r200-dri-module. The particular error is:
r200_maos_arrays.c:298: emit_vector: Assertion `0' failed.
and the spplication died.
Ah,
Hi together,
recently I sended an email to Keith who directed me to this list.
My application (ABAQUS, see below for details) crashes if I use
your r200-dri-module. The particular error is:
r200_maos_arrays.c:298: emit_vector: Assertion `0' failed.
and the spplication died.
Currently I am using th
Alex Deucher wrote:
there is a driver option in your config file to choose how much ram you
want to use for your adapter. I don't remember what it is off hand.
VideoRam 32000
or some other number
Keith
---
This sf.net email is sponsored by:T
the open source radeon Xfree drivers do not support tv out yet. You
might check with the GATOS people (http://gatos.sf.net). it works in
the console because the BIOS is driving the outputs rather than the
driver.
Alex
--- Chris Ison <[EMAIL PROTECTED]> wrote:
> I'm wondering if there is a way t
Dave Airlie wrote:
In i810_dri.h there is a warning..
/* WARNING: Do not change the SAREA structure without changing the kernel
* as well */
for texmem I want to apply the same patch as..
http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/dri/xc/xc/programs/Xserver/hw/xfree86/drivers/i810/i830_dri.h.d
Dave Airlie wrote:
Okay I've gotten around to updating the i810 driver to texmem interface...
http://www.skynet.ie/~airlied/patches/dri/i810_texmem.diff
I've a couple of issues perhaps someone can help with:
1. In texstate.c UpdateTexUnit for most drivers (except i830) the
following appears:
dri
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=314
--- Additional Comments From [EMAIL PROTECTED] 2003-01-09 07:30 ---
Hi,
found some strange thi
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=609
[EMAIL PROTECTED] changed:
What|Removed |Added
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=314
--- Additional Comments From [EMAIL PROTECTED] 2003-01-09 00:06 ---
hardware hp pavilion ze5200
Okay I've gotten around to updating the i810 driver to texmem interface...
http://www.skynet.ie/~airlied/patches/dri/i810_texmem.diff
I've a couple of issues perhaps someone can help with:
1. In texstate.c UpdateTexUnit for most drivers (except i830) the
following appears:
driUpdateTextureLRU(
In i810_dri.h there is a warning..
/* WARNING: Do not change the SAREA structure without changing the kernel
* as well */
for texmem I want to apply the same patch as..
http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/dri/xc/xc/programs/Xserver/hw/xfree86/drivers/i810/i830_dri.h.diff?r1=1.6&r2=1.7
25 matches
Mail list logo
