I haven't moved anything out of shared, it's all paralleled in
shared-core. 90% of the changes are from DRM() macro removal. I did
eliminate one header file for each device since I kept deleting things
until they were empty.
2.4 is a bigger question to me. For example 2.6 is adding the idr_xxx
sup
On Wed, 29 Sep 2004 13:37:59 +0100, Christoph Hellwig <[EMAIL PROTECTED]> wrote:
> Some ideas that would be nice improvements still (not that some may be
> inherited from the old drm code, I just looked at the CVS checkout):
>
> - once we have Alan's idea of the graphics core implemented drm_init
A while back I mentioned on dri-devel that Savage cards will segfault RTCW
while loading the Checkpoint demo.
( http://www.nixnuts.net/benchmarks/current/ ) The problem is in
Mesa/src/mesa/tnl/t_tertex.c around lines 741 and 913.
for (j = 0; j < count; j++) {
GLvector4f *vptr = VB->A
Hello!
When browsing the web I found this: http://sw-shader.sf.net.
It's full software implementation of DX9 for windows.. using SIMD/SSE/MMX.
Could this help Mesa in any way? Mainly the shader optimizations..
-- Pasi Kärkkäinen
^
>
> I would prefer to see the changes for the core live in shared/ like
> always and have the current directories disappear, but it's not a big
> deal.
Merging the shared dirs is not a major undertaking, you could do it with
some static inlines in the platform directories to deal with the lack of
On Thu, 2004-09-30 at 16:52, Jon Smirl wrote:
> What do we want to do about drm-core vs the old build model?
>
> There is no real difference between the code in the linux directory
> and linux-core except for the removal of the DRM macros and the
> associated restructuring needed to make everythin
On Thu, 2004-09-30 at 16:47, Jon Smirl wrote:
> CVSROOT: /cvs/dri
> Module name: drm
> Repository: drm/linux-core/
> Changes by: [EMAIL PROTECTED] 04/09/30 16:47:45
>
> Log message:
> Make the debug memory functions compile for the core model.
Has anybody ever used the drm memor
What do we want to do about drm-core vs the old build model?
There is no real difference between the code in the linux directory
and linux-core except for the removal of the DRM macros and the
associated restructuring needed to make everything work. When we get
linux-core working without problems,
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://freedesktop.org/bugzilla/show_bug.cgi?id=1501
[EMAIL PROTECTED] changed:
What|Removed |Added
On Thu, 30 Sep 2004 21:21:43 +0200, Philipp Klaus Krause <[EMAIL PROTECTED]> wrote:
> Ian Romanick schrieb:
>
> >
> > Looking at the list, I noticed a couple of odd things. Why don't the
> > ATI drivers support GL_{ARB,EXT,NV}_texture_rectange or
> > GL_{ARB,EXT}_blend_equation_separate?
>
> ATI
On Thu, 30 Sep 2004 11:27:28 -0700, Ian Romanick <[EMAIL PROTECTED]> wrote:
> Mike Mestnik wrote:
>
> > Here is a straigth diff, I didn't do a udiff since I think we all know the
> > glxinfo output fairly well. I did make one change s/, $//g and s/, /\n
> > /g. I'm also attaching the 'source'.
>
Ian Romanick schrieb:
Looking at the list, I noticed a couple of odd things. Why don't the
ATI drivers support GL_{ARB,EXT,NV}_texture_rectange or
GL_{ARB,EXT}_blend_equation_separate?
ATI sometimes makes strage decicions about the features their drivers
support: Even though the r200 could supp
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://freedesktop.org/bugzilla/show_bug.cgi?id=1501
Summary: libGL causes double free.
Product: DRI
Version: XO
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://freedesktop.org/bugzilla/show_bug.cgi?id=1501
--- Additional Comments From [EMAIL PROTECTED] 2004-09-30 11:53 ---
Created an
Mike Mestnik wrote:
Here is a straigth diff, I didn't do a udiff since I think we all know the
glxinfo output fairly well. I did make one change s/, $//g and s/, /\n
/g. I'm also attaching the 'source'.
A better way to get "meaningful" diffs is to pipe the output of glxinfo
to "grep GL_ | sed
Patch removes DRM flush, poll, read functions. It leave the fops entry
null so that the OS default function will be used.
The fops table is converted to be one per driver instead of a global.
This fixes the module open ref count problem. It also simplifies
i810/830 by allow them to directly patc
Mike Mestnik wrote:
First I was wondering what it would take, as far as bribes, to get at
least as far as the frglx drivers have with supporting this extension.
"Real" support for VBOs is yet another thing blocked on my memory
manager work. :(
-
On Thu, 2004-09-30 at 05:52, Mike Mestnik wrote:
> I'm interested in switching back and fourth, if any one has some info on
> doing this better I'd like to know. Right now I'm symlinking
> libGL-fglrx.so.1.2 or libGL-dri.so.1.2 into libGL.so.1.2. I also have to
> unload and load kmods too, I do t
Alan Cox wrote:
On Iau, 2004-09-30 at 13:56, Keith Whitwell wrote:
Looking in the i810 driver, it seems like the ringbuffer is flushed and
disabled until the X server calls EnterVT again, and AGP memory is
unbound. How is the client generally notified about this?
The server holds the hw lock until
On Iau, 2004-09-30 at 13:56, Keith Whitwell wrote:
> > Looking in the i810 driver, it seems like the ringbuffer is flushed and
> > disabled until the X server calls EnterVT again, and AGP memory is
> > unbound. How is the client generally notified about this?
>
> The server holds the hw lock until
> Thomas Hellström wrote:
>> Hi!
>>
>> How is VT switching normally handled when a DRI client is active?
>> Meaning, for example, switching from the X display to a virtual text
>> console?
>>
>> Looking in the i810 driver, it seems like the ringbuffer is flushed and
>> disabled until the X server c
Thomas Hellström wrote:
Hi!
How is VT switching normally handled when a DRI client is active?
Meaning, for example, switching from the X display to a virtual text console?
Looking in the i810 driver, it seems like the ringbuffer is flushed and
disabled until the X server calls EnterVT again, and AG
I'm interested in switching back and fourth, if any one has some info on
doing this better I'd like to know. Right now I'm symlinking
libGL-fglrx.so.1.2 or libGL-dri.so.1.2 into libGL.so.1.2. I also have to
unload and load kmods too, I do this by hand as well. I can go from DRI
to fglrx fine, bu
Hi!
How is VT switching normally handled when a DRI client is active?
Meaning, for example, switching from the X display to a virtual text console?
Looking in the i810 driver, it seems like the ringbuffer is flushed and
disabled until the X server calls EnterVT again, and AGP memory is
unbound. H
On Fr, 2004-09-24 at 14:49 +0200, Maurizio Monge wrote:
> Hello, it looks like that someone was able to
> use dri on AMD64 (with 64bits) on a G400
> (http://www.x86-64.org/lists/discuss/msg05271.html)
The message talks about G400 Max -- I don't know but maybe that's the
difference !?!?
> I tried
Philipp Klaus Krause wrote:
It seems you are using outdated drivers. The current DRI drivers support
about as much extensions as the nonfree ATI drivers.
GL_ARB_vertex_buffer_object is in both software Mesa and the r200
driver.
It should be noted though that ARB_vbo is a "fake" extension in the r20
Mike Mestnik schrieb:
I was playing with winex, after paying for some games and a TransGaming
subscription. In the cfg there are options to enable/disable the use of
some OpenGL extensions, one being ARB_VBO. I saw that when using frglx
there were some of these advertised by glxinfo, but not with
I was playing with winex, after paying for some games and a TransGaming
subscription. In the cfg there are options to enable/disable the use of
some OpenGL extensions, one being ARB_VBO. I saw that when using frglx
there were some of these advertised by glxinfo, but not with SW/Mesa or
R200/DRI.
On Tuesday 28 September 2004 18:03, Alex Deucher wrote:
> I think Nicolai has proven his competence as a coder, I think it'd be
> ok to give him mesa cvs access. it might be easier to develop in mesa
> cvs to keep synced up and such. Thoughts? I suppose you might want
> to wait till 6.2 is tagge
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://freedesktop.org/bugzilla/show_bug.cgi?id=1495
--- Additional Comments From [EMAIL PROTECTED] 2004-09-30 00:36 ---
Argh.
OK.
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://freedesktop.org/bugzilla/show_bug.cgi?id=1495
--- Additional Comments From [EMAIL PROTECTED] 2004-09-30 00:08 ---
Please try
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://freedesktop.org/bugzilla/show_bug.cgi?id=1394
[EMAIL PROTECTED] changed:
What|Removed |Added
32 matches
Mail list logo
