On Tue, 15 Jul 2003, Alex Deucher wrote:
This proposal comes up periodically on this and other xfree lists, but
never really goes anywhere. Why not raise money from the open source
community to fund open source driver development?
It is very difficult to convert money into code. It's
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Why not raise money from the open source community to fund open source
driver development?
It sounds good, although I'm sure there're plenty of developers there in DRI.
Someone will have to decide which projects and developers receive the money
[This e-mail has been automatically generated.]
You have one or more bugs assigned to you in the Bugzilla
bugsystem (http://bugs.xfree86.org/) that require
attention.
All of these bugs are in the NEW state, and have not been touched
in 7 days or more. You need to take a look at them, and
I've put more branches in my rsync mirror, namely:
config-0-0-1-branch
mach64-0-0-6-branch
newdrm-0-0-1-branch
savage-0-0-1-branch
savage-1_0_0-branch
To download a branch do something like:
rsync -avz --delete rsync://mefriss1.swan.ac.uk/dri/branch/ branch/
where 'branch' is one
On Wed, Jul 16, 2003 at 12:06:20PM +0100, José Fonseca wrote:
Be careful with the
trailing '/' or you might end erasing your home directory or whateever
directory you're doing this.
Forget this nonsense. I had little sleep today and it shows.
Still the '/' are important, otherwise in the
On Wed, Jul 16, 2003 at 12:05:02PM +0100, José Fonseca wrote:
I've put more branches in my rsync mirror, namely:
config-0-0-1-branch
mach64-0-0-6-branch
newdrm-0-0-1-branch
savage-0-0-1-branch
savage-1_0_0-branch
To download a branch do something like:
rsync -avz
Hi Alan (et dri-devel),
In your -ac1 release you mention that you have a todo to look at the
horribly out of date 2.5 DRM layer,
AFAIK Linus is fairly in sync with the DRI tree on sf.. any recent changes
I've made are in -test1, the 2.4 tree is probably more out of date (the
agp key stuff isn't
On Mer, 2003-07-16 at 13:01, Dave Airlie wrote:
Hi Alan (et dri-devel),
In your -ac1 release you mention that you have a todo to look at the
horribly out of date 2.5 DRM layer,
AFAIK Linus is fairly in sync with the DRI tree on sf.. any recent changes
I've made are in -test1, the 2.4 tree
What about tungsten graphics or Providenza Boekelheide, Inc. (Tim
Robert's company? Plus I'm sure there are other small development
companies that would be interested.
Alex
--- Mark Vojkovich [EMAIL PROTECTED] wrote:
On Tue, 15 Jul 2003, Alex Deucher wrote:
This proposal comes up
Support for HW accelerated indirect rendering is just a matter of
restructuring some library interfaces so that GLX commands can get
decoded and sent to the hardware rather than the sw renderer. It's in
the pipeline for future development by the DRI folks, but if it were
sponsored, it might
On Tue, 15 Jul 2003, Mark Vojkovich wrote:
It is very difficult to convert money into code. It's probably
easier to raise the money than it is to find a way to convert
that into code.
Not exactly a driver, but I was under the impression that remote GLX
support (ie hardware accelerated 3D
On Mer, 2003-07-16 at 15:08, Alex Deucher wrote:
Support for HW accelerated indirect rendering is just a matter of
restructuring some library interfaces so that GLX commands can get
decoded and sent to the hardware rather than the sw renderer. It's in
the pipeline for future development by
On Wed, Jul 16, 2003 at 04:36:33PM +0100, Alan Cox wrote:
On Mer, 2003-07-16 at 15:08, Alex Deucher wrote:
Support for HW accelerated indirect rendering is just a matter of
restructuring some library interfaces so that GLX commands can get
decoded and sent to the hardware rather than the sw
Dear Sirs
After updating to Mandrake Linux 9.1 I get transparent walls in Return
to castle Wolfenstein.It means to see shimmering through the rooms/walls
etc. behind which of course makes it very annoying/impossible to play.
There was a major driver rewrite so I guess that's where this comes
from.
REMOVE MY NAME FROM YOUR
LIST
2.4-test works for the cards I've got, 2.5 crashes for radeon and seems
to have i810 problems. I've not looked deeply into it yet since with
2.6.0 test I've got other radeon related problems that make X crash
without DRI even.
I think the latest Linus update should fix the i810 issue that
Keith Whitwell wrote:
[EMAIL PROTECTED] wrote:
Hi,
Attached is a small patch for the Radeon driver. It allows use of the
full
range of point sizes defined in Mesa. It uses the rasterization fallback
mechanism when rendering points outside the hardware supported range
(!= 1.0).
Since point
On Thu, 17 Jul 2003, Dave Airlie wrote:
I think the latest Linus update should fix the i810 issue that was
reported here, but there may still be some hiding, (that was the one with
the key being 0) but I think any probs in 2.6.0-test1 we should also
see in the the DRI tree...
test1
18 matches
Mail list logo
