On Tue, May 21, 2002 at 12:14:45AM +0100, Keith Whitwell wrote:
> I have a .XF86config-radeon that sets ModulesPath to that directory, and maybe
> I need to set an env var or two... I guess the magic is adding up.
Yeah, I should have rtfm'd, ModulesPath into .../exports/lib/modules
fixes it, tha
Michael wrote:
>
> On Mon, May 20, 2002 at 04:46:41PM +0100, Keith Whitwell wrote:
> > Michael,
> >
> > I've added some code in the DDX driver to keep the back buffer uptodate so
> > that the 'flicker' is gone, and pageflipping looks just like normal
> > swapbuffers.
> >
> > I've done this with t
On Mon, May 20, 2002 at 04:46:41PM +0100, Keith Whitwell wrote:
> Michael,
>
> I've added some code in the DDX driver to keep the back buffer uptodate so
> that the 'flicker' is gone, and pageflipping looks just like normal
> swapbuffers.
>
> I've done this with the miext/shadow module keeping t
--- Michael <[EMAIL PROTECTED]> wrote:
> Can we repair the damage? That doesn't seem to have been that successful
> in the past in terms of recovery / carrying on running the 3d app -
> others have more knowledge here. If anything, cleanly exiting from 3d
> and, if recovery is possible or the 2d
On Mon, May 20, 2002 at 01:27:39PM -0700, Mike Mestnik wrote:
> Now I'd like to tackel another problem, Quake3 is blocked durring this pause
> (sometimes a long pause) This could result in poor sound and more inportantly
> keybord performance. I don't know how to fix this withought using fork. S
Just to remind that the IRC meeting will be held at the usual time, 4:00pm
EST (2100h UTC), i.e., 5 min.
José Fonseca
___
Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.spr
--- Michael <[EMAIL PROTECTED]> wrote:
> What is the problem you're trying to fix?
>
> --
> Michael.
"Incroment 2Was Not Idle!"
See how the fprintf call was interupted.
I found ought after some testing that there is a set amount of bytes that can
be put into the buffer. Being less verbose fix
On Mon, May 20, 2002 at 07:44:11PM +0100, José Fonseca wrote:
> In what way could this affect the DRI Radeon development if it holds true?
> I suppose that some DRI developers already have some form of the source
> code as part of a SDK, so I don't know if it has any relevance.
I saw an interview
In the recent SlashDot interview to Alan Cox, the close/openness of NVidia
drivers was briefly discussed.
In one of the threads a anonymous claiming to be a former ATI employee
defending the company mentioned that the next Direct3D sample driver
source will be Radeon based. You can read it here
h
On Mon, 2002-05-20 at 03:44, Keith Whitwell wrote:
> Is your latest code available somewhere?
The latest code is still at:
http://gladstone.uoregon.edu/~eanholt/dri/sysdrm-2002-05-13.tar.gz
(Haven't worked on it for a bit, waiting for decisions on what's going
to happen with it).
--
Eric Anholt <
On Mon, May 20, 2002 at 05:15:25PM +0100, José Fonseca wrote:
> Jan,
>
> On 2002.05.20 16:42 Jan Schmidt wrote:
> >
> >
> > > On 2002.05.20 12:30 Martin Spott wrote:
> > > >As this _is_ a FAQ it's already listet in the appropriate document.
> > > >Wonder
> > > >how it is called, this document ?
On Sat, 18 May 2002, Felix Kühling wrote:
> On Sat, 18 May 2002 11:30:28 -0400 (EDT)
> Leif Delgass <[EMAIL PROTECTED]> wrote:
>
> > Did you have a 2D accelerated server running on another vt? The DDX saves
> > and restores its register state on mode switches, so it could be a problem
> > with
Jan,
On 2002.05.20 16:42 Jan Schmidt wrote:
>
>
> > On 2002.05.20 12:30 Martin Spott wrote:
> > >As this _is_ a FAQ it's already listet in the appropriate document.
> > >Wonder
> > >how it is called, this document ? We call it "FAQ".
> > >
> >
> > There are two FAQs documents in the DRI website
Michael wrote:
>
> On Sun, Mar 10, 2002 at 10:44:00PM +, Keith Whitwell wrote:
> > Nice. How kludged is kludged?
>
> Attached.
>
> Most of it is just uncommenting what's already there, and adding a call
> (probably in the wrong place as MakeCurrent seems to be called a lot,
> hence the che
> On 2002.05.20 12:30 Martin Spott wrote:
> >As this _is_ a FAQ it's already listet in the appropriate document.
> >Wonder
> >how it is called, this document ? We call it "FAQ".
> >
>
> There are two FAQs documents in the DRI website. This question it's
> addressed in the "Developer's FAQ"
>
On Sun, May 19, 2002 at 11:20:53PM -0700, Mike Mestnik wrote:
> The problem is less noticeable in vanilla quake3.
What is the problem you're trying to fix?
--
Michael.
___
Hundreds of nodes, one monster rendering program.
Now that's a
On Mon, May 20, 2002 at 03:22:52PM +0100, Keith Whitwell wrote:
>
> > > I've got some time to take a look at this over the next couple of days. It
> > > really depends how big the differences are - but probably we need to come up
> > > with a way of doing things without too much #ifdef crud in t
On Mon, 20 May 2002 13:38:48 +0100
José Fonseca <[EMAIL PROTECTED]> wrote:
>
> There are two FAQs documents in the DRI website. This question it's
> addressed in the "Developer's FAQ"
> (http://dri.sourceforge.net/doc/faq/hardware.html#RADEON-8500-PLANS),
> which perhaps isn't as straightforw
> > I've got some time to take a look at this over the next couple of days. It
> > really depends how big the differences are - but probably we need to come up
> > with a way of doing things without too much #ifdef crud in the main code --
> > whether this means we need an abstraction layer, mor
Keith Whitwell wrote:
>
> Eric Anholt wrote:
> >
> > On Mon, 2002-05-13 at 16:59, Jens Owen wrote:
> > > Eric,
> > >
> > > The watermark I would apply for measuring the success of OS-templating
> > > is device indepedence. If all device specific code can go into the
> > > shared/drm/kernel direc
On 2002.05.20 12:30 Martin Spott wrote:
> > I'm just wondering how the development for this chip is coming along?
> > I'm planning on getting the 7500 but if dri support for the 8500 is far
> > enough along I will wait.
>
> As this _is_ a FAQ it's already listet in the appropriate document.
> Won
> I'm just wondering how the development for this chip is coming along?
> I'm planning on getting the 7500 but if dri support for the 8500 is far
> enough along I will wait.
As this _is_ a FAQ it's already listet in the appropriate document. Wonder
how it is called, this document ? We call it "FA
Eric Anholt wrote:
>
> On Mon, 2002-05-13 at 16:59, Jens Owen wrote:
> > Eric,
> >
> > The watermark I would apply for measuring the success of OS-templating
> > is device indepedence. If all device specific code can go into the
> > shared/drm/kernel directory and only device independent code is
On Mon, 2002-05-13 at 16:59, Jens Owen wrote:
> Eric,
>
> The watermark I would apply for measuring the success of OS-templating
> is device indepedence. If all device specific code can go into the
> shared/drm/kernel directory and only device independent code is found in
> the OS specific dire
On 2002.05.16 21:37 José Fonseca wrote:
> ... I'm gonna devise a test for that: it will monitor the BM_GUI_TABLE
> value and change the value at the last moment (like waiting for the
> train to come to cross the line!)
>
> ...
Here is the commented output of such a test that waits for the card
25 matches
Mail list logo
