Re: [Dri-devel] radeon mmio area size

2002-07-17 Thread Tim Smith
controller: PCI device 1002:5157 (ATI Technologies Inc) (rev 0). IRQ 9. Master Capable. Latency=32. Min Gnt=8. Prefetchable 32 bit memory at 0xe000 [0xe7ff]. I/O at 0x9000 [0x90ff]. Non-prefetchable 32 bit memory at 0xed00 [0xed00ffff]. Looks the same as yours.

Re: [Dri-devel] Tribes 2 Lockups: Help me pinpoint the problem...

2002-07-15 Thread Tim Smith
as yours (freelist_get returning NULL - not that that particular error message turned out to have much to do with the real problem, as was pointed out to me when I started wondering aloud about it). Possibly you're running into the same problem? -- Tim Smith ([EMA

Re: [Dri-devel] Radeon scratch register writeback patch

2002-07-15 Thread Tim Smith
On Monday 15 Jul 2002 9:33 pm, Charl P. Botha scribed numinously:" > On Mon, Jul 15, 2002 at 09:25:18PM +0100, Tim Smith wrote: > > I'm back to probing at the lockup now that I have my "hacking space" > > back. I'll post the WAIT_UNTIL_3D_IDLE version in

[Dri-devel] Radeon 7500 lockup workaround

2002-07-15 Thread Tim Smith
Here's the workaround for the Radeon 7500 lockup. I won't dignify it by calling it a fix until I've investigated the actual commands being sent and determined whether there's a better way of fixing it. -- Tim Smith ([EMAIL PROTECTED]) Imperial Royal Guard foils attempted

Re: [Dri-devel] Radeon scratch register writeback patch

2002-07-15 Thread Tim Smith
ile I try to understand the true problem more. Heh. My boss is in the country tomorrow. Maybe I can convince him to let me spend time on this at work -- Tim Smith ([EMAIL PROTECTED]) SMALL ADS: WANTED for treason, arson and insurrection. Reasonable rates. Apply within. -

Re: [Dri-devel] Radeon scratch register writeback patch

2002-07-11 Thread Tim Smith
On Tuesday 09 Jul 2002 12:11 am, Michel Dänzer scribed numinously:" > On Mon, 2002-07-08 at 20:17, Tim Smith wrote: > > On Monday 08 Jul 2002 12:49 am, Michel Dänzer scribed numinously:" > > > > > The scratch register values need to be read with DRM_READ3

Re: [Dri-devel] tuxracer texture problem on radeon

2002-07-08 Thread Tim Smith
; > Ok, I'll investigate the application to see if it's the problem. > > I seem to recall that TuxRacer more or less worked with the 4.2 Radeon > 7500 drivers, but doesn't seem to work with the TCL drivers. This might &

Re: [Dri-devel] Radeon scratch register writeback patch

2002-07-08 Thread Tim Smith
On Monday 08 Jul 2002 12:49 am, Michel Dänzer scribed numinously:" > On Tue, 2002-07-02 at 00:32, Tim Smith wrote: > > Here it is. It'll need cleaning up if it works, but it'll do as a test. > > Took me quite some fiddling to get it working here, but that's m

Re: [Dri-devel] bsd-3-0-0-branch status -- SET_SCISSORS

