[Dri-devel] [Bug 314] 3D support for Radeon IGP chips

2004-04-16 Thread bugzilla-daemon
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter your comments there. http://bugs.xfree86.org/show_bug.cgi?id=314 --- Additional Comments From [EMAIL PROTECTED] 2004-04-16 06:00 --- Hi folks, I am b

[Dri-devel] Re: Splitting binary snapshots

2004-04-16 Thread Michel Dänzer
On Thu, 2004-04-15 at 18:38, Felix KÃhling wrote: > > Here are my plans to split the binary snapshot into a device-specific > and a common (device-independent) part. Sounds good. > The only thing I'm not quite sure about is where the drm sources should > go. I suppose there are good arguments f

Re: [Dri-devel] problems with savage (prosavage KN133) and dri -SOLVED!!!

2004-04-16 Thread vud1
hi all: some weeks ago i wrote to the list because i had problems with my savage card in my acer aspire 1300: 01:00.0 VGA compatible controller: S3 Inc. VT8636A [ProSavage KN133] AGP4X VGA Controller (TwisterK) (rev 01) well i have been doing a lot of tests with several cvs versions and diferen

Re: [Dri-devel] problems with savage (prosavage KN133) and dri -SOLVED!!!

2004-04-16 Thread vud1
hi all: some weeks ago i wrote to the list because i had problems with my savage card in my acer aspire 1300: 01:00.0 VGA compatible controller: S3 Inc. VT8636A [ProSavage KN133] AGP4X VGA Controller (TwisterK) (rev 01) well i have been doing a lot of tests with several cvs versions and diferen

[Dri-devel] Re: Finally looking at the DRI SMP issues - Yahooo! (fps 30-31 fps up)!

2004-04-16 Thread Dieter Nützel
Am Freitag, 16. April 2004 00:10 schrieb Ian Romanick: > Ian Romanick wrote: > > I finally have access to an x86 SMP box, and I have a few cycles to look > > at the SMP related problems. I'm using an AGP G400 and quake3-smp. Like > > Dieter, I get a black screen and a hung program. When I break i

[Dri-devel] [r200] gltestperf - drmRadeonIrqWait: -16

2004-04-16 Thread Dieter Nützel
progs/demos> ./gltestperf GLTest v1.0 Written by David Bucciarelli Mesa: software DXTn compression/decompression available Benchmark: 0 Elapsed time for the calibration test (22282): 2.00 Selected number of benchmark iterations: 55705 Elapsed time for run 0: 1.207000 Elapsed time for run 1: 1.2

Re: [Dri-devel] Re: Finally looking at the DRI SMP issues - Yahooo! (fps 30-31 fps up)!

2004-04-16 Thread Ian Romanick
Dieter Nützel wrote: Am Freitag, 16. April 2004 00:10 schrieb Ian Romanick: Ian Romanick wrote: I finally have access to an x86 SMP box, and I have a few cycles to look at the SMP related problems. I'm using an AGP G400 and quake3-smp. Like Dieter, I get a black screen and a hung program. When

Re: [Dri-devel] problems with savage (prosavage KN133) and dri -SOLVED!!!

2004-04-16 Thread Alex Deucher
--- [EMAIL PROTECTED] wrote: > hi all: > > some weeks ago i wrote to the list because i had problems with my > savage > card in my > acer aspire 1300: > > 01:00.0 VGA compatible controller: S3 Inc. VT8636A [ProSavage KN133] > AGP4X > VGA > Controller (TwisterK) (rev 01) > > > well i have been

[Dri-devel] Re: [CHECKER] Probable security holes in 2.6.5

2004-04-16 Thread Chris Wright
* Ken Ashcraft ([EMAIL PROTECTED]) wrote: > [BUG] > /home/kash/linux/linux-2.6.5/drivers/char/drm/i810_dma.c:1276:i810_dma_mc: > ERROR:TAINT: 1267:1276:Using user value "((mc).idx * 4)" without first performing > bounds checks [SOURCE_MODEL=(lib,copy_from_user,user,taintscalar)] [PATH= > "(*((*d

[Dri-devel] [r200] What about r200-maybe-flush-less?

2004-04-16 Thread Dieter Nützel
Speed things definitely up (even on SMP). http://marc.theaimsgroup.com/?l=dri-devel&m=106668758605732&w=2 More on this here: http://marc.theaimsgroup.com/?l=dri-devel&m=107736345811718&w=2 Huray, wire-frame is on top (VTK), again. But some slowdown for [] (normal), [small_sphere] and [transparen

Re: [Dri-devel] DRI/Xfree86 Merge

2004-04-16 Thread Alan Hourihane
On Thu, Apr 15, 2004 at 08:13:53AM -0700, Alex Deucher wrote: > Speaking of merging, what are everyone's thoughts on merging the DDX > trees (drivers at least, I don't know about the rest, especially with > the licensing)? I was thinking mostly DRI<->xfree86 but I suppose we > could look at gatos

