Re: [Dri-devel] New code in mach64-0-0-3-dma-branch: how to approach?

2002-05-05 Thread Leif Delgass
On Fri, 3 May 2002, Felix Kühling wrote: However, when exiting the X server, I get a hard lockup. I haven't found Maybe this is related: whenever the X-server exits I get the following messages at the end of XFree86.1.log: Fatal server error: Caught signal 11. Server aborting So

Re: [Dri-devel] New code in mach64-0-0-3-dma-branch: how to approach?

2002-05-03 Thread José Fonseca
On 2002.05.01 19:41 Frank C. Earl wrote: On Wednesday 01 May 2002 03:58 am, JosX Fonseca wrote: Frank just commited a set of changes to the mach64-0-0-3-dma-branch. Is in own words: Most of the first cut of the DMA code. It's got most of the dispatch architecture in place

Re: [Dri-devel] New code in mach64-0-0-3-dma-branch: how to approach?

2002-05-03 Thread Leif Delgass
On Wed, 1 May 2002, José Fonseca wrote: ... or we bring Frank's changes to mach64-0-0-4-branch. Personally I'm more in favor of the later, since it will avoid redundant work of merging back and forward, and will also enable the PowerPC architecture to participate in testing.

Re: [Dri-devel] New code in mach64-0-0-3-dma-branch: how to approach?

2002-05-03 Thread Felix Kühling
On Fri, 3 May 2002 04:01:42 -0400 (EDT) Leif Delgass [EMAIL PROTECTED] wrote: I wanted to give you an update on my progress since I sent the first patch of my merge. None of this is checked in yet, btw. I added the necessary initialization to atidri.c, based on the glint/gamma driver, and

[Dri-devel] New code in mach64-0-0-3-dma-branch: how to approach?

2002-05-01 Thread José Fonseca
Frank just commited a set of changes to the mach64-0-0-3-dma-branch. Is in own words: Most of the first cut of the DMA code. It's got most of the dispatch architecture in place (Lacks actual DMA submission (The easy part, really...)) so it's not done yet, but I promised people that

Re: [Dri-devel] New code in mach64-0-0-3-dma-branch: how to approach?

2002-05-01 Thread Leif Delgass
On Wed, 1 May 2002, José Fonseca wrote: Frank just commited a set of changes to the mach64-0-0-3-dma-branch. Is in own words: Most of the first cut of the DMA code. It's got most of the dispatch architecture in place (Lacks actual DMA submission (The easy part, really...)) so

Re: [Dri-devel] New code in mach64-0-0-3-dma-branch: how to approach?

2002-05-01 Thread José Fonseca
On 2002.05.01 16:18 Leif Delgass wrote: One thing I realized concerning blits: the utah driver uses the host_data[0-15] registers to do blits which treats blits as a GUI-master operation. This means it works with pseudo-DMA. I think the better way to do it is to use the system bus

Re: [Dri-devel] New code in mach64-0-0-3-dma-branch: how to approach?

2002-05-01 Thread Frank C. Earl
On Wednesday 01 May 2002 03:58 am, JosX Fonseca wrote: Frank just commited a set of changes to the mach64-0-0-3-dma-branch. Is in own words: Most of the first cut of the DMA code. It's got most of the dispatch architecture in place (Lacks actual DMA submission (The easy part,

Re: [Dri-devel] New code in mach64-0-0-3-dma-branch: how to approach?

2002-05-01 Thread Leif Delgass
On Wed, 1 May 2002, Frank C. Earl wrote: The part which is missing is more or less what we have in the mach64-0-0-4-branch, except that the state update is still being made with MMIO. So either we add the remaining parts to mach64-0-0-3-branch or we bring Frank's changes to