Re: [Dri-devel] Radeon switch to VT and back X freeze

2002-07-17 Thread Charl P. Botha
On Wed, Jul 17, 2002 at 01:04:38AM +0200, Michel Dänzer wrote: On Tue, 2002-07-16 at 23:02, Charl P. Botha wrote: Option AGPMode 2 Does 1x make a difference? 1x makes no difference; still X freezes after a switch to VT and back. # Option ForcePCIMode On # not

[Dri-devel] segfault in r200InitIoctlFuncs-r200GetAllParams.

2002-07-17 Thread Mike Mestnik
I built with -O3 -march=athlon, thought I'v been doing that for some time now. ddd reports the segfalut during the pushl of the fd, just befor calling drmCommandWriteRead. Dump of assembler code for function r200InitIoctlFuncs: 0x4054eba0 r200InitIoctlFuncs:push %ebp

Re: [Dri-devel] radeon mmio area size

2002-07-17 Thread Markus Benning
Hi, here is mine: Bus 1, device 0, function 0: VGA compatible controller: ATI Technologies Inc Radeon Mobility M6 LY (rev 0). IRQ 10. Master Capable. Latency=66. Min Gnt=8. Prefetchable 32 bit memory at 0xd800 [0xdfff]. I/O at 0x2000 [0x20ff].

[Dri-devel] 8500 Xvideo

2002-07-17 Thread Marc Poulhiès
Hi, sorry if this is a dumb question :) I was wondering if it was possible to use Xvideo with the radeon 8500 drivers? I know gatos is more apropriate for such questions, but i would like to have 3D and Xvideo. For the moment i'm forced to use mplayer with the -noxv switch... Thanks

[Dri-devel] Re: Mach64 flatshading

2002-07-17 Thread Michel Dänzer
On Tue, 2002-07-16 at 20:17, Leif Delgass wrote: On Tue, 16 Jul 2002, Keith Whitwell wrote: Well, it's not high on my list. I don't think flat-shading is used that often, and the changes don't have any effect on smooth shading. Actually, it _eliminates_ some saves/restores

Re: [Dri-devel] radeon mmio area size

2002-07-17 Thread Adam Duck
Michal == Michal Bukovjan [EMAIL PROTECTED] writes: Michal Keith Whitwell wrote: Can someone out there check this quickly? In radeon.h in the 2d driver, the size of the radeon mmio area is defined as 0x8 - however, on my r200 at least, /proc/pci shows the

[Dri-devel] Re: r128 PPC patches

2002-07-17 Thread Michel Dänzer
On Wed, 2002-07-17 at 03:32, Henry Worth wrote: Michel Dänzer wrote: On Wed, 2002-07-17 at 02:10, Henry Worth wrote: Attached are patches for r128 on ppc. Rather little change to the r128 code was needed once I gave up on the char arrays for the vertex colors, and embraced the hw

[Dri-devel] Re: r128 PPC patches

2002-07-17 Thread Michel Dänzer
On Wed, 2002-07-17 at 05:15, Henry Worth wrote: Henry Worth wrote: I gave the driver a quick try without the HOST_BIG_ENDIAN_EN bit set and with the PACK*LE macros. And, the 2-d stuff seems to be working and the textures do need the PACK*LE macros. So, perhaps the bit only impacts the

Re: [Dri-devel] radeon mmio area size

2002-07-17 Thread Michal Bukovjan
Adam Duck wrote: Michal == Michal Bukovjan [EMAIL PROTECTED] writes: Michal Keith Whitwell wrote: Can someone out there check this quickly? In radeon.h in the 2d driver, the size of the radeon mmio area is defined as 0x8 - however, on my r200 at

Re: [Dri-devel] radeon mmio area size

2002-07-17 Thread Tim Smith
On Tuesday 16 Jul 2002 8:58 pm, Keith Whitwell scribed numinously: Can someone out there check this quickly? In radeon.h in the 2d driver, the size of the radeon mmio area is defined as 0x8 - however, on my r200 at least, /proc/pci shows the area as being 1/8th that size: Bus 1,

Re: [Dri-devel] Re: Mach64 flatshading

2002-07-17 Thread Leif Delgass
On 17 Jul 2002, Michel Dänzer wrote: On Tue, 2002-07-16 at 20:17, Leif Delgass wrote: On Tue, 16 Jul 2002, Keith Whitwell wrote: Well, it's not high on my list. I don't think flat-shading is used that often, and the changes don't have any effect on smooth shading. Actually,

