On Thu, Sep 21, 2017 at 06:57:41PM +0700, Antoine Martin wrote:
> (snip)
>
> >> And it all seems to work pretty well so far. Applications like Firefox
> >> can now scroll a few pixels at a time.
> >>
> >> Questions:
> >> 1) Anything wrong with this approach?
> >
> > well. on the face of it, it's
Adam Jackson writes:
> Only enabled for the DRI backends at the moment. In principle WGL/CGL
> could support this - it's sort of implied by GL 3.0 support - but in
> practice I don't know that it would actually work.
>
> This is currently a draft extension, under review at:
>
> https://github.com
Adam Jackson writes:
> Just never filled in, oops. Seems to have gone unnoticed because
> normally glXQueryContext simply returns the values filled in by the
> client library when the context was created. The only path by which you
> normally get to a GLXQueryContext request is glXImportContext,
Please include the following commit in the next xserver release:
abb031e731f5c159add1b3351de9c4bb121bf00a
dri2: Sync i965_pci_ids.h from Mesa.
The ids are needed for us to test new systems with xorg.
-Mark
___
xorg-devel@lists.x.org: X.Org development
Only enabled for the DRI backends at the moment. In principle WGL/CGL
could support this - it's sort of implied by GL 3.0 support - but in
practice I don't know that it would actually work.
This is currently a draft extension, under review at:
https://github.com/KhronosGroup/OpenGL-Registry/pull/
Just never filled in, oops. Seems to have gone unnoticed because
normally glXQueryContext simply returns the values filled in by the
client library when the context was created. The only path by which you
normally get to a GLXQueryContext request is glXImportContext, and then
only if the context is
Hi Jason,
> It doesn't look like my following fix didn't made it into your branch.
> Overlooked, or didn't make the cut?
>
> https://cgit.freedesktop.org/~ofourdan/xserver/commit/?id=2fbf62b2fb3dcb29551251d09aa695715bb754f4
Yeap, that's just an overlook, sorry.
Cheers,
Olivier
_
On Thu, Sep 21, 2017 at 7:21 AM, Olivier Fourdan wrote:
>
> Hi all,
>
> It appears the Xserver in 1.19 branch is missing quite a few fixes from
> master, so I prepared a branch back-porting fixes at:
>
> https://cgit.freedesktop.org/~ofourdan/xserver/log/?h=server-1.19-fixes
>
> I *tried* to pi
Hi all,
It appears the Xserver in 1.19 branch is missing quite a few fixes from master,
so I prepared a branch back-porting fixes at:
https://cgit.freedesktop.org/~ofourdan/xserver/log/?h=server-1.19-fixes
I *tried* to pick as many relevant fixes as possible, avoiding new features (*)
and im
Hi.
Just a kind ping. Is any additional information needed in this patch?
Thanks!
2017-09-13 23:23 GMT-04:00 Nikolay Martynov :
> It looks like offsets calculated during image censoring are wrong.
> This results in black (empty) images returns.
>
> This fix is very similar to 6c6f09aac7f1d1367a0
(snip)
>> And it all seems to work pretty well so far. Applications like Firefox
>> can now scroll a few pixels at a time.
>>
>> Questions:
>> 1) Anything wrong with this approach?
>
> well. on the face of it, it's fine. but remember, you're not triggering a
> behaviour directly, you're emulating
On 06/08/17 09:46, Yu, Qiang wrote:
> How do you run the xserver?
https://xpra.org/trac/wiki/Xdummy
> And do you have this file
> /dev/dri/renderD128
Yes.
> and right permission to access?
Yes.
As per ajax's reply, I've revised my reasonable-but-invalid expectations.
I'm primarily interested in
On 28/08/17 13:02, Alan Coopersmith wrote:
> I admit not looking at this code in a year and a half and barely
> remembering
> what it does, but that seems like the wrong place to add the check -
> wouldn't
> it make more sense to change
> if (displayfd != -1) {
> to
> if ((displayfd != -1)
13 matches
Mail list logo