2002-07-04 Thread Tim Smith
On Thursday 04 Jul 2002 8:03 pm, Tim Smith scribed numinously:" > On Thursday 04 Jul 2002 7:22 pm, Felix Kühling scribed numinously:" > > > On Thu, 4 Jul 2002 17:19:23 +0100 > > > > Tim Smith <[EMAIL PROTECTED]> wrote: > > > (on my system glxge

Re: [Dri-devel] bsd-3-0-0-branch status -- SET_SCISSORS

2002-07-04 Thread Tim Smith
On Thursday 04 Jul 2002 7:22 pm, Felix Kühling scribed numinously:" > On Thu, 4 Jul 2002 17:19:23 +0100 > > Tim Smith <[EMAIL PROTECTED]> wrote: > > (on my system glxgears behaves quite oddly with pageflipping enabled > > even with only one; it has brief peri

Re: [Dri-devel] bsd-3-0-0-branch status -- SET_SCISSORS

2002-07-04 Thread Tim Smith
On Thursday 04 Jul 2002 7:11 pm, Keith Whitwell scribed numinously:" > Tim Smith wrote: > > On Thursday 04 Jul 2002 5:28 pm, Keith Whitwell scribed numinously:" > > > >>>I've just tried two glxgears at the same time and I am seeing utterly > >>

Re: [Dri-devel] bsd-3-0-0-branch status -- SET_SCISSORS

2002-07-04 Thread Tim Smith
nd power-cycling too. Most annoying. I'll take the NOMMIO stuff out of my test tree as well and see if I can provoke it again. -- Tim Smith ([EMAIL PROTECTED]) "Oink" is a deadly insult in Gamorrese. --

Re: [Dri-devel] bsd-3-0-0-branch status -- SET_SCISSORS

2002-07-04 Thread Tim Smith
animate slowly backwards, but shows no significant change in framerate - it is the only app that I've tried that behaves so strangely) I have some suspicions. Amongst them is the fact that the 2D drivers emit clip rectangles too, I notice. I will have a look at it and see if I can some o

Re: [Dri-devel] Radeon scratch register writeback patch

2002-07-03 Thread Tim Smith
On Wednesday 03 Jul 2002 5:03 am, David Willmore scribed numinously:" > > On Tue, Jul 02, 2002 at 10:48:29PM +0100, Tim Smith wrote: > > > Great. So we're OK on > > > > > > Radeon 7500 > > > Radeon 7200 > > > > > > anyone got a

Re: [Dri-devel] Radeon 7500 lockup FIXED

2002-07-03 Thread Tim Smith
On Tuesday 02 Jul 2002 11:57 pm, Michel Dänzer scribed numinously:" > On Tue, 2002-07-02 at 23:40, Tim Smith wrote: > > On Monday 01 Jul 2002 10:10 pm, Keith Whitwell scribed numinously:" > > > > > Michel Dänzer wrote: > > > >

Re: [Dri-devel] Radeon scratch register writeback patch

2002-07-02 Thread Tim Smith
On Tuesday 02 Jul 2002 12:27 am, Vedran Rodic scribed numinously:" > On Mon, Jul 01, 2002 at 11:32:04PM +0100, Tim Smith wrote: > > Here it is. It'll need cleaning up if it works, but it'll do as a test. > > Thanks Tim > > Works fine here on my old Radeon 7

Re: [Dri-devel] Radeon 7500 lockup FIXED

2002-07-02 Thread Tim Smith
On Monday 01 Jul 2002 10:10 pm, Keith Whitwell scribed numinously:" > Michel Dänzer wrote: > > On Mon, 2002-07-01 at 21:28, Tim Smith wrote: > >>- BEGIN_RING( 4 ); > >>- OUT_RING( CP_PACKET0( RADEON_RE_TOP_LEFT, 0 ) ); > >>- OUT_RING( (box

Re: [Dri-devel] Radeon 7500 lockup FIXED

2002-07-02 Thread Tim Smith
o objections to access for you, less work for me. :) > > My feelings also -- Tim, do you have a sourceforge user id? I do now; electronghost Silly, but all the non-silly ones were taken... -- Tim Smith ([EMAIL PROTECTED]) "And I did woggle and nerk, me boys / as I shall quickly tell /

[Dri-devel] Radeon scratch register writeback patch

2002-07-01 Thread Tim Smith
Here it is. It'll need cleaning up if it works, but it'll do as a test. -- Tim Smith ([EMAIL PROTECTED]) "A fray" -- Groo the Wanderer Index: xc/lib/GL/mesa/src/drv/radeon/radeon_ioctl.c === RCS file: /c

Re: [Dri-devel] Radeon 7500 lockup FIXED

2002-07-01 Thread Tim Smith
On Monday 01 Jul 2002 10:57 pm, Michel Dänzer scribed numinously:" > On Mon, 2002-07-01 at 23:23, Tim Smith wrote: > > On Monday 01 Jul 2002 9:06 pm, Michel Dänzer scribed numinously:" > > > > > On Mon, 2002-07-01 at 21:28, Tim Smith wr

Re: [Dri-devel] Radeon 7500 lockup FIXED

2002-07-01 Thread Tim Smith
On Monday 01 Jul 2002 10:10 pm, Keith Whitwell scribed numinously:" > Michel Dänzer wrote: > > On Mon, 2002-07-01 at 21:28, Tim Smith wrote: > >>- BEGIN_RING( 4 ); > >>- OUT_RING( CP_PACKET0( RADEON_RE_TOP_LEFT, 0 ) ); > >>- OUT_RING( (box

Re: [Dri-devel] Radeon 7500 lockup FIXED

