[Bug 13438] request commit access

http://bugs.freedesktop.org/show_bug.cgi?id=13438 --- Comment #2 from [EMAIL PROTECTED] 2007-11-28 21:13 PST --- Created an attachment (id=12819) --> (http://bugs.freedesktop.org/attachment.cgi?id=12819&action=view) gpg key -- Configure bugmail: http://bugs.freedesktop.org/userpre

[Bug 13438] request commit access

http://bugs.freedesktop.org/show_bug.cgi?id=13438 --- Comment #1 from [EMAIL PROTECTED] 2007-11-28 21:12 PST --- Created an attachment (id=12818) --> (http://bugs.freedesktop.org/attachment.cgi?id=12818&action=view) ssh key -- Configure bugmail: http://bugs.freedesktop.org/userpre

[Bug 13438] New: request commit access

http://bugs.freedesktop.org/show_bug.cgi?id=13438 Summary: request commit access Product: DRI Version: XOrg CVS Platform: Other OS/Version: FreeBSD Status: NEW Severity: normal Priority: medium Component: D

[Bug 13091] glean abort with "Segmentation fault" in GarbageCollectDRIDrawables

http://bugs.freedesktop.org/show_bug.cgi?id=13091 [EMAIL PROTECTED] changed: What|Removed |Added Status|RESOLVED|VERIFIED --- Comment #7 from [

[Bug 10002] problem 915gm with texturized video

http://bugs.freedesktop.org/show_bug.cgi?id=10002 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution|

[Bug 13427] Fix bsd build with drm_ati_pcigart_info

http://bugs.freedesktop.org/show_bug.cgi?id=13427 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution|

Re: Clip Lists

Keith Packard <[EMAIL PROTECTED]> writes: > On Wed, 2007-11-28 at 06:19 +0100, Soeren Sandmann wrote: > > > - When a client wishes to copy something to the frontbuffer (for > > whatever reason - glXSwapBuffers(), glCopyPixels(), etc), it uses > > plain old XCopyArea() with the generated pixma

Re: DRI2 and lock-less operation

On Nov 28, 2007 6:15 AM, Stephane Marchesin <[EMAIL PROTECTED]> wrote: > On 11/28/07, Keith Packard <[EMAIL PROTECTED]> wrote: > > On Wed, 2007-11-28 at 00:52 +0100, Stephane Marchesin wrote: > > > > > The third case obviously will never require any kind of state > > > re-emitting. > > > > Unless y

Re: DRI2 and lock-less operation

On Wed, 2007-11-28 at 15:07 +0100, Thomas Hellström wrote: > Michel Dänzer wrote: > > >On Tue, 2007-11-27 at 15:44 -0500, Kristian Høgsberg wrote: > > > > > >>On Nov 27, 2007 2:30 PM, Keith Packard <[EMAIL PROTECTED]> wrote: > >>... > >> > >> > I both cases, the kernel will need to >

[Bug 13409] Killing compiz crashes Xorg

http://bugs.freedesktop.org/show_bug.cgi?id=13409 --- Comment #4 from [EMAIL PROTECTED] 2007-11-28 09:07 PST --- (In reply to comment #3) > (In reply to comment #2) > > Once again, does anyone have a clue why there are no line numbers in my > > stacktraces? > > See comment #4 of bug

[Bug 13427] Fix bsd build with drm_ati_pcigart_info

http://bugs.freedesktop.org/show_bug.cgi?id=13427 --- Comment #1 from [EMAIL PROTECTED] 2007-11-28 08:27 PST --- Created an attachment (id=12782) --> (http://bugs.freedesktop.org/attachment.cgi?id=12782&action=view) Patch to fix drm_ati_pcigart_info -- Configure bugmail: http://bu

[Bug 13427] New: Fix bsd build with drm_ati_pcigart_info

