On Tue, Sep 18, 2001 at 10:55:02PM -0400, Frank Earl wrote:
On Tuesday 18 September 2001 19:05, Mike A. Harris wrote:
Very much agreed. This is moreso even for standard XFree86
driver development (2D et al.), and porting old 3.3.6 driver to
4.x.
Yes, I would love to see the CyberBlade
I would like to track which regions of the screen have changed. This
would be of use for something like x0rfbserver which allows remote
access to the local x display.
Has anybody looked into something like this? What docs are availible?
It looks like most of the docs are user level or meant
On Wednesday 19 September 2001 04:42, Alan Hourihane wrote:
What's the problem Frank. I don't believe I've ever had a report from you
on problemsor if you have, can you refresh my memory on what these
problems are...(Oh, and which CyberBlade is it ?)
Never filed a report- had too many
On Wednesday 19 September 2001 14:34, Alan Hourihane wrote:
What about setting another Chipset rather than options ?
Tried all the gamut to see if there was any variation- no such luck with at
least my machine. Win98/Me shows it to be an Ai1 chip, which jives with the
info KDS has available
for what it's worth, there is cyberblade documentation
available at this web site:
http://www.creatis.insa-lyon.fr/~bellet/trident/
Alex
---
On Wednesday 19 September 2001 14:34, Alan
Hourihane wrote:
What about setting another Chipset rather than
options ?
Hello!
It's me again :-)
This time I need to utilize DMA to transfer data from videocard into system
memory (i.e the opposite direction), which is the only way to get decent video
grabbing from ATI AIW (for those who don't know AIW is a videocard with
onboard tv-decoder and other stuff). There
I've got the apg texturing patches applied to my checked out dri tree (trunk)
and I was wondering if they've ever been committed to any branch of the dri
cvs tree? I get the odd problem (programs using dri segfaulting at
indeterminate occasions, corrupted textures, out of memory (null heap