Re: [Mesa3d-dev] Re: [Dri-devel] Re: Mach64 flatshading

2002-07-17 Thread Leif Delgass
On Wed, 17 Jul 2002, Leif Delgass wrote: On 17 Jul 2002, Michel Dänzer wrote: On Tue, 2002-07-16 at 20:17, Leif Delgass wrote: On Tue, 16 Jul 2002, Keith Whitwell wrote: Well, it's not high on my list. I don't think flat-shading is used that often, and the changes don't

Re: [Dri-devel] Re: r128 PPC patches

2002-07-17 Thread Leif Delgass
On Tue, 16 Jul 2002, Leif Delgass wrote: These look very good to me, I'll commit them. Leif, can you verify they don't break x86? I'd be very surprised, but it wouldn't be the first time. :) I'll give these a try once I've updated my tree, I was testing from binaries before. The

Re: [Dri-devel] Re: r128 PPC patches

2002-07-17 Thread Michel Dänzer
On Wed, 2002-07-17 at 16:50, Leif Delgass wrote: On Tue, 16 Jul 2002, Leif Delgass wrote: These look very good to me, I'll commit them. Leif, can you verify they don't break x86? I'd be very surprised, but it wouldn't be the first time. :) I'll give these a try once I've updated

[Dri-devel] MACH64VT (264VT) vs. RAGE IIc

2002-07-17 Thread Dieter Ntzel
Hello, I have both (PCI) for my fathers computer. Which one is better? Any docs? Specs? Thanks, Dieter --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf

Re: [Dri-devel] MACH64VT (264VT) vs. RAGE IIc