2002-07-01 Thread Tim Smith
On Monday 01 Jul 2002 9:06 pm, Michel Dänzer scribed numinously:" > On Mon, 2002-07-01 at 21:28, Tim Smith wrote: > > - BEGIN_RING( 4 ); > > - OUT_RING( CP_PACKET0( RADEON_RE_TOP_LEFT, 0 ) ); > > - OUT_RING( (box->y1 << 16) | box->x1 ); > > -

Re: [Dri-devel] Radeon 7500 lockup FIXED

2002-07-01 Thread Tim Smith
On Monday 01 Jul 2002 8:38 pm, Keith Whitwell scribed numinously:" > Tim Smith wrote: > > On Monday 01 Jul 2002 5:19 pm, Keith Whitwell scribed numinously:" > > > >>>I'm running without PageFlipping, and don't see any SwapBuffers ioctls

Re: [Dri-devel] Radeon 7500 lockup FIXED

2002-07-01 Thread Tim Smith
packets. Given that this fixes it without a wait, I theorise that either it's more of a conflict over the host interface than over the 2D/3D engines, or the microengine knows something about the SET_SCISSORS command packet that it doesn't know about two consecutive register writes (which l

Re: [Dri-devel] Radeon 7500 lockup FIXED

2002-07-01 Thread Tim Smith
On Sunday 30 Jun 2002 8:49 pm, Keith Whitwell scribed numinously:" > Tim Smith wrote: > > I found a few other ways of provoking the problem while I was at it, > > and dragging an xclock window over the 3D view did it too (with a > > window manager and "solidmo

Re: [Dri-devel] Radeon 7500 lockup FIXED

2002-06-29 Thread Tim Smith
On Saturday 29 Jun 2002 4:05 pm, Tim Smith scribed numinously:" > In a totally unrelated note, the texture funnies that I reported earlier > do not occur in 24-bit mode, but only in 16-bit mode. Tux Racer shows > this too though in tux racer the problem is still visible in 16bit

[Dri-devel] Radeon 7500 lockup FIXED

2002-06-29 Thread Tim Smith
an before. FWIW, I *expect* it to turn into a slideshow at that point with this app; zooming out that far is possible, but not exactly recommended :-) -- Tim Smith ([EMAIL PROTECTED]) The difference between theory and practice is that, in t

Re: [Dri-devel] ATI Radeon 7500 Performance Issues

2002-06-23 Thread Tim Smith
0. Similarly, enabling page flipping raises the rate to around 600fps. I'm running with the latest CVS HEAD. I generally run with page flipping disabled, because when it's enabled I get jumpy animation and the appearance of the gears appear

Re: [Dri-devel] Radeon 7500 lockup

2002-06-05 Thread Tim Smith
On Friday 31 May 2002 4:54 pm, Tim Smith scribed numinously:" > On Friday 31 May 2002 4:12 pm, Keith Whitwell scribed numinously:" > > > Tim Smith wrote: > > > Me too. Could this be a locking problem? There seem to be two > > > contexts own

Re: [Dri-devel] Radeon 7500 lockup

2002-05-31 Thread Tim Smith
On Friday 31 May 2002 4:12 pm, Keith Whitwell scribed numinously:" > Tim Smith wrote: > > On Friday 31 May 2002 2:00 pm, Keith Whitwell scribed numinously:" > > > >>Tim Smith wrote: > >>>I conclude from this that writing the ring tail register cau

Re: [Dri-devel] Radeon 7500 lockup

2002-05-31 Thread Tim Smith
On Friday 31 May 2002 2:00 pm, Keith Whitwell scribed numinously:" > Tim Smith wrote: > > I conclude from this that writing the ring tail register causes the > > card to fetch all the commands up until that point and feed them to its > > FIFO, which may fill it... It&#x

Re: [Dri-devel] Radeon 7500 lockup

2002-05-31 Thread Tim Smith
the wireframe highlight boxes it uses to indicate the currently selected object spray lines randomly around the screen. -- Tim Smith ([EMAIL PROTECTED]) Food for myself is one thing, but food for a whole village? That is a lot of cheese dip. -- Groo the Wanderer __

Re: [Dri-devel] Radeon 7500 lockup

2002-05-30 Thread Tim Smith
tually did fail for > the whole cycle, the 3d app should exit, and the 2d should write to > /var/log/XFree.0.log and I've seen neither. I tried that trace early this morning. In my case it's the app that generates the errors. That's reasonable though; I doubt Quake3 uses the 2d

