[ CC: to Mark to get the most competent comments on XAA ]
Gerd Knorr wrote:
the indirect buffers aren't flushed often enough. When I move a window
with amiwm, the contents don't move at first. Only when I move it
again do the contents appear in the current place. A quick comparison
I'm going to start getting the 3-5 branch uptodate with current cvs using the
old MesaSrcDir technique. I probably won't commit until Brian releases 4.0
it is merged across, unless anyone would rather I did so sooner. (Doing so
would require people to revert to the MesaSrcDir technique also).
Hello all:
Where are things standing with pcigart support for ATI
Mobility M1 (Mach64)under DRI?
Thanks
Alex DeWolf
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
Jeff, Rik, Others,
Can you please post a description of what the backwards compatibility kernel
code changes are, how they work, what developers are expected to do to keep
them working?
Has this code/technique been ported to the 3.5 branch? Has that been examined
for feasibility?
Keith
On Thu, 20 Sep 2001, Michel Dänzer wrote:
[ CC: to Mark to get the most competent comments on XAA ]
Gerd Knorr wrote:
the indirect buffers aren't flushed often enough. When I move a window
with amiwm, the contents don't move at first. Only when I move it
again do the contents
Hey all,
Sorry this is a little off topic, but I'm thinking of making a mips-based
laptop for my senior design project, and I was considering what video
chipset to use. Does anyone have an opinion on if one of the ATI chips
would be a good choice? Also, does anyone have a guess on my chances of
Mark Vojkovich wrote:
Mark, is there a way to flush DMA buffers after a batch of XAA operations
right now? If not, could it be added easily?
Wrap the BlockHandler and flush there. It gets called before the
X-server goes back to waiting on its file descriptors.
Luckily, the r128
Interesting Concept. The ATI mobility is pretty good, except for the
origional (anything based on mach64). ATI just released the
documentation to Mach64 to a lot of people, so your odds are kinda low
for getting anything else.
MICHAEL M DELANEY wrote:
Hey all,
Sorry this is a little off
On Tue, 18 Sep 2001 11:10:11 -0700 Mark Allan [EMAIL PROTECTED] wrote:
MA They shouldn't have to. But there are users who can. Look at the Utah GLX
MA project - that was necessitated by id software releasing games.
MA
MA Not true. If you knew your history, Dave Schmenk (now at NVIDIA) began
On Thu, Sep 20, 2001 at 10:00:33AM -0600, Keith Whitwell wrote:
I'm going to start getting the 3-5 branch uptodate with current cvs
using the old MesaSrcDir technique. I probably won't commit until
Brian releases 4.0 it is merged across, unless anyone would rather I
did so sooner. (Doing
Keith Whitwell wrote:
Jeff, Rik, Others,
Can you please post a description of what the backwards compatibility kernel
code changes are, how they work, what developers are expected to do to keep
them working?
Here is a quick rundown of how the infrastructure works:
During Xserver startup
11 matches
Mail list logo
