On Mon, May 13, 2002 at 06:01:14PM -0700, Mike Mestnik wrote:
>
> --- Micah Galizia <[EMAIL PROTECTED]> wrote:
> > Which source should i be modifying. The source available online at
> > http://www.xfree86.org/~alanh/ has radeon 1.1.1; however, when I made my
> > patch, it was against 1.2.0. I
--- Micah Galizia <[EMAIL PROTECTED]> wrote:
> Which source should i be modifying. The source available online at
> http://www.xfree86.org/~alanh/ has radeon 1.1.1; however, when I made my
> patch, it was against 1.2.0. I'm a little confused!
>
> Micah
>
I don't think at this time it would
--- Micah Galizia <[EMAIL PROTECTED]> wrote:
> No. I couldn't get it to compile under 2.4, but I think I was compiling
> against 2.5 headers. More importantly, where should I be getting source
> from? The source code at http://www.xfree86.org/~alanh/ is 1.1.1; Is
> that right?
That is the
Jens Owen wrote:
>Micah Galizia wrote:
>
>
>>I would love to contribute, and I'm more then willing to help with this
>>problem, however, I've only got a radeon, so I cant do too much testing
>>with anything else. At any rate, Lemmie know what needs to be done.
>>
>>
>
>Micah,
>
>Do the cha
Patch so that drivers compile under 2.5.x kernel :
--
Zilvinas Valinskas
--- drm_drv.h Mon May 13 01:23:49 2002
+++ ../drm/drm_drv.hSat May 4 15:22:30 2002
@@ -705,7 +705,7 @@
int i;
for (i = 0; i < DRM(numdevs); i++) {
- if (MINOR(inode->i_rdev) == DRM(mi
On Tue, May 14, 2002 at 01:04:46AM +0100, Jos? Fonseca wrote:
>
> > - for 2.5.x likewise, for which Micah patched the radeon kernel
> >
> >As of 2.5.9 the r128 driver looked identical to the 2.4.17 r128 driver.
> >If we can keep the source for converged between these two branches, that
> >wou
Which source should i be modifying. The source available online at
http://www.xfree86.org/~alanh/ has radeon 1.1.1; however, when I made my
patch, it was against 1.2.0. I'm a little confused!
Micah
___
Have big pipes? SourceForge.
On Tue, May 14, 2002 at 01:43:43AM +0200, Dieter Nützel wrote:
> If you've got a patch for me (against the trunk) I can throw same bigger 3D
> med apps on my V5 5500 AGP.
Ok, thanks, heres what I've been running, this is basically changing
assert() to ASSERT() across the board in texman.c and ch
Jens Owen wrote:
>Micah Galizia wrote:
>
>
>>I would love to contribute, and I'm more then willing to help with this
>>problem, however, I've only got a radeon, so I cant do too much testing
>>with anything else. At any rate, Lemmie know what needs to be done.
>>
>>
>
>Micah,
>
>Do the cha
On 2002.05.14 00:42 Jens Owen wrote:
> José Fonseca wrote:
> >...
> >
> > Nop, but who will do this? (I can't volunteer as I have no more spare
> time
> > until June.)
>
> Mike Mestnik has created this initial patch for testing. I hope Mike
> has the time to see this into kernel integration, but
Sorry, I found the "first" official in the German Heise news ticker (c't
magazine):
http://www.heise.de/newsticker/data/law-13.05.02-000/
Have fun.
--
Dieter Nützel
Graduate Student, Computer Science
University of Hamburg
Department of Computer Science
@home: [EMAIL PROTECTED]
On Mon, May 13, 2002 at 04:06:53PM -0400, Leif Delgass wrote:
> On Mon, 13 May 2002, Ian Romanick wrote:
>
> > On Sun, May 12, 2002 at 06:18:58PM -0400, Leif Delgass wrote:
> >
> > > In working on AGP texturing for mach64, I'm starting from the Rage128
> > > code, which seems to have some proble
Micah Galizia wrote:
>
> I would love to contribute, and I'm more then willing to help with this
> problem, however, I've only got a radeon, so I cant do too much testing
> with anything else. At any rate, Lemmie know what needs to be done.
Micah,
Do the changes you made work with the 2.4 kern
Keith wrote:
> Michael wrote:
> >
> > Looking at the tdfx driver texture stuff
[-]
> The texture memory management code in the tdfx driver is dark & mysterious.
> I don't know if anyone understands it any more... It's completely different
> to the other drivers and it's not really clear why. If
José Fonseca wrote:
>
> Jens,
>
> On 2002.05.13 14:58 Jens Owen wrote:
> > Jose,
> >
> > I recommend a full two way merge (DRI->kernel and kernel->DRI). The
> > kernel->DRI changes can be submitted directly to our repository for
> > testing. The DRI->kernel changes require a patch be submitted
José Fonseca wrote:
> I would be nice to know what is the current state of affairs?
I'll be happy to review the nitty gritty details...I'll post this to the
dri-devel list.
-- /\
Jens Owen/ \/\ _
[EMAIL PROTECTED] /\ \ \ Steamboat S
Hi all
I know, this is going to sound stupid in the list discussing textures,
mappings etc.. but I found another little buggy in the install.sh script
(in mach64 binary snapshots). This script moves existing binary objects
(for example, mach64.o) into dri-old prefix and restores them back when
as
Martin Spott wrote:
>
> On Thu, May 09, 2002 at 11:59:21AM -0700, Mike Mestnik wrote:
> > --- Martin Spott <[EMAIL PROTECTED]> wrote:
> > > [... Mike wrote ...]
>
> > > > I have a good start on a Linux DRM update. [...]
> > >
> > > > The patch is avaliable http://The Low Bandwidth Server
> > >
Eric Anholt wrote:
> I would like to see a form of OS-templated code get into CVS. If the
> rest of the DRI developers are interested in having this done, this is
> what I would like to happen:
>
> Step 1:
> - repocopy most of linux/drm/kernel/ to shared/drm/kernel (see below)
> - make the buil
On Monday 13 May 2002 16:50, Ian Romanick wrote:
> On Sun, May 12, 2002 at 11:08:47PM +0200, German Gomez Garcia wrote:
>
> > I would like to know if anybody was able to run Maya 4 on a
> > Matrox G400
> > using DRI, it seems that Maya only support 3DLabs and nVidia cards. Any
> > clue abo
Warning
Unable to process data:
multipart/mixed;boundary="=_NextPart_000_00D4_84A27C8B.D2345D21"
On Mon, 2002-05-13 at 16:13, Keith Whitwell wrote:
> Does the code you've linked implement these (or some of these) changes? Or is
> it the current bsd-only code. (I haven't looked at it yet)
>
> Keith
sending back to the group since I was probably unclear.
The linked code is the current OS-te
Eric Anholt wrote:
>
> As most of you know, I've been working on the BSD DRM for a year or so
> now. I've been working on the code based on bsd-2-0-0-branch, which
> uses C macros and ifdefs to deal with the differences between Linux and
> FreeBSD. To see the current state of the code checked i
As most of you know, I've been working on the BSD DRM for a year or so
now. I've been working on the code based on bsd-2-0-0-branch, which
uses C macros and ifdefs to deal with the differences between Linux and
FreeBSD. To see the current state of the code checked into FreeBSD CVS
(it's close to
Michael wrote:
>
> Looking at the tdfx driver texture stuff
>
> tdfxTMFindOldestObject
> does an assert ( t->range[0] ) which afaict is bogus, that's the
> point where it fails here running q3 with hardcoded 1mb of
> texture space.
>
> a) afaict assert()ing will
Looking at the tdfx driver texture stuff
tdfxTMFindOldestObject
does an assert ( t->range[0] ) which afaict is bogus, that's the
point where it fails here running q3 with hardcoded 1mb of
texture space.
a) afaict assert()ing will crash/hang the X server regardle
>
> I understand that, but my issue was that it's only freed when the heap
> fills up. If the global LRU card heap is full except for the last region,
> but the texture we're uploading is larger than that, we could end up
> switching to AGP memory, even if there was space no longer in use by
>
On Mon, 13 May 2002, Keith Whitwell wrote:
> Leif Delgass wrote:
> >
> > On Mon, 13 May 2002, Ian Romanick wrote:
> >
> > > On Sun, May 12, 2002 at 06:18:58PM -0400, Leif Delgass wrote:
> > >
> > > > In working on AGP texturing for mach64, I'm starting from the Rage128
> > > > code, which seems
Leif Delgass wrote:
>
> On Mon, 13 May 2002, Ian Romanick wrote:
>
> > On Sun, May 12, 2002 at 06:18:58PM -0400, Leif Delgass wrote:
> >
> > > In working on AGP texturing for mach64, I'm starting from the Rage128
> > > code, which seems to have some problems (though the texture aging problem
> >
Leif Delgass wrote:
>
> On Mon, 13 May 2002, Ian Romanick wrote:
>
> > On Sun, May 12, 2002 at 06:18:58PM -0400, Leif Delgass wrote:
> >
> > > In working on AGP texturing for mach64, I'm starting from the Rage128
> > > code, which seems to have some problems (though the texture aging problem
> >
On Mon, 13 May 2002, Ian Romanick wrote:
> On Sun, May 12, 2002 at 06:18:58PM -0400, Leif Delgass wrote:
>
> > In working on AGP texturing for mach64, I'm starting from the Rage128
> > code, which seems to have some problems (though the texture aging problem
> > could affect other drivers). My
Oops. Here's the attachment.
Jens Owen wrote:
>
> Frank,
>
> It would be a good thing if we can clarify what outstanding work can
> still be done on the DRI infrastructure itself. I've reorganized and
> added to our project "status" page (and attached to this e-mail). I
> kept the call for h
Frank,
It would be a good thing if we can clarify what outstanding work can
still be done on the DRI infrastructure itself. I've reorganized and
added to our project "status" page (and attached to this e-mail). I
kept the call for help at the top, and added a section called
"Outstanding Infrast
José Fonseca wrote:
>
> Jens,
>
> On 2002.05.13 14:58 Jens Owen wrote:
> > Jose,
> >
> > I recommend a full two way merge (DRI->kernel and kernel->DRI). The
> > kernel->DRI changes can be submitted directly to our repository for
> > testing. The DRI->kernel changes require a patch be submitted
Jens,
On 2002.05.13 14:58 Jens Owen wrote:
> Jose,
>
> I recommend a full two way merge (DRI->kernel and kernel->DRI). The
> kernel->DRI changes can be submitted directly to our repository for
> testing. The DRI->kernel changes require a patch be submitted to the
> kernel team. If we need two
On Mon, May 13, 2002 at 02:29:18AM +, Greg T Hill wrote:
> I posted this last month on the dri-users list in hopes that I was doing
> something wrong and would find out how to fix it. I eventually did fix it by
> installing a matrox g450, and everything works. This pretty well rules out
>
On Sun, May 12, 2002 at 06:18:58PM -0400, Leif Delgass wrote:
> In working on AGP texturing for mach64, I'm starting from the Rage128
> code, which seems to have some problems (though the texture aging problem
> could affect other drivers). My understanding is that textures in the
> global LRU a
On Sun, May 12, 2002 at 11:08:47PM +0200, German Gomez Garcia wrote:
> I would like to know if anybody was able to run Maya 4 on a
> Matrox G400
> using DRI, it seems that Maya only support 3DLabs and nVidia cards. Any
> clue
> about running it on a G400?
I believe that Maya also (offici
On Thu, May 09, 2002 at 11:59:21AM -0700, Mike Mestnik wrote:
> --- Martin Spott <[EMAIL PROTECTED]> wrote:
> > [... Mike wrote ...]
> > > I have a good start on a Linux DRM update. [...]
> >
> > > The patch is avaliable http://The Low Bandwidth Server
> > > /~cheako/linux-drm-4.2.0-kernel-2.4.
Warning
Unable to process data:
multipart/mixed;boundary="=_NextPart_000_00C4_76E22E4B.D3765E82"
Jose,
I recommend a full two way merge (DRI->kernel and kernel->DRI). The
kernel->DRI changes can be submitted directly to our repository for
testing. The DRI->kernel changes require a patch be submitted to the
kernel team. If we need two patches (for 2.4 and 2.5) that's okay--but
we should tr
Micah, this is a subject that although concerns Xpert list too it's more
appropriate to the dri-devel list.
Jens, I guess that we need to start hosting kernel patches for the
different linux versions. We also need to differentiate the patches that
should be applied against the linux kernel and
Mike,
On 2002.05.08 20:35 José Fonseca wrote:
> On 2002.05.08 20:03 Martin Spott wrote:
>> [... Mike wrote ...]
>> > I have a good start on a Linux DRM update. [...]
>>
>> > The patch is avaliable http://The Low Bandwidth Server
>> > /~cheako/linux-drm-4.2.0-kernel-2.4.18-patch.gz
>>
>> Has an
43 matches
Mail list logo
