We've talked about doing the xserver equivalent of XCB for years--that is,
auto-generating the protocol serialization and deserialization code from
XCB's machine-readable descriptions of the X protocol and extensions.
Considering the recent CVEs in that code, I think it's time. So I want to
Jamey Sharp ja...@minilop.net writes:
We've talked about doing the xserver equivalent of XCB for years--that is,
auto-generating the protocol serialization and deserialization code from
XCB's machine-readable descriptions of the X protocol and extensions.
Considering the recent CVEs in that
On 27/06/14 02:47, Peter Hutterer wrote:
right idea, but I think this is too fancy for what we need. Something like
this before the loop should be enough:
/* curse you, android! */
if (libevdev_has_event_code(EV_ABS, ABS_MT_POSITION_X)
!libevdev_has_event_code(EV_ABS, ABS_X))
{
While testing input-evdev, I removed my distro (Fedora) provided
xorg-x11-drv-evdev package and did a make install from source into
/usr/local/lib/xorg/modules.
I was rather shocked (hmmm, my machine has working wacom but no
keyboard or trackpoint...) that X does not search /usr/local/lib by
[Resending this from the address that's actually subscribed.]
On Sat, Dec 20, 2014 at 12:27:08PM -0800, Jamey Sharp wrote:
We've talked about doing the xserver equivalent of XCB for years--that is,
auto-generating the protocol serialization and deserialization code from
XCB's machine-readable
While these patches seem to work ok, somethings not properly getting
accelerated when using a shadow buffer and I really don't know why. I
guess it's still better than no shadow.
On Fri, Dec 19, 2014 at 2:25 PM, Jason Ekstrand ja...@jlekstrand.net
wrote:
I've also pushed a branch with my
