Hi,
Keith talked me intro writing a spec for DRI2, which I grudgingly must
admit is a good idea. I used the randr spec as a template, except I
replaced the flowery section dividers with a more fitting gears motif.
It's still a work in progress, mostly the introductory/background
sections though.
On Mon, Sep 8, 2008 at 9:38 PM, Keith Packard <[EMAIL PROTECTED]> wrote:
> On Mon, 2008-09-08 at 17:58 -0400, Kristian Høgsberg wrote:
>> Hi,
>>
>> Keith talked me intro writing a spec for DRI2, which I grudgingly must
>> admit is a good idea. I used the r
On Tue, Sep 9, 2008 at 11:46 AM, Keith Packard <[EMAIL PROTECTED]> wrote:
> On Tue, 2008-09-09 at 13:27 +0200, Michel Dänzer wrote:
>
>> I think it'd be good if the authentication stuff could be made/kept
>> optional or at least not DRM specific. (I'm not sure GEM or the DRM in
>> general is within
On Tue, Sep 9, 2008 at 1:34 PM, Michel Dänzer
<[EMAIL PROTECTED]> wrote:
> On Tue, 2008-09-09 at 10:11 -0700, Keith Packard wrote:
>> On Tue, 2008-09-09 at 18:41 +0200, Michel Dänzer wrote:
>> > Generally, if DRI2CopyRegion seriously wants to be useful for
>> > synchronization purposes, it probably
On Wed, Sep 10, 2008 at 5:10 PM, Keith Packard <[EMAIL PROTECTED]> wrote:
> On Wed, 2008-09-10 at 14:09 -0400, Kristian Høgsberg wrote:
>
>> Everybody can talk to the DRM and create
>> a token, but only if you can pass it to the server over DRI2 protocol,
>> can yo
On Thu, Sep 11, 2008 at 6:40 AM, Michel Dänzer
<[EMAIL PROTECTED]> wrote:
> On Wed, 2008-09-10 at 14:09 -0400, Kristian Høgsberg wrote:
>> On Tue, Sep 9, 2008 at 11:46 AM, Keith Packard <[EMAIL PROTECTED]> wrote:
>> > On Tue, 2008-09-09 at 13:27 +0200, Miche
On Thu, Sep 11, 2008 at 3:49 PM, Jesse Barnes <[EMAIL PROTECTED]> wrote:
> On Thursday, September 11, 2008 8:59 am Kristian Høgsberg wrote:
>> On Thu, Sep 11, 2008 at 6:40 AM, Michel Dänzer
>>
>> <[EMAIL PROTECTED]> wrote:
>> > On Wed, 2008-09-10 at 14:0
Hi,
Here's an updated version of the DRi2 specification. I've added some
discussion points with ISSUE: in the spec. The new stuff here is the
XChangeWindowAttributes inspired DRI2CopyRegion, that'll let us better
extend it in the future. I clarified and simplified the auth stuff,
dropping the gr
Hi,
Here's a quick, last-minute note on the state of DRI2 before I take
off for 2 weeks of vacation. I just pushed the updated protocol+docs
to dri2proto and updated mesa, xserver and the dri2 branch of
xf86-video-intel with the corresponding changes. What's implemented
here is the lowest level
Here's the 1.99.3 release of dri2proto, required by xserver master and 1.6.
cheers,
Kristian
Kristian Høgsberg (3):
Add protocol documentation, update to DRI2CopyRegion request.
Bump version to 1.99.2.
Bump to 1.99.3 and back out the value bitmask from the CopyRegion
re
On Wed, Jan 21, 2009 at 11:14 AM, Vasily Khoruzhick wrote:
> Hi, with mesa from git 3D is not hardware accellerated anymore on gma950,
>
> glxinfo | grep rend
> direct rendering: Yes
> OpenGL renderer string: Software Rasterizer
>
> LIBGL_DEBUG=1 glxgears
> libGL error: dlopen /usr/lib/dri/i915_dr
On Mon, Jan 26, 2009 at 7:41 PM, Alex Deucher wrote:
> AMD is pleased to announce the release of a 3D register reference
> guide for Radeon 6xx/7xx chips.
>
> The guide will be available in the usual places:
> http://www.x.org/docs/AMD/R6xx_3D_Registers.pdf
> and
> http://ati.amd.com/developer/ope
On Sun, Feb 8, 2009 at 7:00 AM, Eric Anholt wrote:
> With trying to match depths so that you didn't end up with a depth 24
> fbconfig for the 32-bit composite visual, I broke the alpha bits on the depth
> 24 X visual, which angered other applications. But in fixing that, the
> pickFBconfigs code
On Sat, Feb 28, 2009 at 12:21 AM, Eric Anholt wrote:
...
> I think the problem here was the DRI2 tiling fix, which was great for
> the 915-class 3D performance regression but bad for 915-class 2D. I've
> pushed a fix to master that should help. If it does, I'll try to get a
> 2.6.3 out soon.
>
>
On Fri, Mar 13, 2009 at 2:55 PM, Dan Nicholson wrote:
> On Thu, Mar 12, 2009 at 11:51 PM, Donnie Berkholz
> wrote:
>>
>> - merging xkbcomp into the server
>
> I'm been working on this in my spare time as per Daniel's advice to
> create a libxkbcommon shared library. If anyone wants any more deta
On Thu, Mar 26, 2009 at 6:33 PM, Jesse Barnes wrote:
> Ok, I think this is where the leak was:
> __glXUnrefDrawable->DrawableGone->__glXUnrefDrawable. This sequence
> meant the glxPriv would stay around (since it was used), but
> DrawableGone had generally already disposed of the pDrawable before
2009/4/1 Michel Dänzer :
> On Mon, 2009-03-30 at 13:04 +0800, Shuang He wrote:
>> Shuang He wrote:
>> > Jesse Barnes wrote:
>> > > On Fri, 27 Mar 2009 13:20:25 -0400
>> > > Kristian Høgsberg wrote:
>> > > >
>> > >
On Wed, Mar 25, 2009 at 10:21:51AM -0700, Jesse Barnes wrote:
> In trying to track down the memory leak in 20704, I found that the DRI2
> drawable destroy routine doesn't seem to get called when new drawables
> are created and old ones destroyed (as in the glViewport case in the
> bug).
Ok, sorry
by a server release.
Julien Cristau (1):
Distribute the protocol documentation
Kristian Høgsberg (1):
Bump to 2.0 and release
Paulo Cesar Pereira de Andrade (1):
Janitor: Correct make distcheck and dont distribute autogen.sh
git tag: dri2proto-2.0
http://xorg.freedesktop.org/ar
Here is dri2proto version 2.3. This release adds an event designed by
Francisco Jerez to let the server notify clients when the buffers
associated with a drawable become invalid. This can happen when the
drawable is resized or when DRI2SwapBuffer exchanges front and back
buffers.
Francisco Jerez
This case was missing and could cause corruption if we flush damage events
to a client before the driver gets to submit the rendering from the
callback chain.
Signed-off-by: Kristian Høgsberg
---
os/io.c |4
1 files changed, 4 insertions(+), 0 deletions(-)
diff --git a/os/io.c b/os
On Thu, Jul 29, 2010 at 7:18 PM, Keith Packard wrote:
> On Thu, 29 Jul 2010 18:53:34 -0400, Kristian Høgsberg
> wrote:
>
>> This case was missing and could cause corruption if we flush damage events
>> to a client before the driver gets to submit the rendering from
2010/7/29 Dave Airlie :
>>> Also, there is one more call to FlushClient in CloseDownConnection; any
>>> reason we shouldn't be invoking the FlushCallback there too? More from a
>>> sense of completeness than a chance that it's going to actually matter.
>>
>> Yes, that sounds fine. And I just reali
r has even seen the rendering
request. Reporting damage events after the rendering fixes this
corner case and better corresponds with how we expect this to work.
Signed-off-by: Kristian Høgsberg
---
damageext/damageext.c |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/dama
We were missing the callback in a couple of places. Drivers may use
the flush callback to submit batched up rendering before events (for
example, damage events) are sent out, to ensure that the rendering
has happend when the client receives the event.
Signed-off-by: Kristian Høgsberg
---
os
Before this gets drowned out in janitorial patches... Keith, do you
want a pull request for this and the damageext patch? Did you have
have a look at the damage change?
Kristian
2010/7/29 Kristian Høgsberg :
> We were missing the callback in a couple of places. Drivers may use
> the
On Sun, Aug 1, 2010 at 3:20 PM, Keith Packard wrote:
> On Sun, 1 Aug 2010 14:39:46 -0400, Kristian Høgsberg
> wrote:
>> Before this gets drowned out in janitorial patches... Keith, do you
>> want a pull request for this and the damageext patch? Did you have
>> have a l
2010/8/2 Keith Packard :
> On Mon, 2 Aug 2010 08:24:04 -0400, Kristian Høgsberg
> wrote:
>> On Sun, Aug 1, 2010 at 3:20 PM, Keith Packard wrote:
>> > On Sun, 1 Aug 2010 14:39:46 -0400, Kristian Høgsberg
>> > wrote:
>> >> Before this gets drowned
ts to the client buffer before the
driver sees the rendering request, but wants to make sure that once the
output buffer is flushed, all the rendering has been submitted.
Signed-off-by: Kristian Høgsberg
---
Here's the other approach for fixing damage vs flush client. In writing the
commit m
On Mon, Aug 2, 2010 at 2:36 PM, Keith Packard wrote:
> On Mon, 2 Aug 2010 11:29:55 -0400, Kristian Høgsberg
> wrote:
>>
>> Here's the other approach for fixing damage vs flush client. In writing the
>> commit message, it certainly does feel like damage should jus
2010/8/2 Keith Packard :
> On Mon, 2 Aug 2010 19:58:47 -0400, Kristian Høgsberg
> wrote:
>
>> And if I don't have to touch low level protocol code, I'd
>> rather not.
>
> Scaredy cat.
Oh, I'm mostly just lazy. Cleaning up X code
On Mon, Aug 2, 2010 at 2:36 PM, Keith Packard wrote:
> On Mon, 2 Aug 2010 11:29:55 -0400, Kristian Høgsberg
> wrote:
>>
>> Here's the other approach for fixing damage vs flush client. In writing the
>> commit message, it certainly does feel like damage should jus
On Sun, Nov 28, 2010 at 9:46 AM, Jan Engelhardt wrote:
>
> The following changes since commit f94a64cc08b47cdbfdfea5b5756340246fc391ed:
>
> Link with -no-undefined (2010-10-26 14:11:38 -0400)
Thanks, those all look good, pulled and pushed.
Kristian
> are available in the git repository at:
>
From: Justin Dou
The calling for allocate_or_reuse_buffer may fail due to some reason, e.g. out
of memory.
If the buffers[] were not initialized to be NULL, the following err_out may try
to access an illegal memory, which will cause X crash afterward.
Reviewed-by: Kristian Høgsberg
Signed
34 matches
Mail list logo
