Brian Paul wrote:
I'll be checking in the merge soon. I'm just doing a second build to
double-check everything. Testing is going good so far.
OK, the merge is done.
-Brian
---
This SF.net email is sponsored by: Get the new Palm Tungsten
I'll be checking in the merge soon. I'm just doing a second build to
double-check everything. Testing is going good so far.
-Brian
---
This SF.net email is sponsored by: Get the new Palm Tungsten T
handheld. Power & Color in a compact size
Brian Paul wrote:
Michel Dänzer wrote:
On Mon, 2002-11-25 at 17:15, Brian Paul wrote:
I'm trying to decide when to merge the mesa-41 branch into the trunk.
People have reported a number of problems, but for the most part, they
seem to be present in the trunk as well.
At this time, the only d
Michel Dänzer wrote:
On Mon, 2002-11-25 at 17:15, Brian Paul wrote:
I'm trying to decide when to merge the mesa-41 branch into the trunk.
People have reported a number of problems, but for the most part, they
seem to be present in the trunk as well.
At this time, the only differences between t
On Mon, 25 Nov 2002, Brian Paul wrote:
>
> It might make sense to merge to the trunk soon so that there's one code
> base to focus on. Everyone seems to want the mesa-41 work to get into
> XFree86 4.3.
>
> What do people think?
I say go for it.
If we can get it into the trunk then it will be
On Mon, 2002-11-25 at 17:15, Brian Paul wrote:
> I'm trying to decide when to merge the mesa-41 branch into the trunk.
>
> People have reported a number of problems, but for the most part, they
> seem to be present in the trunk as well.
>
> At this time, the only differences between the trunk and
On Mon, Nov 25, 2002 at 09:15:59AM -0700, Brian Paul wrote:
> It might make sense to merge to the trunk soon so that there's one code
> base to focus on.
That seems like a very good call. I'd also like to get mesa-41 merged so
that I can bring it into the texmem branch.
> Everyone seems to want
I'm trying to decide when to merge the mesa-41 branch into the trunk.
People have reported a number of problems, but for the most part, they
seem to be present in the trunk as well.
At this time, the only differences between the trunk and branch server
code is in the indirect GLX rendering code.
On Sat, 23 Nov 2002 19:47:35 -0500
Garry Reisky <[EMAIL PROTECTED]> wrote:
> Switching resolutions in quake 3 based games seems to cause some
> problems. Also switching from fullscreen to windowed mode causes the
> same effect. I've tried q3a, wolfenstein, ut, fakk2. They all do the
> same thing f
That file is symlinked from xf86ScanPci.c, it shouldn't exist.
Do a clean checkout.
Alan.
On Fri, Nov 22, 2002 at 02:37:35PM +0100, Dieter Nützel wrote:
> M xc/programs/Xserver/hw/xfree86/scanpci/xf86PciData.c
>
> But latest version. The "current" is much older.
>
> /* $XFree86: xc/programs/Xs
> I just ran FlightGear with this branch (instead of employing binary
> snapshots) on my Radeon7500. Everything is quite fast, the colours look
> perfect, the previously known feature of everything appearing too dark has
> gone !
Hmmm, today I had to realize that this is still dependend on the
Hi!
I've done some more testing on the mesa-4-1-branch (checked out and
compiled yesterday)
All in all everything runs quite nicely and stable. I successfully tested:
-quake (quakeforge-0.5.2): works, but quite sluggish, especially when
there are lots of light effects
-quake2 (quakeIIforge 0.1
On Mit, 2002-11-20 at 22:04, Martin Spott wrote:
> Brian wrote:
> > Adam K Kirchhoff wrote:
> >> So I decided to give the mesa-4-1-branch a whirl and do some testing... I
> >> grabbed it from CVS:
> >>
> >> $ cvs -z3 co -r mesa-4-1-branch xc
>
> > Do a CVS update again in case you didn't get my
On Mit, 2002-11-20 at 16:56, Adam K Kirchhoff wrote:
> On 20 Nov 2002, Michel [ISO-8859-1] Dänzer wrote:
>
> > On Mit, 2002-11-20 at 00:38, Adam K Kirchhoff wrote:
> > >
> > > heretic2 has some problems, but they also show up in the trunk :-)
> > > Basically, any sort of flashing (like if my chara
Brian wrote:
> Adam K Kirchhoff wrote:
>> So I decided to give the mesa-4-1-branch a whirl and do some testing... I
>> grabbed it from CVS:
>>
>> $ cvs -z3 co -r mesa-4-1-branch xc
> Do a CVS update again in case you didn't get my latest check-ins.
I just ran FlightGear with this branch (instea
On 20 Nov 2002, Michel [ISO-8859-1] Dänzer wrote:
> On Mit, 2002-11-20 at 00:38, Adam K Kirchhoff wrote:
> >
> > heretic2 has some problems, but they also show up in the trunk :-)
> > Basically, any sort of flashing (like if my character throws a fireball),
> > causes a huge drop in the framerate
On Mit, 2002-11-20 at 00:38, Adam K Kirchhoff wrote:
>
> heretic2 has some problems, but they also show up in the trunk :-)
> Basically, any sort of flashing (like if my character throws a fireball),
> causes a huge drop in the framerate.
It uses the Quake 2 engine, right? As has been discus
On Tue, 19 Nov 2002, Brian Paul wrote:
> Adam K Kirchhoff wrote:
> > Alright, after clearing out my local copy of the mesa-4.1 branch, I pulled
> > everything again and was able to build that branch without any problems.
> >
> > I've done some basic testing so far.
> >
> > This is on a dua
Adam K Kirchhoff wrote:
Alright, after clearing out my local copy of the mesa-4.1 branch, I pulled
everything again and was able to build that branch without any problems.
I've done some basic testing so far.
This is on a dual proc, 1ghz., PIII. Via chipset. 2x AGP, 64 meg
aperature. 512
Adam K Kirchhoff wrote:
> On Tue, 19 Nov 2002, Brian Paul wrote:
>
>
>>Adam K Kirchhoff wrote:
>>
>>>So I decided to give the mesa-4-1-branch a whirl and do some
testing... I
>>>grabbed it from CVS:
>>>
>>>$ cvs -z3 co -r mesa-4-1-branch xc
>>>
>>>And then I did a Make world. Unfortunately, it di
Hold on a sec. I've got too many different branches of the DRI on my
machine (the texmem branch, the mesa-4.1 branch, and the trunk) so now I'm
beginning to second guess what I've updated and what I haven't.
I'm gonna clean everything off and do a fresh pull of the mesa-4.1 branch.
Adam
On Tue
On Tue, 19 Nov 2002, Brian Paul wrote:
> Adam K Kirchhoff wrote:
> > On Tue, 19 Nov 2002, Brian Paul wrote:
> >
> >
> >>Adam K Kirchhoff wrote:
> >>
> >>>So I decided to give the mesa-4-1-branch a whirl and do some testing... I
> >>>grabbed it from CVS:
> >>>
> >>>$ cvs -z3 co -r mesa-4-1-bran
Alan Hourihane wrote:
On Tue, Nov 19, 2002 at 01:04:54PM -0500, Adam K Kirchhoff wrote:
On Tue, 19 Nov 2002, Brian Paul wrote:
Adam K Kirchhoff wrote:
So I decided to give the mesa-4-1-branch a whirl and do some testing... I
grabbed it from CVS:
$ cvs -z3 co -r mesa-4-1-branch xc
And the
On Tue, Nov 19, 2002 at 01:04:54PM -0500, Adam K Kirchhoff wrote:
>
> On Tue, 19 Nov 2002, Brian Paul wrote:
>
> > Adam K Kirchhoff wrote:
> > > So I decided to give the mesa-4-1-branch a whirl and do some testing... I
> > > grabbed it from CVS:
> > >
> > > $ cvs -z3 co -r mesa-4-1-branch xc
>
Adam K Kirchhoff wrote:
On Tue, 19 Nov 2002, Brian Paul wrote:
Adam K Kirchhoff wrote:
So I decided to give the mesa-4-1-branch a whirl and do some testing... I
grabbed it from CVS:
$ cvs -z3 co -r mesa-4-1-branch xc
And then I did a Make world. Unfortunately, it didn't get very far:
mak
On Tue, 19 Nov 2002, Brian Paul wrote:
> Adam K Kirchhoff wrote:
> > So I decided to give the mesa-4-1-branch a whirl and do some testing... I
> > grabbed it from CVS:
> >
> > $ cvs -z3 co -r mesa-4-1-branch xc
> >
> > And then I did a Make world. Unfortunately, it didn't get very far:
> >
>
Heh.. I actually noticed it a couple days ago on the texmem branch, but I
figured that I was doing something odd/wrong. Guess not :-)
Adam
On Tue, 19 Nov 2002, Urs Schroffenegger wrote:
> Well, I didn't find what's wrong, but i encountered exactly the same
> thing at exactly the same point (
Adam K Kirchhoff wrote:
So I decided to give the mesa-4-1-branch a whirl and do some testing... I
grabbed it from CVS:
$ cvs -z3 co -r mesa-4-1-branch xc
And then I did a Make world. Unfortunately, it didn't get very far:
make[5]: Entering directory `/home/adamk/mesa-4.1-branch/xc/xc/programs
28 matches
Mail list logo