Re: [Dri-devel] Radeon 7500 lockup

2002-05-30 Thread Tim Smith
to go from 64 slots free to 0 in one ioctl... ...so maybe what we need is some clue as to exactly how many commands we're about to feed it (I made Wild-Ass-Guesses about the number of commands when we were just blasting a buffer from userspace, which may go a long way to explaining the sucky perfor

Re: [Dri-devel] Radeon 7500 lockup

2002-05-29 Thread Tim Smith
On Wednesday 29 May 2002 11:26 am, Keith Whitwell scribed numinously:" > Tim Smith wrote: > > On Tuesday 28 May 2002 1:13 pm, Keith Whitwell scribed numinously:" > > > >>Tim Smith wrote: > >>>On Tuesday 28 May 2002 8:40 am, Keith Whitwell sc

Re: [Dri-devel] Radeon 7500 lockup

2002-05-29 Thread Tim Smith
On Tuesday 28 May 2002 1:13 pm, Keith Whitwell scribed numinously:" > Tim Smith wrote: > > On Tuesday 28 May 2002 8:40 am, Keith Whitwell scribed numinously:" > > > >>Tim Smith wrote: > >>>I've done some more digging and it would app

Re: [Dri-devel] Radeon 7500 lockup

2002-05-28 Thread Tim Smith
On Tuesday 28 May 2002 8:40 am, Keith Whitwell scribed numinously:" > Tim Smith wrote: > > I've done some more digging and it would appear to send an enormous > > amount of commands via radeon_cp_cmdbuf, all ending up going via > > radeon_emit_packet3_cliprect. Act

Re: [Dri-devel] Radeon 7500 lockup

2002-05-27 Thread Tim Smith
On Monday 27 May 2002 8:22 pm, Michael scribed numinously:" > On Sun, May 26, 2002 at 06:50:11PM +0100, Tim Smith wrote: > > The tcl-0-0-branch really doesn't like 2D menus being popped up over > > the 3D drawing area; it locks up after a few of these with or without >

Re: [Dri-devel] Radeon 7500 lockup

2002-05-26 Thread Tim Smith
traces and produce more information if requested. The system in question is an Athlon 1200 on a KT7RAID m/b with a Radeon 7500 SDR 64Meg. Yes, I do have mem=nopentium set. -- Tim Smith ([EMAIL PROTECTED]) "And I did woggle and nerk, me b

Re: [Dri-devel] Radeon 7500 lockup

2002-05-25 Thread Tim Smith
Sometimes it runs out of FIFO and sometimes it runs out of buffers. I've got reams of logs by now, and chased an awful lot of red herrings :-). The culprit always seems to be a call to radeon_cp_vertex2, but currently I'm blowed if I can figure out why. I'm going to con

Re: [Dri-devel] Radeon 7500 lockup

2002-05-24 Thread Tim Smith
On Friday 24 May 2002 7:36 pm, Tim Smith scribed numinously:" > I've introduced a tiny usleep into the loop in radeon_accel.c to give > syslog a chance and my loghost now produces a couple of thousand lines of > the form > > moomintroll kernel: [drm:radeon_freelist_get]

Re: [Dri-devel] Radeon 7500 lockup

2002-05-24 Thread Tim Smith
s are entirely different. Logs from a couple of tries are at http://www.electronghost.co.uk/radlock1.txt.gz Any ideas about where I should look? -- Tim Smith ([EMAIL PROTECTED]) Interfere? Of course we should interfere! Always do what you're best at, that's what I say. -- Doctor W

Re: [Dri-devel] Radeon 7500 lockup

2002-05-24 Thread Tim Smith
On Friday 24 May 2002 8:49 am, Keith Whitwell scribed numinously:" > Tim Smith wrote: > > I have a nice, 100% reliable way to lock up my Radeon 7500 using the > > most recent CVS. I can do this with Tux Racer, if I play for a couple > > of courses, but it's much eas

[Dri-devel] Radeon 7500 lockup

2002-05-23 Thread Tim Smith
55 moomintroll kernel: [drm:radeon_cp_dispatch_indirect] indirect: buf=13 s=0x8c20 e=0x8cd6 May 24 00:11:55 moomintroll kernel: [drm:radeon_emit_state] radeon_emit_state: dirty=0x00000201 ...and after more of the same I reboot -- Tim Smith ([EMAIL PROTECTED]) Interfere? Of course we should inter