On Mon, 2002-09-23 at 09:00, Michel Dänzer wrote:
> I've incorporated this and turned it into a template:
>
> http://penguinppc.org/~daenzer/DRI/drm-vblank-template.diff
I've put a new one up at
http://people.freebsd.org/~anholt/dri/files/framethrottle2.diff
which includes MGA support. I'll wo
>>>>> "Charl" == Charl P Botha <[EMAIL PROTECTED]> writes:
>> I've just check snapshot radeon-20020924 and same situation. I can run
>> programs except those which create new window.
>> For example:
>> xinit /usr/X11R6
Alan, Others,
I've been thinking again about pageflipping & realized I can solve the
remaining few problems if I can tweak the behaviour of the 2d driver slightly.
At the moment, the 2d driver always draws to buffer zero (the old front
buffer), and then at some point in the future, the dirty
On Tue, 2002-09-24 at 11:56, Adam Duck wrote:
> >>>>> "Charl" == Charl P Botha <[EMAIL PROTECTED]> writes:
>
> >> I've just check snapshot radeon-20020924 and same situation. I can run
> >> programs except those which create new
On Mon, 2002-09-23 at 19:35, Michel Dänzer wrote:
> On Mon, 2002-09-23 at 10:20, Alan Hourihane wrote:
> > On Sun, Sep 22, 2002 at 10:33:15 +0200, Michel Dänzer wrote:
> > >
> > > Several people on IRC reported crashes in the 2D code with the current
> > > trunk snapshots. I realized they are du
On Die, 2002-09-24 at 13:11, Keith Whitwell wrote:
>
> I've been thinking again about pageflipping & realized I can solve the
> remaining few problems if I can tweak the behaviour of the 2d driver slightly.
>
> At the moment, the 2d driver always draws to buffer zero (the old front
> buffer),
Michel Dänzer wrote:
> On Die, 2002-09-24 at 13:11, Keith Whitwell wrote:
>
>>I've been thinking again about pageflipping & realized I can solve the
>>remaining few problems if I can tweak the behaviour of the 2d driver slightly.
>>
>>At the moment, the 2d driver always draws to buffer zero (th
Hi guys. Yep, vacations ended.
I've updated my workstation to the RedHat Linux 7.3.94 beta, which has gcc 3.2. So now
forward the snapshots will be built with this version. AFAIK this shouldn't pose any
problem to the users since the key issue is that the kernel modules are compiled with
the s
On Sat, Aug 31, 2002 at 09:01:16AM -0600, Jens Owen wrote:
> It looks like there is some type of problem when the GL subdirectory is
> empty. Here's what the script tries to do when it get's to an empty GL
> portion of the install.
>
Ok. The problem is at:
echo -n " GL & GLU li
On Tue, Sep 24, 2002 at 02:19:24 +0100, Keith Whitwell wrote:
> Michel Dänzer wrote:
> >On Die, 2002-09-24 at 13:11, Keith Whitwell wrote:
> >
> >>I've been thinking again about pageflipping & realized I can solve the
> >>remaining few problems if I can tweak the behaviour of the 2d driver
> >>
Keith,
I'm looking to understand the behaviour I'm seeing since I installed
the main branch today.
With the default settings, and glxgears, I see:
r200CreateScreen
1077 frames in 5.0 seconds = 215.400 FPS
(Previously, I'd see around 300FPS for software rendering, and ~1500FPS for
TCL)
If I set
Jan Schmidt wrote:
> Keith,
>
> I'm looking to understand the behaviour I'm seeing since I installed
> the main branch today.
>
> With the default settings, and glxgears, I see:
> r200CreateScreen
> 1077 frames in 5.0 seconds = 215.400 FPS
>
> (Previously, I'd see around 300FPS for software ren
On Tue, Sep 24, 2002 at 02:49:37 +0100, Alan Hourihane wrote:
> On Tue, Sep 24, 2002 at 02:19:24 +0100, Keith Whitwell wrote:
> > Michel Dänzer wrote:
> > >On Die, 2002-09-24 at 13:11, Keith Whitwell wrote:
> > >
> > >>I've been thinking again about pageflipping & realized I can solve the
> > >>
> Why do you even care about software rasterization? In normal use the card
> basically never does this.
Only because I remember the numbers from when DRI has not been set up
properly, and I get suspicious when DRI runs slower than the software
rendering.
> There is code in the newest r200 dri
On Die, 2002-09-24 at 15:19, Keith Whitwell wrote:
> Michel Dänzer wrote:
> > On Die, 2002-09-24 at 13:11, Keith Whitwell wrote:
> >>
> >>I think all my problems can be solved if I do two things:
> >>1) always have X draw to the *current* front buffer (buffer zero or buffer
>one,
> >>depend
On Die, 2002-09-24 at 16:34, Michel Daenzer wrote:
> CVSROOT: /cvsroot/dri
> Module name: xc
> Repository: xc/xc/programs/Xserver/hw/xfree86/xaa/
> Changes by: mdaenzer@usw-pr-cvs1. 02/09/24 07:34:16
>
> Log message:
> * bump XAA minor and move new fields at the end of XAAInfoRec
>
Hi Jose
> I've updated my workstation to the RedHat Linux 7.3.94 beta, which has gcc 3.2. So
>now forward the snapshots will be built with this version. AFAIK this shouldn't pose
>any problem to the users since the key issue is that the kernel modules are compiled
>with the same version of gcc
> You can't change the offset in the chip or offscreen access goes after
> whatever buffer is front. You'd have to use coordinate deltas, but only
> if the coordinates are within the virtual resolution, and even then I'm
> not sure that would always work. Try and see I guess. :)
If so, it's a fu
>
> I missed that thread, actually... are you talking about the
> r200WaitForFrameCompletion one, or somewhere else?
Yes.
>
>>>So, I'm looking to understand why the standard glxgears now renders slower
>>>than software fallbacks used to, and why now when I use R200_NO_RAST I only
>>>see 50FP
On Tue, Sep 24, 2002 at 04:51:53PM +0200, Michel Dänzer wrote:
> On Die, 2002-09-24 at 16:34, Michel Daenzer wrote:
> > CVSROOT:/cvsroot/dri
> > Module name:xc
> > Repository: xc/xc/programs/Xserver/hw/xfree86/xaa/
> > Changes by: mdaenzer@usw-pr-cvs1. 02/09/24 07:34:16
> >
> > Log
On Die, 2002-09-24 at 16:59, Keith Whitwell wrote:
>
> > You can't change the offset in the chip or offscreen access goes after
> > whatever buffer is front. You'd have to use coordinate deltas, but only
> > if the coordinates are within the virtual resolution, and even then I'm
> > not sure that
On Die, 2002-09-24 at 16:58, Kevin E Martin wrote:
> On Tue, Sep 24, 2002 at 04:51:53PM +0200, Michel Dänzer wrote:
> > On Die, 2002-09-24 at 16:34, Michel Daenzer wrote:
> > > CVSROOT: /cvsroot/dri
> > > Module name: xc
> > > Repository: xc/xc/programs/Xserver/hw/xfree86/xaa/
> > > Ch
Michel Dänzer wrote:
> On Die, 2002-09-24 at 16:59, Keith Whitwell wrote:
>
>>>You can't change the offset in the chip or offscreen access goes after
>>>whatever buffer is front. You'd have to use coordinate deltas, but only
>>>if the coordinates are within the virtual resolution, and even then I
Alan Hourihane wrote:
> On Tue, Sep 24, 2002 at 02:49:37 +0100, Alan Hourihane wrote:
>
>>On Tue, Sep 24, 2002 at 02:19:24 +0100, Keith Whitwell wrote:
>>
>>>Michel Dänzer wrote:
>>>
On Die, 2002-09-24 at 13:11, Keith Whitwell wrote:
>I've been thinking again about pageflipping
Speaking of the new web site, could someone please remove the section
in the FAQ that says that various NDA'd documentation can be obtained
by becoming an XFree86 Project member.
Anyone who applies for XFree86 membership in order to obtain access to
NDA'd documentation will be rejected. The XFre
Michel Dänzer wrote:
> On Die, 2002-09-24 at 16:59, Keith Whitwell wrote:
>
>>>You can't change the offset in the chip or offscreen access goes after
>>>whatever buffer is front. You'd have to use coordinate deltas, but only
>>>if the coordinates are within the virtual resolution, and even then I
On Sun, Sep 22, 2002 at 10:33:15PM +0200, Michel Dänzer wrote:
> Several people on IRC reported crashes in the 2D code with the current
> trunk snapshots. I realized they are due to the TwoPoint acceleration
> functions depending on XAA changes. How can we handle this, bump the XAA
> version
Keith,
This should do it.
{
PixmapPtr pspix;
pspix = (*pScreen->GetScreenPixmap) (pScreen);
(*pScreen->ModifyPixmapHeader)(pspix, 0, 0, 0, 0, 0,
info->FB + XXXOFFSETX );
}
Alan.
---
Alan Hourihane wrote:
> Keith,
>
> This should do it.
>
> {
> PixmapPtr pspix;
> pspix = (*pScreen->GetScreenPixmap) (pScreen);
> (*pScreen->ModifyPixmapHeader)(pspix, 0, 0, 0, 0, 0,
> info->FB + XXXOFFSETX );
On Tue, Sep 24, 2002 at 05:06:13 +0100, Keith Whitwell wrote:
> Alan Hourihane wrote:
> >Keith,
> >
> >This should do it.
> >
> > {
> > PixmapPtr pspix;
> > pspix = (*pScreen->GetScreenPixmap) (pScreen);
> > (*pScreen->ModifyPixmapHeader)(pspix, 0, 0, 0, 0,
On Die, 2002-09-24 at 18:37, Alan Hourihane wrote:
> On Tue, Sep 24, 2002 at 05:06:13 +0100, Keith Whitwell wrote:
> > Alan Hourihane wrote:
> > >Keith,
> > >
> > >This should do it.
> > >
> > > {
> > > PixmapPtr pspix;
> > > pspix = (*pScreen->GetScreenPixmap
On Die, 2002-09-24 at 17:30, Jens Owen wrote:
> Michel Dänzer wrote:
> > On Die, 2002-09-24 at 16:59, Keith Whitwell wrote:
> >
> >>>You can't change the offset in the chip or offscreen access goes after
> >>>whatever buffer is front. You'd have to use coordinate deltas, but only
> >>>if the coor
On Die, 2002-09-24 at 17:55, Stephane Chauveau wrote:
> On Sun, Sep 22, 2002 at 10:33:15PM +0200, Michel Dänzer wrote:
> > Several people on IRC reported crashes in the 2D code with the current
> > trunk snapshots. I realized they are due to the TwoPoint acceleration
> > functions depending on
On Tue, Sep 24, 2002 at 06:43:32 +0200, Michel Dänzer wrote:
> On Die, 2002-09-24 at 18:37, Alan Hourihane wrote:
> > On Tue, Sep 24, 2002 at 05:06:13 +0100, Keith Whitwell wrote:
> > > Alan Hourihane wrote:
> > > >Keith,
> > > >
> > > >This should do it.
> > > >
> > > > {
> > > >
On Tue, Sep 24, 2002 at 05:06:13 +0100, Keith Whitwell wrote:
> Alan Hourihane wrote:
> >Keith,
> >
> >This should do it.
> >
> > {
> > PixmapPtr pspix;
> > pspix = (*pScreen->GetScreenPixmap) (pScreen);
> > (*pScreen->ModifyPixmapHeader)(pspix, 0, 0, 0, 0,
I noticed that some code from Mesa was recently folded into DRI to support
APPLE_client_storage. What does it take to enable that in a driver? Is it
like SGIS_generate_mipmaps in that the driver just needs to enable it?
On a related note, some time ago (on an IRC meeting, I think) there was som
On Die, 2002-09-24 at 19:10, Alan Hourihane wrote:
> On Tue, Sep 24, 2002 at 06:43:32 +0200, Michel Dänzer wrote:
> > On Die, 2002-09-24 at 18:37, Alan Hourihane wrote:
> > >
> > > If we code up 'WriteBitmap' and 'WritePixmap' which deals with
> > > pixmap cache loading and hook these into our _a
Ian Romanick wrote:
> I noticed that some code from Mesa was recently folded into DRI to support
> APPLE_client_storage. What does it take to enable that in a driver? Is it
> like SGIS_generate_mipmaps in that the driver just needs to enable it?
>
> On a related note, some time ago (on an IRC m
Howzit Frank?
> > Quite frankly (no pun intended) IRC logs are about the only thing out of
> > place, and when I look at that page I wonder if I should remove them,
> > however your idea to split documentation back out of help will draw
> > attention back to them on that page meaning they can be
> Howzit Frank?
>
> > Ok, I would remove CVS and IRC Logs from that page. They should
> > re-appear on the "Contribute" page.
> IRC is already gone, I'm leaving CVS there (for now at least) because
> is working on scripts to pull CVs, compile etc
Why do you need to leave the CVS information th
> > > Ok, I would remove CVS and IRC Logs from that page. They should
> > > re-appear on the "Contribute" page.
> > IRC is already gone, I'm leaving CVS there (for now at least) because
> > is working on scripts to pull CVs, compile etc
>
> Why do you need to leave the CVS information there?
>
> Speaking of the new web site, could someone please remove the section
> in the FAQ that says that various NDA'd documentation can be obtained
> by becoming an XFree86 Project member.
I'm sure someone could do that, could you point out where this is,
I'm certainly not about to read all the FAQ
> > Speaking of the new web site, could someone please remove the section
> > in the FAQ that says that various NDA'd documentation can be obtained
> > by becoming an XFree86 Project member.
>
> I'm sure someone could do that, could you point out where this is,
> I'm certainly not about to read
> > Speaking of the new web site, could someone please remove the section
> > in the FAQ that says that various NDA'd documentation can be obtained
> > by becoming an XFree86 Project member.
>
> I'm sure someone could do that, could you point out where this is,
> I'm certainly not about to read
All our mailings are sent complying to the proposed H.R. 3113 Unsolicited Commercial
Electronic Mail Act of 2000. Please see the bottom of this message for further
information and removal instructions.
PARENTS OF 15 - YEAR OLD - FIND $71,000 CASH HIDDEN IN HIS CLOSET!
Does this headline lo
Hello Keith,
your last r200 merge disabled the build of all other drivers. I think the
problem cis in lib/GL/mesa/src/drv/Imakefile:
>> #SUBDIRS = common DriDrivers
>> SUBDIRS = common r200 radeon
Greetings
Marc
--
Marc Dietrich
"Help yourself or Mic
Oh, now that's even more annoying than SPAM usually is!
Here I was thinking that someone was going to announce that NVidia
decided to support open source or that the texture compression pattent
was going to be opened to the DRI group or *something* cool.
*sigh*
Cheers,
David
David Willmore wrote:
> Oh, now that's even more annoying than SPAM usually is!
>
> Here I was thinking that someone was going to announce that NVidia
> decided to support open source or that the texture compression pattent
> was going to be opened to the DRI group or *something* cool.
>
> *sigh
On Die, 2002-09-24 at 10:08, Eric Anholt wrote:
> On Mon, 2002-09-23 at 09:00, Michel Dänzer wrote:
>
> > I've incorporated this and turned it into a template:
> >
> > http://penguinppc.org/~daenzer/DRI/drm-vblank-template.diff
>
> I've put a new one up at
> http://people.freebsd.org/~anholt/d
On Tue, 2002-09-24 at 17:08, Michel Dänzer wrote:
> On Die, 2002-09-24 at 10:08, Eric Anholt wrote:
> > On Mon, 2002-09-23 at 09:00, Michel Dänzer wrote:
> >
> > > I've incorporated this and turned it into a template:
> > >
> > > http://penguinppc.org/~daenzer/DRI/drm-vblank-template.diff
> >
On Mit, 2002-09-25 at 03:52, Eric Anholt wrote:
> On Tue, 2002-09-24 at 17:08, Michel Dänzer wrote:
> >
> > BTW is there any reason why the mga stuff can't move to the shared DRM
> > directory?
>
> Which mga stuff? MGA is shared about as much as the other drivers.
Hmm, I think I confused mga a
Warning
Unable to process data:
multipart/mixed;boundary="=_NextPart_000_00D7_80C51D6A.A5835A82"
52 matches
Mail list logo