Re: [Dri-devel] DRI/Xfree86 Merge

2004-04-16 Thread Mike Mestnik
I was under the impresion that several bugs where found in 4.3.99.902 that need patching. This work has allready been done twice I shuder to think any one would bother a third. --- Alan Hourihane <[EMAIL PROTECTED]> wrote: > On Thu, Apr 15, 2004 at 08:13:53AM -0700, Alex Deucher wrote: > > Speaki

Re: [Dri-devel] [PATCH] Convert r128 driver in linux kernel 2.6 to use userland firmware loading

2004-04-16 Thread Nathanael Nerode
Michel DÃnzer wrote: On Thu, 2004-04-15 at 22:00, Nathanael Nerode wrote: This is a diff for drivers/char/drm to make r128 use userland-loadable firmware. Sigh, is this really necessary? :\ It allows for the microcode to be updated without replacing the kernel, which is not a bad thing anyway

Re: [Dri-devel] [PATCH] Convert r128 driver in linux kernel 2.6 to use userland firmware loading

2004-04-16 Thread Nathanael Nerode
Keith Whitwell wrote: Nathanael Nerode wrote: My changes are GPL licensed (of course). The r128 module is BSD licensed (though I thought it was supposed to be dual BSD/GPL) - are you willing to reconsider? Yes, I'll be happy to BSD license this; it's not as if it's really very much material, s

Re: [Dri-devel] DRI/Xfree86 Merge

2004-04-16 Thread Ian Romanick
Alan Hourihane wrote: I could merge in XFree86 4.3.99.902 which is before the license change and closer to what X.Org went with for now. That will bring us closer to both trees. And then we can delay a decision until things have settled on both sides of the pond, and see where the land lies. What

Re: [Dri-devel] DRI/Xfree86 Merge

2004-04-16 Thread Michel Dänzer
On Sat, 2004-04-17 at 00:00, Alan Hourihane wrote: > > I could merge in XFree86 4.3.99.902 which is before the license change Are you sure? AFAIK David applied the new license (or at least a similarly controversial one) to some files before it was publicly announced. > and closer to what X.Org w

Re: [Dri-devel] DRI/Xfree86 Merge

2004-04-16 Thread Roland Scheidegger
Michel DÃnzer wrote: On Sat, 2004-04-17 at 00:00, Alan Hourihane wrote: I could merge in XFree86 4.3.99.902 which is before the license change Are you sure? AFAIK David applied the new license (or at least a similarly controversial one) to some files before it was publicly announced. This page

Re: [Dri-devel] DRI/Xfree86 Merge

2004-04-16 Thread Dave Airlie
> AFAIK X.org also imported 4.3.99.902 for their version (at least the release > notes indicates that 4.3.99.902 was merged unconditionally, > http://freedesktop.org/cgi-bin/viewcvs.cgi/xc/RELNOTES?root=xorg), so if > indeed some files would be covered under the new license even for this version >

Re: [Dri-devel] [PATCH] Convert r128 driver in linux kernel 2.6 to use userland firmware loading

2004-04-16 Thread Michel Dänzer
On Fri, 2004-04-16 at 23:02, Nathanael Nerode wrote: > Michel DÃnzer wrote: > > On Thu, 2004-04-15 at 22:00, Nathanael Nerode wrote: > > > >>This is a diff for drivers/char/drm to make r128 use userland-loadable > >>firmware. > > > > Sigh, is this really necessary? :\ > It allows for the microc

[Dri-devel] [PATCH] R200 t_vertex conversion

2004-04-16 Thread Ian Romanick
This is what I have done so far to convert the R200 driver to use t_vertex. It is only a conversion for SW TCL, and it's not quite complete. I've managed to clean up all the crashes that I could find, but I've only tested with gears, geartrain, and tunnel. There are some known problems: - T

Re: [Dri-devel] [PATCH] Convert r128 driver in linux kernel 2.6 to use userland firmware loading

2004-04-16 Thread Ryan Underwood
On Sat, Apr 17, 2004 at 03:03:04AM +0200, Michel Dänzer wrote: > > It allows for the microcode to be updated without replacing the kernel, > > which is not a bad thing anyway. But changing the microcode would change the driver->chip interface anyway. So you'd have to update the driver too. Ke