http://bugs.freedesktop.org/show_bug.cgi?id=13427 Summary: Fix bsd build with drm_ati_pcigart_info Product: DRI Version: DRI CVS Platform: Other OS/Version: FreeBSD Status: NEW Severity: normal Priority: medium

Re: DRI2 and lock-less operation

On Nov 26, 2007 6:51 PM, Jerome Glisse <[EMAIL PROTECTED]> wrote: ... > > Sounds like this will all work out after all :) > > Kristian > > Yes, between i started looking at your dri2 branch and didn't find dri2 > branch in your intel ddx repository did you pushed the code anywhere else ? > Would he

[Bug 13091] glean abort with "Segmentation fault" in GarbageCollectDRIDrawables

http://bugs.freedesktop.org/show_bug.cgi?id=13091 --- Comment #6 from [EMAIL PROTECTED] 2007-11-28 07:56 PST --- Thanks for fixing this. Brian, you're right this in only on mesa master, not the 7.0 branch. -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email -

[Bug 13425] New: on intel 945GM, xorg hard-locks when having glxgears and a custom-glx-application running

http://bugs.freedesktop.org/show_bug.cgi?id=13425 Summary: on intel 945GM, xorg hard-locks when having glxgears and a custom-glx-application running Product: DRI Version: XOrg CVS Platform: x86 (IA32) OS/Version: Linux (All)

Re: DRI2 and lock-less operation

Michel Dänzer wrote: >On Tue, 2007-11-27 at 15:44 -0500, Kristian Høgsberg wrote: > > >>On Nov 27, 2007 2:30 PM, Keith Packard <[EMAIL PROTECTED]> wrote: >>... >> >> I both cases, the kernel will need to know how to activate a given context and the context handle should be part

[PATCH] DRM: Standardize format of including linux header files with "<>".

Signed-off-by: Robert P. J. Day <[EMAIL PROTECTED]> --- outside of UML code, there are very few instances of including linux header files that don't use the "<>" format, so it would be nice to make everything completely standard. and it makes my tree-scanning scripts simpler, too. :-) diff

Re: Swapbuffers [was: Re: DRI2 and lock-less operation]

On Wed, Nov 28, 2007 at 12:43:18PM +0100, Stephane Marchesin wrote: > > This is what I want to do too. Especially since in the nvidia case we don't > have the issue of routing vblank interrupts to user space for that. > > So, the only issue I'm worried about is the latency induced by this > appro

Re: Swapbuffers [was: Re: DRI2 and lock-less operation]

Stephane Marchesin wrote: > On 11/28/07, *Keith Whitwell* <[EMAIL PROTECTED] > > wrote: > > > In my ideal world, the entity which knows and cares about cliprects > should be the one that does the swapbuffers, or at least is in control > of the process. That

Re: Clip Lists

Stephane Marchesin wrote: > > > On 11/28/07, *Keith Whitwell* <[EMAIL PROTECTED] > > wrote: > > Stephane Marchesin wrote: > > > > > > On 28 Nov 2007 06:19:39 +0100, *Soeren Sandmann* > <[EMAIL PROTECTED] > > mailto

Re: Clip Lists

On 11/28/07, Keith Whitwell <[EMAIL PROTECTED]> wrote: > > Stephane Marchesin wrote: > > > > > > On 28 Nov 2007 06:19:39 +0100, *Soeren Sandmann* <[EMAIL PROTECTED] > > > wrote: > > > > "Stephane Marchesin" <[EMAIL PROTECTED] > > > writes:

Re: Swapbuffers [was: Re: DRI2 and lock-less operation]

On 11/28/07, Keith Whitwell <[EMAIL PROTECTED]> wrote: > > > In my ideal world, the entity which knows and cares about cliprects > should be the one that does the swapbuffers, or at least is in control > of the process. That entity is the X server. > > Instead of tying ourselves into knots trying

Re: DRI2 and lock-less operation

