On Sat, Aug 26, 2017 at 2:18 AM, Peter Hutterer
wrote:
> On 26/08/2017 06:52 , Roderick Colenbrander wrote:
>>
>> Hi Peter,
>>
>> I'm not too familiar with this code, but does this prevent usage of
>> accelerometer axes in libevdev for pure accelero
On Mon, Aug 28, 2017 at 2:29 AM, Pekka Paalanen wrote:
> On Wed, 23 Aug 2017 11:48:59 +1000
> Peter Hutterer wrote:
>
>> For previous versions, see:
>> v1:
>> https://lists.freedesktop.org/archives/wayland-devel/2017-March/033626.html
>> v2:
>> https://lists.freedesktop.org/archives/wayland-dev
Hi Peter,
I'm not too familiar with this code, but does this prevent usage of
accelerometer axes in libevdev for pure accelerometer devices as in
devices setting INPUT_PROP_ACCELEROMETER and not providing buttons or
other axes? As you are aware we are quite interested in in dualshock 3
/ 4 gamepad
ust from the fd.
Since I wasn't sure I did some digging. My first attempt was to use
EVIOCGPHYS, which for many HID devices seems to return hardware bus
information, which with some parsing could be mapped to a sysfs path.
However many older devices don't put reliable data in here, so this is
un
On Mon, Apr 17, 2017 at 9:05 PM, Peter Hutterer
wrote:
>
> On Fri, Apr 07, 2017 at 01:43:57PM +0300, Pekka Paalanen wrote:
> > On Fri, 7 Apr 2017 14:04:40 +1000
> > Peter Hutterer wrote:
> >
> > > For the initial patchset, see
> > > https://lists.freedesktop.org/archives/wayland-devel/2017-March/
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 wo
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 som
m not sure how much I like the inputfd
proposal. For a part because it doesn't fit some of our use cases well
(remote desktop + custom protocols). In addition I'm also a bit worried
about the complexity in handling composite devices.
Thanks,
Roderick
--
Roderick Colenbrander
Senior Manage
On Mon, Jan 23, 2017 at 10:38 PM, Peter Hutterer
wrote:
> On Mon, Jan 23, 2017 at 07:24:24PM -0800, Roderick Colenbrander wrote:
>> On Mon, Jan 23, 2017 at 2:05 PM, Jingkui Wang wrote:
>> > On Fri, Jan 20, 2017 at 2:22 AM, Pekka Paalanen
>> > wrote:
>> >>
nts
> or take the fd and get a full set of capabilities. Exposing the
> "standard set" will save the client from understanding the kernel and
> using toolkit/library. If some
> feature becomes so common, maybe we can move on to add it into the
> "standard set".
>
On Sun, Jan 22, 2017 at 9:02 PM, Peter Hutterer
wrote:
> On Sat, Jan 21, 2017 at 12:01:18PM -0800, Roderick Colenbrander wrote:
>> Hi Pekka,
>>
>> Thanks for your input as well. You raised some valid points as well
>> e.g. performance, just in case of my company's
ves for ideas and interested people to CC. IIRC there
> were quite many people and long discussions.
>
> Dennis, Jingkui, did you ever consider this approach, and if you did,
> what downsides did you see?
>
>
> Thanks,
> pq
--
Roderick Colenbrander
Senior Manager of Sof
of capability bitmap could make
sense. My team and I ourselves need most of this functionality as
well, so we won't mind helping out in some way.
Thanks,
Roderick
--
Roderick Colenbrander
Senior Manager of Software Engineering
Gaikai, a Sony Interactive Entertainment Company
roder...@
13 matches
Mail list logo
