Ian Romanick wrote:
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
On Sat, Apr 17, 2004 at 01:18:49AM +0200, 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
On Sad, 2004-04-17 at 06:44, Ryan Underwood wrote:
3) Neither of these is ok, must go into non-free because binary-only
firmware doesnt meet DFSG (no source) regardless of its license. Either
whole driver must go into non-free, or a crippled driver is provided in
main and a userspace loader
On Sat, 2004-04-17 at 07:44, Ryan Underwood wrote:
On Sat, Apr 17, 2004 at 03:03:04AM +0200, Michel Dnzer 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
Ian Romanick wrote:
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
I can't get a current version of the DRI cvs to build on FreeBSD any more:
cd ./config/makedepend make -f Makefile.proto bootstrap
Makefile.proto, line 30: Need an operator
Makefile.proto, line 81: Need an operator
make: fatal errors encountered -- cannot continue
*** Error code 1
Stop in
On Sat, Apr 17, 2004 at 09:36:24AM +0100, Alan Cox wrote:
This is the answer I was given by lawyers. The analogy they use is
an interesting but sensible one. If I add a chapter to a book it is
clearly a derivative work, if I bundle the one work with a second
pamphlet containing the chapter
On Sat, Apr 17, 2004 at 03:33:16PM +0200, Michel Dänzer wrote:
I don't think such a complicated scheme is needed? Just encode the
microcode version in the filename and try to load any supported version,
from most to least preferred?
I think that's what I meant. Point being, have the kernel
--- Michel Dänzer [EMAIL PROTECTED] wrote:
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
Never mind Stupid mistake on my part.
Adam
On Sat, 17 Apr 2004, Adam K Kirchhoff wrote:
I can't get a current version of the DRI cvs to build on FreeBSD any more:
cd ./config/makedepend make -f Makefile.proto bootstrap
Makefile.proto, line 30: Need an operator
Makefile.proto, line
On Sad, 2004-04-17 at 19:40, Ryan Underwood wrote:
Of course, if the legal advice you refer to was specifically aimed at
the firmware scenario, where you have a blob of who-knows-what that does
not execute on the host embedded into a driver binary, then I'm not one
to argue with that.
It was
On Sat, 2004-04-17 at 20:46, Ryan Underwood wrote:
On Sat, Apr 17, 2004 at 03:33:16PM +0200, Michel Dnzer wrote:
I don't think such a complicated scheme is needed? Just encode the
microcode version in the filename and try to load any supported version,
from most to least preferred?
I
On Wed, 2004-04-14 at 16:19, Keith Whitwell wrote:
Michel Dnzer wrote:
Does anything speak against repo-moving Makefile.{bsd,linux} to
Makefile?
I can't think of any reason not to.
Turns out a simple repo-move doesn't work for Makefile.linux as it
contains some Makefile juggling hacks.
Hi guys, I've been busy for a while, but summer is approaching with the
possibility of some spare time, so I have several questions about current
status of DRI:
1. I could not find a link to the newer ViewCVS interface on the website
- does it exist ?
2. Is anyone working on accelerated 3d
On Fri, Apr 16, 2004 at 11:35:14AM -0700, Ian Romanick wrote:
The r200 is the clear bottleneck, now
What we need next is the TMU3 patch...;-)
I'm still trying to work through the t_vertex conversion. That should
help some too. Of course, Quake3 only uses 2 TMUs anyway. I'll post
what I
On Sun, 2004-04-18 at 03:19, Vladimir Dergachev wrote:
1. I could not find a link to the newer ViewCVS interface on the website
- does it exist ?
http://dri.freedesktop.org/cgi-bin/cvsweb/dri/
2. Is anyone working on accelerated 3d for newer Radeons (R300, etc) ?
Not that I know of.
On Saturday 17 April 2004 20:19, Vladimir Dergachev wrote:
4. Are there any examples of user-space applications accessing DRM, the
same way Mesa driver does, but (hopefully) simpler ? I might have
some success in figuring out CP sequences and present the result as a
On Sat, 2004-04-17 at 07:54, Alan Hourihane wrote:
On Sat, Apr 17, 2004 at 01:18:49AM +0200, 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
On Sun, 18 Apr 2004, Michel [ISO-8859-1] Dnzer wrote:
On Sun, 2004-04-18 at 03:19, Vladimir Dergachev wrote:
1. I could not find a link to the newer ViewCVS interface on the website
- does it exist ?
http://dri.freedesktop.org/cgi-bin/cvsweb/dri/
Thank you !
3. Can anyone
The infamous CP microcode is needed. AFAIK, Benjamin Herrenschmidt got
it from ATI.
the BeOS driver has some r300 microcode in its sources...
http://www.bebits.com/appver/2938
download the r5 source at look at CPMicroCode.h in the file...
no idea what it is of course it might be 2d only or
On Sun, 18 Apr 2004, Dave Airlie wrote:
The infamous CP microcode is needed. AFAIK, Benjamin Herrenschmidt got
it from ATI.
the BeOS driver has some r300 microcode in its sources...
http://www.bebits.com/appver/2938
download the r5 source at look at CPMicroCode.h in the file...
no
21 matches
Mail list logo