On Tue, 2007-11-27 at 15:44 -0500, Kristian Høgsberg wrote: > On Nov 27, 2007 2:30 PM, Keith Packard <[EMAIL PROTECTED]> wrote: > ... > > > I both cases, the kernel will need to > > > know how to activate a given context and the context handle should be > > > part of the super ioctl arguments. >

Re: DRI2 and lock-less operation

On Tue, 2007-11-27 at 16:50 -0500, Kristian Høgsberg wrote: > > [...] I'm starting to doubt the "cliprects and swapbuffer > in the kernel" design anyhow. I wasn't going this route originally, > but since we already had that in place for i915 vblank buffer swaps, I > figured we might as well go t

Re: Clip Lists

Stephane Marchesin wrote: > > > On 28 Nov 2007 06:19:39 +0100, *Soeren Sandmann* <[EMAIL PROTECTED] > > wrote: > > "Stephane Marchesin" <[EMAIL PROTECTED] > > writes: > > > I fail to see how this works with a lockless design. How

Re: DRI2 and lock-less operation

On 11/28/07, Keith Packard <[EMAIL PROTECTED]> wrote: > > > On Wed, 2007-11-28 at 00:52 +0100, Stephane Marchesin wrote: > > > > The third case obviously will never require any kind of state > > re-emitting. > > Unless you run out of hardware contexts. Well, in that case we (plan to) bang the sta

Re: Clip Lists

On 28 Nov 2007 06:19:39 +0100, Soeren Sandmann <[EMAIL PROTECTED]> wrote: > > "Stephane Marchesin" <[EMAIL PROTECTED]> writes: > > > I fail to see how this works with a lockless design. How do you ensure > the X > > server doesn't change cliprects between the time it has written those in > the > >

Swapbuffers [was: Re: DRI2 and lock-less operation]

Kristian Høgsberg wrote: > On Nov 27, 2007 11:48 AM, Stephane Marchesin > <[EMAIL PROTECTED]> wrote: >> On 11/22/07, Kristian Høgsberg <[EMAIL PROTECTED]> wrote: > ... >>> It's all delightfully simple, but I'm starting to reconsider whether >>> the "lockless" bullet point is realistic. Note, the

Re: DRI2 and lock-less operation

Michel Dänzer wrote: > On Wed, 2007-11-28 at 09:30 +, Keith Whitwell wrote: >> Kristian Høgsberg wrote: >> >>> Another problem is that it's not just swapbuffer - anything that >>> touches the front buffer have to respect the cliprects - glCopyPixels >>> and glXCopySubBufferMESA - and thus have

Re: DRI2 and lock-less operation

On Wed, 2007-11-28 at 09:30 +, Keith Whitwell wrote: > Kristian Høgsberg wrote: > > > Another problem is that it's not just swapbuffer - anything that > > touches the front buffer have to respect the cliprects - glCopyPixels > > and glXCopySubBufferMESA - and thus have to happen in the kernel

Re: DRI2 and lock-less operation

Kristian Høgsberg wrote: > Another problem is that it's not just swapbuffer - anything that > touches the front buffer have to respect the cliprects - glCopyPixels > and glXCopySubBufferMESA - and thus have to happen in the kernel. These don't touch the real swapbuffer, just the fake one. Hence

Re: DRI2 and lock-less operation

Kristian Høgsberg wrote: > On Nov 27, 2007 2:30 PM, Keith Packard <[EMAIL PROTECTED]> wrote: > ... >>> I both cases, the kernel will need to >>> know how to activate a given context and the context handle should be >>> part of the super ioctl arguments. >> We needn't expose the contexts to user-s

[Bug 13409] Killing compiz crashes Xorg

http://bugs.freedesktop.org/show_bug.cgi?id=13409 --- Comment #3 from [EMAIL PROTECTED] 2007-11-28 00:48 PST --- (In reply to comment #2) > Once again, does anyone have a clue why there are no line numbers in my > stacktraces? See comment #4 of bug 13391. Can you still reproduce thi