On Sat, Dec 20, 2014 at 10:57:12PM +, Colin Macdonald wrote:
> 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
On Sun, Dec 21, 2014 at 02:39:02AM -0800, Dima Ryazanov wrote:
> Currently, the indexes are off by 4 because of the scroll buttons.
>
> Signed-off-by: Dima Ryazanov
> ---
> hw/xwayland/xwayland-input.c | 7 ++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/hw/xwayland/xw
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 descriptions of the X protocol and extensions.
>
> Consideri
Currently, the indexes are off by 4 because of the scroll buttons.
Signed-off-by: Dima Ryazanov
---
hw/xwayland/xwayland-input.c | 7 ++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/hw/xwayland/xwayland-input.c b/hw/xwayland/xwayland-input.c
index b8c543c..ad30c31 100644
---
On 21/12/14 22:24, Peter Hutterer wrote:
> see Alan's post for a better general answer, for Fedora you best run
> ./configure --prefix=/usr --libdir=/usr/lib64
>
> you can also rebuild the xorg-x11-drv-evdev package locally and check the
> configure line we pass in through the spec files, but
On Sat, Dec 20, 2014 at 11:06:21PM +, Colin Macdonald wrote:
> 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 bu
On 12/20/14 03:06 PM, Colin Macdonald wrote:
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.
Hi Jamey,
Thank you for your positive feedback.
and that you are willing to help and be involved.
On 12/21/14 15:49, Jamey Sharp wrote:
> That's great! If Asalle and Jaya don't mind, I'd like to be CC'd on
> progress reports and questions on these projects. I may be able to
> help.
Thank you for
That's great! If Asalle and Jaya don't mind, I'd like to be CC'd on
progress reports and questions on these projects. I may be able to
help.
The length-checking/byte-swapping proposal sounds like what I had in
mind, and what Keith expressed interest in. I have some confusion
about some of the deta
On 12/21/14 01:27, Josh Triplett wrote:
> XCB's client code turns a function call with arguments into data on the
> wire. I think the XCB server code should turn data on the wire into a
> dispatched function call, with approximately the same arguments and
> types as the original XCB client function
Overall task:
Make the server-side implementation of requests, events etc use
XCB-generated code.
(Instead of using the data structures from manually written proto-headers,
and instead of manual interpretation of the protocol in Proc functions.)
Overall strategy:
1. Use the generated code of libxc
Overall Task:
Implement byte-swapping and size-checking in the X-Server by using
generated code based on XCB protocol definitions.
1. Write a new code-generator which creates byte-swapping and
size-checking code.
(Byte-swapping and size-checking can both be done with the same generator.)
2.
There is already a project underway to do this.
We would have sent the technical proposal in a few days.
I will send the technical proposal as an extra message, soon.
In any case we should avoid that two teams are working on that independently.
We have two interns at Xorg who are working on this
13 matches
Mail list logo
