Based on Alex Deucher's recent request to test the
Savage driver he and Felix have been working on, I
recently pulled the savage-2-0-0-branch and compiled
the driver for testing.
My configuration is Fedora Core 1, AMD Athlon 2200,
512 MB, ProsavageDDR in a Shuttle SK41G.
My results have been good
Dieter Nützel wrote:
Am Freitag, 16. Januar 2004 20:00 schrieb Roland Scheidegger:
ok, here's another attempt, which uses an external dxtn library (patch
against current Mesa cvs trunk).
And, again? - After texture merge.
since you've asked ;-)
fixes:
- the dlopen stuff will no longer be built
the i810 got broken by the texture changes over the last few days, the
imesa->i810Screen pointer wasn't setup before the call to
mesa_create_context and it in turn called i810SetTexFilter which used
IS_I815 which used i810Screen, I've checked in a fix (I've just moved all
the pointer assignments b
On Tue, Jan 27, 2004 at 08:41:45PM +, Keith Whitwell wrote:
> What I'd really like to be able to do now is build the dri drivers directly
> out of the Mesa tree.
Does this means that finally we will see XFree and linux-solo build
it's drivers from Mesa-newtree/src/drivers/dri or this is not t
On Wed, Jan 14, 2004 at 01:39:39PM +, Alan Cox wrote:
>I think this is about the minimal fix needed. I'm not entirely happy
>with the limits picked, especially for spans, but maybe someone with
>an R128 can verify it is ok, or change the code to loop each chunk
>of pixels/span data.
I've attac
Sorry for the spam, but I forgot another thing:
in r200UploadRectSubImage, shouldn't r200AllocDmaRegion just call for a
1024 byte alignment (since the blit offset looks like it needs to be
1024 byte aligned)? That'll get rid of the failed assertion with texrect
when using 16bit textures - the ra
(since the original email never made it to the list, a new one - it's
not a resend though)
texrect is broken here (and I've no idea why it works for other people ;-)).
There are 2 problems in the driver which cause this:
First, if glGenTextures is called, there is no texture target yet. This
wil
>
> If anyone complains of getting the following errors at startx:
>
> mtrr: 0xf800,0x200 overlaps existing 0xf800,0x100
> mtrr: 0xf800,0x200 overlaps existing 0xf800,0x100
> [drm:radeon_cp_init] *ERROR* radeon_cp_init called without lock held
> [drm:radeon_unlock]
I've built DRI CVS along with Mesa CVS to get test my IGP340M on the 2.6.1
kernel. I'd like to report success. Note: this chipset has no TCL.
glinfo (I cut GL_EXTENSIONS from here):
disabling TCL support
GL_VERSION: 1.2 Mesa 6.1
GL_RENDERER: Mesa DRI Radeon 20030328 AGP 4x x86/MMX/SSE2 NO-TCL
GL_
uilding shared library /opt/VTK/V4.0/VTK/bin/libvtkParallelJava.so...
Building shared module /opt/VTK/V4.0/VTK/bin/libvtkParallelPython.so...
Building shared library /opt/VTK/V4.0/VTK/bin/libvtkParallelTCL.so...
./Wrapping/Tcl: building default_target
Building dependencies. cmake.depends...
Buildin
Just for fun, tried all mesa demos/tests etc. with a radeon 7200 sdr.
redbook/alpha3d: nothing is seen unless a is pressed (and then only for
a very short time, buffering problem? (same as with r200)
samples/fog: the red part seems to have the fog applied quite
differently than with software me
On Wed, 2004-01-28 at 00:28, Alan Hourihane wrote:
> On Wed, Jan 28, 2004 at 12:25:23AM +0100, Michel DÃnzer wrote:
> >
> > What about a branch corresponding to the Mesa stable branch though?
> > Then David could grab that for XFree86.
>
> It's currently mesa_6_0_branch.
Yes, I mean a corresp
On Wed, Jan 28, 2004 at 12:25:23AM +0100, Michel Dänzer wrote:
> On Tue, 2004-01-27 at 21:41, Keith Whitwell wrote:
> > Alan Hourihane wrote:
> > >
> > > Do we want to bring Mesa 6.0's branch into the DRI repository now or
> > > stick with the way we have it currently ?
> > >
> > > I guess if we
On Tue, 2004-01-27 at 21:41, Keith Whitwell wrote:
> Alan Hourihane wrote:
> >
> > Do we want to bring Mesa 6.0's branch into the DRI repository now or
> > stick with the way we have it currently ?
> >
> > I guess if we stick with the way it is now, then most developers will
> > track Mesa's trun
On Tue, Jan 27, 2004 at 01:17:20PM -0800, Alex Deucher wrote:
>
> --- Alan Hourihane <[EMAIL PROTECTED]> wrote:
> > On Tue, Jan 27, 2004 at 07:38:59PM +, Keith Whitwell wrote:
> > > This is a good time to remind people/establish the principle that
> > driver
> > > bug fixes should be propogat
On Tue, Jan 27, 2004 at 07:52:32PM +, Alan Hourihane wrote:
>On Tue, Jan 27, 2004 at 02:21:42PM -0500, David Dawes wrote:
>> On Tue, Jan 27, 2004 at 06:45:10PM +, Alan Hourihane wrote:
>> >On Tue, Jan 27, 2004 at 12:37:51PM -0500, David Dawes wrote:
>> >> There are quite a few Radeon-relate
--- Alan Hourihane <[EMAIL PROTECTED]> wrote:
> On Tue, Jan 27, 2004 at 07:38:59PM +, Keith Whitwell wrote:
> > This is a good time to remind people/establish the principle that
> driver
> > bug fixes should be propogated to the mesa-6_0_branch of the Mesa
> > repository. Brian's always done
Alan Hourihane wrote:
What I'd really like to be able to do now is build the dri drivers directly
out of the Mesa tree.
Definately. Slate that up for 6.1, I'll certainly work on that issue.
It's not too hard - I had it working on the embedded branch a while ago.
In general, the Mesa make syst
On Tue, Jan 27, 2004 at 08:41:45PM +, Keith Whitwell wrote:
> Alan Hourihane wrote:
> >On Tue, Jan 27, 2004 at 07:38:59PM +, Keith Whitwell wrote:
> >
> >>This is a good time to remind people/establish the principle that driver
> >>bug fixes should be propogated to the mesa-6_0_branch of t
On Wed, 2004-01-21 at 22:57, Marco van Zwetselaar wrote:
> Michel Daenzer wrote:
> > Ariel Garcia wrote:
> > > both on my desktop and my laptop i am getting strange hangs
> > > when running XFree packages (both debian testing/unstable,
> > > 4.2.1-{12.1,15}) with the newer linux kernels. This h
Alan Hourihane wrote:
On Tue, Jan 27, 2004 at 07:38:59PM +, Keith Whitwell wrote:
This is a good time to remind people/establish the principle that driver
bug fixes should be propogated to the mesa-6_0_branch of the Mesa
repository. Brian's always done a good job of making sure core mesa fix
On Tue, Jan 27, 2004 at 07:38:59PM +, Keith Whitwell wrote:
> This is a good time to remind people/establish the principle that driver
> bug fixes should be propogated to the mesa-6_0_branch of the Mesa
> repository. Brian's always done a good job of making sure core mesa fixes
> get copied
On Tue, Jan 27, 2004 at 02:21:42PM -0500, David Dawes wrote:
> On Tue, Jan 27, 2004 at 06:45:10PM +, Alan Hourihane wrote:
> >On Tue, Jan 27, 2004 at 12:37:51PM -0500, David Dawes wrote:
> >> There are quite a few Radeon-related bugs still outstanding in
> >> bugs.xfree86.org, including several
David Dawes wrote:
On Tue, Jan 27, 2004 at 06:45:10PM +, Alan Hourihane wrote:
On Tue, Jan 27, 2004 at 12:37:51PM -0500, David Dawes wrote:
There are quite a few Radeon-related bugs still outstanding in
bugs.xfree86.org, including several related to DRI lockups.
Has anyone followed them up?
D
On Tue, Jan 27, 2004 at 06:45:10PM +, Alan Hourihane wrote:
>On Tue, Jan 27, 2004 at 12:37:51PM -0500, David Dawes wrote:
>> There are quite a few Radeon-related bugs still outstanding in
>> bugs.xfree86.org, including several related to DRI lockups.
>>
>> Has anyone followed them up?
>
>David
On Tue, Jan 27, 2004 at 12:37:51PM -0500, David Dawes wrote:
> There are quite a few Radeon-related bugs still outstanding in
> bugs.xfree86.org, including several related to DRI lockups.
>
> Has anyone followed them up?
David,
I suspect not with XFree86's DRI drivers still being based on Mesa 4
On Fri, 2004-01-23 at 03:45, Michel DÃnzer wrote:
> On Fri, 2004-01-23 at 02:28, Michel DÃnzer wrote:
> >
> > [...] (works with current libGL):
>
> Actually, most if not all textured apps spew
>
> [driAllocateTexture:577] unable to allocate texture
>
> all over the place and seem to fall back t
There are quite a few Radeon-related bugs still outstanding in
bugs.xfree86.org, including several related to DRI lockups.
Has anyone followed them up?
David
--
David Dawes
developer/release engineer The XFree86 Project
www.XFree86.org/~dawes
--
On Mon, 26 Jan 2004 16:03:02 -0800 (PST)
Linus Torvalds <[EMAIL PROTECTED]> wrote:
>
> On Mon, 26 Jan 2004, Felix Kühling wrote:
> >
> > after a CVS upgrade last night I got two some assertions in the radeon
> > driver. One happened when exiting from glxgears in radeonDeleteTexture.
> > Commenti
hello,
I don't know if it's the right place to ask but I have a small question:
My kernel is compiled with gcc-2.95.3 (as recommanded in the kernel README).
Isn't it better to compile X with the same gcc version? especially because the
kernel will load the module radeon.o (for example).
If so how
On Sat, 2004-01-24 at 15:28, Keith Whitwell wrote:
> Michel DÃnzer wrote:
> > On Fri, 2004-01-23 at 03:45, Michel DÃnzer wrote:
> >
> >>On Fri, 2004-01-23 at 02:28, Michel DÃnzer wrote:
> >>
> >>[...] most if not all textured apps spew
> >>
> >>[driAllocateTexture:577] unable to allocate texture
>
31 matches
Mail list logo