2002-07-17 Thread Leif Delgass
The Rage IIc is part of the more recent GT family and adds improved video filtering (according to the programmer's guide) and some 3D features (texturing, I think). Unfortunately, neither of these cards are supported by the DRI driver since they don't have triangle setup. On Wed, 17 Jul 2002,

Re: [Dri-devel] Re: Mach64 flatshading

2002-07-17 Thread Keith Whitwell
Michel Dänzer wrote: On Tue, 2002-07-16 at 20:17, Leif Delgass wrote: On Tue, 16 Jul 2002, Keith Whitwell wrote: Well, it's not high on my list. I don't think flat-shading is used that often, and the changes don't have any effect on smooth shading. Actually, it _eliminates_ some

[Dri-devel] Re: radeon mmio area size

2002-07-17 Thread Konstantin Lepikhov
Hi Keith! Tuesday 16, at 01:58:29 PM you wrote: Can someone out there check this quickly? In radeon.h in the 2d driver, the size of the radeon mmio area is defined as 0x8 - however, on my r200 at least, /proc/pci shows the area as being 1/8th that size: Bus 1, device 0,

Re: [Dri-devel] MACH64VT (264VT) vs. RAGE IIc

2002-07-17 Thread Leif Delgass
It also looks like bus-mastering capabilities were added starting with the 264VT-B and Rage II. That would include Rage IIc, but not plain 264VT. However, the 2D driver doesn't currently use bus mastering. On Wed, 17 Jul 2002, Leif Delgass wrote: The Rage IIc is part of the more recent GT

[Dri-devel] mmio size -- thanks everyone

2002-07-17 Thread Keith Whitwell
OK, I've got enough info to get an idea of what hardware variation exists out there. Thanks to everyone who responded. Keith --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf

[Dri-devel] Re: r128 PPC patches

2002-07-17 Thread Henry Worth
Michel Dänzer wrote: AGP has become very stable here since the radeon driver doesn't update the ring write pointer in ADVANCE_RING() but in the new COMMIT_RING(). Seems updating it 'too often' is no good, for whatever 'too often' may mean. Does this also involve the differences between the

Re: [Dri-devel] Re: Mach64 flatshading

2002-07-17 Thread Leif Delgass
On 17 Jul 2002, Michel Dänzer wrote: On Wed, 2002-07-17 at 20:05, Keith Whitwell wrote: I've fixed this for drivers that use t_dd_triemit.h -- currently only radeon and r200. Great job! The clipping problems I originally reported with the xscreensaver gears hack and fsv are fixed.

Re: [Dri-devel] Re: Mach64 flatshading

2002-07-17 Thread Leif Delgass
On Wed, 17 Jul 2002, Leif Delgass wrote: On 17 Jul 2002, Michel Dänzer wrote: On Wed, 2002-07-17 at 20:05, Keith Whitwell wrote: I've fixed this for drivers that use t_dd_triemit.h -- currently only radeon and r200. Great job! The clipping problems I originally reported with the

Re: [Dri-devel] Re: Mach64 flatshading

2002-07-17 Thread Keith Whitwell
Leif Delgass wrote: On Wed, 17 Jul 2002, Leif Delgass wrote: On 17 Jul 2002, Michel Dänzer wrote: On Wed, 2002-07-17 at 20:05, Keith Whitwell wrote: I've fixed this for drivers that use t_dd_triemit.h -- currently only radeon and r200. Great job! The clipping problems I originally

Re: [Dri-devel] Re: r128 PPC patches

2002-07-17 Thread Henry Worth
I applied and retested it, looks good. One pedantic little change to the diff that I missed is attached, it might avoid future problems. Another version to fix a typo. Henry --- r128-dri-endianness.diff.orig Wed Jul 17 12:02:48 2002 +++ r128-dri-endianness.diffWed Jul 17

[Dri-devel] Have a sneak peak at the new DRI website and give your opinions.

2002-07-17 Thread Smitty
email me and I will email you the updated version, it is currently less than 70K uncompressed (it uses the existing site) this version may be up to double that -I'll try to keep it down in size. Liam it depends --- This sf.net email is

[Dri-devel] Re: r128 PPC patches

2002-07-17 Thread Michel Dänzer
On Wed, 2002-07-17 at 20:03, Henry Worth wrote: Michel Dänzer wrote: AGP has become very stable here since the radeon driver doesn't update the ring write pointer in ADVANCE_RING() but in the new COMMIT_RING(). Seems updating it 'too often' is no good, for whatever 'too often' may mean.

[Dri-devel] Weird memory : messages in the kernel log

2002-07-17 Thread Pavel Roskin
Hello! I'm using Linux 2.4.19-rc1-ac7, and sometimes the kernel prints strange messages to the kernel log while XFree86 is running: memory : c71c43d4 memory : c71c441c memory : c71c4464 It turns out that the messages come from drivers/char/agp/agpgart_fe.c Please keep in mind that the debug

Re: [Dri-devel] Re: Mach64 flatshading

2002-07-17 Thread Leif Delgass
On Wed, 17 Jul 2002, Keith Whitwell wrote: I've done all the others. Lets see if testing was required... So, should I commit the fix for r128? I've tested that and it works fine. Yes, go ahead. I took a look at the other drivers concerning the read buffer fix. It looks like

[Dri-devel] Re: r128 PPC patches

2002-07-17 Thread Henry Worth
Michel Dänzer wrote: The intermediate variable isn't needed if one changes the macro argument from v to e.g. v0. I've now basically copied those macros from the radeon driver and updated the above patch to what I just committed. Thanks for your fixes! Took a look at the archive, I had tried

Re: [Dri-devel] Radeon switch to VT and back X freeze

2002-07-17 Thread Charl P. Botha
On Wed, Jul 17, 2002 at 09:38:54AM +0200, Charl P. Botha wrote: On Wed, Jul 17, 2002 at 01:04:38AM +0200, Michel Dänzer wrote: The code is there but not enabled on x86 yet. Can you try with it enabled? You need to define PCIGART_ENABLED both in the DRM and the 2D driver. It would also be

Re: [Dri-devel] Radeon switch to VT and back X freeze

2002-07-17 Thread Dave Jones
On Wed, Jul 17, 2002 at 11:18:59PM +0200, Charl P. Botha wrote: I think I'm going to give 2.5.x (with the 2.4 IDE backport, no sense in throwing away all my data) kernel a shot to see whether updates to agpgart make any difference. 2.5.26 is currently missing some of the fixes of

[Dri-devel] Re: r128 PPC patches

2002-07-17 Thread Michel Dänzer
On Wed, 2002-07-17 at 23:15, Henry Worth wrote: Michel Dänzer wrote: The intermediate variable isn't needed if one changes the macro argument from v to e.g. v0. I've now basically copied those macros from the radeon driver and updated the above patch to what I just committed. Thanks