On Wed, Apr 05, 2017 at 04:51:51PM -0700, Roderick Colenbrander wrote:
> On Mon, Apr 3, 2017 at 9:08 PM, Peter Hutterer
> wrote:
> >
> > On Mon, Apr 03, 2017 at 04:08:21PM -0700, Roderick Colenbrander wrote:
> > > Hi Peter,
> > >
> > > Thanks for sharing this proposal. I have some little comments
On Wed, 05 Apr 2017 at 17:45:51 -0700, Roderick Colenbrander wrote:
> I wonder how Valve is doing this on Steam as with the Steam
> Controller, which I haven't used. I think they are allowing it to
> replace keyboard and mouse kind of. Curious how they are solving this.
> My guess is they are actua
On Wed, Apr 05, 2017 at 11:15:05AM +0100, Steven Newbury wrote:
> On Wed, 2017-04-05 at 11:57 +0200, Bastien Nocera wrote:
> > On Wed, 2017-04-05 at 10:42 +0100, Steven Newbury wrote:
> > >
> >
> >
> > > There's a reason the mouse support from the X DGA Extension out-
> > > survived the "direct
On Wed, Apr 05, 2017 at 11:12:47AM +0100, Daniel Stone wrote:
> Hi Steven,
>
> On 5 April 2017 at 11:04, Steven Newbury wrote:
> > On Wed, 2017-04-05 at 10:53 +0100, Daniel Stone wrote:
> >> DGA's DirectMouse doesn't change the latency. It doesn't give the
> >> client a direct-to-kernel stream. I
Hi Bastien,
On Tue, Apr 4, 2017 at 2:17 AM, Bastien Nocera wrote:
> Hey Roderick,
>
> On Mon, 2017-04-03 at 16:08 -0700, Roderick Colenbrander wrote:
>> Hi Peter,
>>
>> Thanks for sharing this proposal. I have some little comments for a
>> later stage, but would rather discuss some big items fir
On Mon, Apr 3, 2017 at 9:08 PM, Peter Hutterer wrote:
>
> On Mon, Apr 03, 2017 at 04:08:21PM -0700, Roderick Colenbrander wrote:
> > Hi Peter,
> >
> > Thanks for sharing this proposal. I have some little comments for a later
> > stage, but would rather discuss some big items first.
> >
> > The fee
On Wed, 2017-04-05 at 11:57 +0200, Bastien Nocera wrote:
> On Wed, 2017-04-05 at 10:42 +0100, Steven Newbury wrote:
> >
>
>
> > There's a reason the mouse support from the X DGA Extension out-
> > survived the "direct framebuffer access". The latency through the
> > wire
> > whether X or Waylan
Hi Steven,
On 5 April 2017 at 11:04, Steven Newbury wrote:
> On Wed, 2017-04-05 at 10:53 +0100, Daniel Stone wrote:
>> DGA's DirectMouse doesn't change the latency. It doesn't give the
>> client a direct-to-kernel stream. It still results in the server
>> doing
>
> I wondered if I was implying th
On Wed, 2017-04-05 at 10:53 +0100, Daniel Stone wrote:
> Hi Steven,
>
> On 5 April 2017 at 10:42, Steven Newbury
> wrote:
> > On Wed, 2017-04-05 at 10:25 +0100, Daniel Stone wrote:
> > > The compositor _must_ interpose every single keyboard/mouse
> > > event,
> > > and
> > > they are simple enoug
On Wed, 2017-04-05 at 10:42 +0100, Steven Newbury wrote:
>
> There's a reason the mouse support from the X DGA Extension out-
> survived the "direct framebuffer access". The latency through the
> wire
> whether X or Wayland for mouse input it just too high for mouse
> controlled high framerate 3
Hi Steven,
On 5 April 2017 at 10:42, Steven Newbury wrote:
> On Wed, 2017-04-05 at 10:25 +0100, Daniel Stone wrote:
>> The compositor _must_ interpose every single keyboard/mouse event,
>> and
>> they are simple enough that it is possibly to easily encode them with
>> universally-accepted concept
On Wed, 2017-04-05 at 10:25 +0100, Daniel Stone wrote:
> Hi,
>
> On 5 April 2017 at 04:40, Carsten Haitzler
> wrote:
> > On Tue, 04 Apr 2017 14:45:13 +0200 Bastien Nocera > t> said:
> > > There's two possible solutions to this problem:
> > > - evdev gives you the ability the mask certain events.
On Wed, 2017-04-05 at 12:40 +0900, Carsten Haitzler wrote:
> On Tue, 04 Apr 2017 14:45:13 +0200 Bastien Nocera
> said:
>
> > On Tue, 2017-04-04 at 20:32 +0900, Carsten Haitzler wrote:
> > > On Tue, 4 Apr 2017 10:22:24 +1000 Peter Hutterer > > who-
> > > t.net>
> > > said:
> > >
> > > > On Tue,
Hi,
On 5 April 2017 at 04:40, Carsten Haitzler wrote:
> On Tue, 04 Apr 2017 14:45:13 +0200 Bastien Nocera said:
>> There's two possible solutions to this problem:
>> - evdev gives you the ability the mask certain events. The compositor
>> can keep one fd open masking everything but the power/men
On Tue, 04 Apr 2017 14:45:13 +0200 Bastien Nocera said:
> On Tue, 2017-04-04 at 20:32 +0900, Carsten Haitzler wrote:
> > On Tue, 4 Apr 2017 10:22:24 +1000 Peter Hutterer > t.net>
> > said:
> >
> > > On Tue, Apr 04, 2017 at 08:16:03AM +0900, Carsten Haitzler wrote:
> > > > On Fri, 31 Mar 2017 17
On Tue, 2017-04-04 at 20:32 +0900, Carsten Haitzler wrote:
> On Tue, 4 Apr 2017 10:22:24 +1000 Peter Hutterer t.net>
> said:
>
> > On Tue, Apr 04, 2017 at 08:16:03AM +0900, Carsten Haitzler wrote:
> > > On Fri, 31 Mar 2017 17:29:19 +1000 Peter Hutterer > > @who-t.net>
> > > said:
> > >
> > > If
On Tue, 04 Apr 2017 11:29:30 +0200 Bastien Nocera said:
> On Tue, 2017-04-04 at 08:16 +0900, Carsten Haitzler wrote:
> > On Fri, 31 Mar 2017 17:29:19 +1000 Peter Hutterer > -t.net>
> > said:
> >
> > If you're going to do this ... why not just do it for keyboards,
> > mice, touch
> > panels etc.
On Tue, 4 Apr 2017 10:22:24 +1000 Peter Hutterer
said:
> On Tue, Apr 04, 2017 at 08:16:03AM +0900, Carsten Haitzler wrote:
> > On Fri, 31 Mar 2017 17:29:19 +1000 Peter Hutterer
> > said:
> >
> > If you're going to do this ... why not just do it for keyboards, mice, touch
> > panels etc. too?
>
On Tue, 2017-04-04 at 08:16 +0900, Carsten Haitzler wrote:
> On Fri, 31 Mar 2017 17:29:19 +1000 Peter Hutterer -t.net>
> said:
>
> If you're going to do this ... why not just do it for keyboards,
> mice, touch
> panels etc. too?
>
> My point is - the same reasons these other devices don't be laz
Hey Roderick,
On Mon, 2017-04-03 at 16:08 -0700, Roderick Colenbrander wrote:
> Hi Peter,
>
> Thanks for sharing this proposal. I have some little comments for a
> later stage, but would rather discuss some big items first.
>
> The feedback I will share comes from a couple different angles as we
On Tue, Apr 04, 2017 at 08:52:03AM +0100, Steven Newbury wrote:
> On Tue, 2017-04-04 at 13:42 +1000, Peter Hutterer wrote:
> > On Mon, Apr 03, 2017 at 10:19:16PM -0500, Joshua Watt wrote:
> > >
> > >
> > > On 04/03/2017 07:22 PM, Peter Hutterer wrote:
> > > > On Tue, Apr 04, 2017 at 08:16:03AM +0
On Tue, 2017-04-04 at 13:42 +1000, Peter Hutterer wrote:
> On Mon, Apr 03, 2017 at 10:19:16PM -0500, Joshua Watt wrote:
> >
> >
> > On 04/03/2017 07:22 PM, Peter Hutterer wrote:
> > > On Tue, Apr 04, 2017 at 08:16:03AM +0900, Carsten Haitzler wrote:
> > > > On Fri, 31 Mar 2017 17:29:19 +1000 Pete
On Sat, Apr 01, 2017 at 12:55:57PM +0800, Jonas Ådahl wrote:
[...]
> FWIW, creating a libgamingdev repository that just contains a property
> specification text file and a hwdb file, could potentially be a good
> enough authority.
Code is easier to criticise than ideas, so here's a repository ;)
On Mon, Apr 03, 2017 at 04:08:21PM -0700, Roderick Colenbrander wrote:
> Hi Peter,
>
> Thanks for sharing this proposal. I have some little comments for a later
> stage, but would rather discuss some big items first.
>
> The feedback I will share comes from a couple different angles as we are
> i
On Mon, Apr 03, 2017 at 10:19:16PM -0500, Joshua Watt wrote:
>
>
> On 04/03/2017 07:22 PM, Peter Hutterer wrote:
> > On Tue, Apr 04, 2017 at 08:16:03AM +0900, Carsten Haitzler wrote:
> > > On Fri, 31 Mar 2017 17:29:19 +1000 Peter Hutterer
> > >
> > > said:
> > >
> > > If you're going to do thi
On 04/03/2017 07:22 PM, Peter Hutterer wrote:
On Tue, Apr 04, 2017 at 08:16:03AM +0900, Carsten Haitzler wrote:
On Fri, 31 Mar 2017 17:29:19 +1000 Peter Hutterer
said:
If you're going to do this ... why not just do it for keyboards, mice, touch
panels etc. too?
all these have desktop intera
On Tue, Apr 04, 2017 at 08:16:03AM +0900, Carsten Haitzler wrote:
> On Fri, 31 Mar 2017 17:29:19 +1000 Peter Hutterer
> said:
>
> If you're going to do this ... why not just do it for keyboards, mice, touch
> panels etc. too?
all these have desktop interactions that the compositor needs. joystic
On Fri, 31 Mar 2017 17:29:19 +1000 Peter Hutterer
said:
If you're going to do this ... why not just do it for keyboards, mice, touch
panels etc. too?
My point is - the same reasons these other devices don't be lazy and stick
their heads in the sand with these other devices are the same reasons
j
Hi Peter,
Thanks for sharing this proposal. I have some little comments for a later
stage, but would rather discuss some big items first.
The feedback I will share comes from a couple different angles as we are
interested in Wayland for various different use cases.
Originally we had the gamepad
On Mon, 2017-04-03 at 10:59 +1000, Peter Hutterer wrote:
>
> Mostly for the archives, Timo Paulssen pointed me to
> https://github.com/denilsonsa/udev-joystick-blacklist
> At least for the compositor's side of things this is a good start,
> it's
> independent of this protocol though.
Very usefu
Hey,
On Fri, 2017-03-31 at 12:23 +0300, Pekka Paalanen wrote:
> On Fri, 31 Mar 2017 17:29:19 +1000
> Peter Hutterer wrote:
>
> > +
> > +
> > + This event is sent to notify the client of a custom
> > property that
> > + applies to this device. The property is a standard
> > key/val
On Sat, 1 Apr 2017 10:48:40 +1000
Peter Hutterer wrote:
> On Fri, Mar 31, 2017 at 12:23:49PM +0300, Pekka Paalanen wrote:
> > > +
> > > + This event is sent to notify the client of a custom property that
> > > + applies to this device. The property is a standard key/value store
> > > + in U
On Sat, Apr 01, 2017 at 12:55:57PM +0800, Jonas Ådahl wrote:
> On Sat, Apr 01, 2017 at 10:48:40AM +1000, Peter Hutterer wrote:
> > On Fri, Mar 31, 2017 at 12:23:49PM +0300, Pekka Paalanen wrote:
> > > > +
> > > > + This event is sent to notify the client of a custom property
> > > > th
On Fri, Mar 31, 2017 at 05:29:19PM +1000, Peter Hutterer wrote:
> This is the first draft for a protocol to enable direct access to input
> devices. The basic premise is: instead of protocols to handle gaming
> devices, 3D mice, sensors, etc. we just hand you (the client) an fd and hope
> you're ha
On Sat, Apr 01, 2017 at 10:48:40AM +1000, Peter Hutterer wrote:
> On Fri, Mar 31, 2017 at 12:23:49PM +0300, Pekka Paalanen wrote:
> > > +
> > > + This event is sent to notify the client of a custom property that
> > > + applies to this device. The property is a standard key/value store
> > >
On Fri, Mar 31, 2017 at 12:23:49PM +0300, Pekka Paalanen wrote:
> > +
> > + This event is sent to notify the client of a custom property that
> > + applies to this device. The property is a standard key/value store
> > + in UTF-8 format, interpretation of both strings is left to the
> >
On 31/03/17 04:23 AM, Pekka Paalanen wrote:
On Fri, 31 Mar 2017 17:29:19 +1000
Peter Hutterer wrote:
This is the first draft for a protocol to enable direct access to input
devices. The basic premise is: instead of protocols to handle gaming
devices, 3D mice, sensors, etc. we just hand you (th
On Fri, 31 Mar 2017 17:29:19 +1000
Peter Hutterer wrote:
> This is the first draft for a protocol to enable direct access to input
> devices. The basic premise is: instead of protocols to handle gaming
> devices, 3D mice, sensors, etc. we just hand you (the client) an fd and hope
> you're happy w
This is the first draft for a protocol to enable direct access to input
devices. The basic premise is: instead of protocols to handle gaming
devices, 3D mice, sensors, etc. we just hand you (the client) an fd and hope
you're happy with it. You get to play with that fd until it's revoked, i.e.
right
39 matches
Mail list logo
