On Apr 23 2015 or thereabouts, Dmitry Torokhov wrote:
> On Thu, Apr 23, 2015 at 02:38:27PM -0400, Benjamin Tissoires wrote:
> > On Apr 23 2015 or thereabouts, Dmitry Torokhov wrote:
> > > On Thu, Apr 23, 2015 at 07:10:55PM +0200, Henrik Rydberg wrote:
> > > > > "Creation, replacement and
On Apr 23 2015 or thereabouts, Dmitry Torokhov wrote:
On Thu, Apr 23, 2015 at 02:38:27PM -0400, Benjamin Tissoires wrote:
On Apr 23 2015 or thereabouts, Dmitry Torokhov wrote:
On Thu, Apr 23, 2015 at 07:10:55PM +0200, Henrik Rydberg wrote:
Creation, replacement and destruction of
On Fri, Apr 24, 2015 at 08:26:39AM +0200, Henrik Rydberg wrote:
> Peter,
>
> It may be a long time ago now, but we had very vocal discussions regarding the
> MT protocol back then, and I am quite sure all the subtleties are well
> understood. In order to fully appreciate the simplicity of the
On Fri, Apr 24, 2015 at 08:26:39AM +0200, Henrik Rydberg wrote:
Peter,
It may be a long time ago now, but we had very vocal discussions regarding the
MT protocol back then, and I am quite sure all the subtleties are well
understood. In order to fully appreciate the simplicity of the
Peter,
It may be a long time ago now, but we had very vocal discussions regarding the
MT protocol back then, and I am quite sure all the subtleties are well
understood. In order to fully appreciate the simplicity of the protocol, one
only needs to stop misintepreting it. In order to do that,
Peter,
It may be a long time ago now, but we had very vocal discussions regarding the
MT protocol back then, and I am quite sure all the subtleties are well
understood. In order to fully appreciate the simplicity of the protocol, one
only needs to stop misintepreting it. In order to do that,
On Thu, Apr 23, 2015 at 11:47:09AM -0700, Dmitry Torokhov wrote:
> On Thu, Apr 23, 2015 at 02:38:27PM -0400, Benjamin Tissoires wrote:
> > On Apr 23 2015 or thereabouts, Dmitry Torokhov wrote:
> > > On Thu, Apr 23, 2015 at 07:10:55PM +0200, Henrik Rydberg wrote:
> > > > > "Creation, replacement
> My guess is that none of these drivers are
> able to handle a silent closing of a slot and the easiest solution might
> be to simply change the documentation if in fact nobody uses the
> compressed notation (which removes just one ABS_SLOT event within the
> frame, so not sure we can call it
On Thu, Apr 23, 2015 at 02:38:27PM -0400, Benjamin Tissoires wrote:
> On Apr 23 2015 or thereabouts, Dmitry Torokhov wrote:
> > On Thu, Apr 23, 2015 at 07:10:55PM +0200, Henrik Rydberg wrote:
> > > > "Creation, replacement and destruction of contacts is achieved by
> > > > modifying the
On Apr 23 2015 or thereabouts, Dmitry Torokhov wrote:
> On Thu, Apr 23, 2015 at 07:10:55PM +0200, Henrik Rydberg wrote:
> > > "Creation, replacement and destruction of contacts is achieved by
> > > modifying the ABS_MT_TRACKING_ID of the associated slot. A
> > > non-negative tracking id is
On Thu, Apr 23, 2015 at 07:10:55PM +0200, Henrik Rydberg wrote:
> > "Creation, replacement and destruction of contacts is achieved by
> > modifying the ABS_MT_TRACKING_ID of the associated slot. A
> > non-negative tracking id is interpreted as a contact, and the value -1
> > denotes an unused
> "Creation, replacement and destruction of contacts is achieved by
> modifying the ABS_MT_TRACKING_ID of the associated slot. A
> non-negative tracking id is interpreted as a contact, and the value -1
> denotes an unused slot. A tracking id not previously present is
> considered new, and a
On Tue, Apr 7, 2015 at 6:17 AM, Jiri Kosina wrote:
> On Mon, 6 Apr 2015, Dmitry Torokhov wrote:
>
>> > With
>> > https://git.kernel.org/cgit/linux/kernel/git/jikos/hid.git/commit/?h=for-4.1/wacom=9a1c001298fd567c0f0776ab54ab9965eeb9019f
>> > in Jiri's tree, scheduled for 4.1, this patch should
Creation, replacement and destruction of contacts is achieved by
modifying the ABS_MT_TRACKING_ID of the associated slot. A
non-negative tracking id is interpreted as a contact, and the value -1
denotes an unused slot. A tracking id not previously present is
considered new, and a tracking
On Apr 23 2015 or thereabouts, Dmitry Torokhov wrote:
On Thu, Apr 23, 2015 at 07:10:55PM +0200, Henrik Rydberg wrote:
Creation, replacement and destruction of contacts is achieved by
modifying the ABS_MT_TRACKING_ID of the associated slot. A
non-negative tracking id is interpreted as a
On Thu, Apr 23, 2015 at 02:38:27PM -0400, Benjamin Tissoires wrote:
On Apr 23 2015 or thereabouts, Dmitry Torokhov wrote:
On Thu, Apr 23, 2015 at 07:10:55PM +0200, Henrik Rydberg wrote:
Creation, replacement and destruction of contacts is achieved by
modifying the ABS_MT_TRACKING_ID of
On Thu, Apr 23, 2015 at 07:10:55PM +0200, Henrik Rydberg wrote:
Creation, replacement and destruction of contacts is achieved by
modifying the ABS_MT_TRACKING_ID of the associated slot. A
non-negative tracking id is interpreted as a contact, and the value -1
denotes an unused slot. A
My guess is that none of these drivers are
able to handle a silent closing of a slot and the easiest solution might
be to simply change the documentation if in fact nobody uses the
compressed notation (which removes just one ABS_SLOT event within the
frame, so not sure we can call it
On Tue, Apr 7, 2015 at 6:17 AM, Jiri Kosina jkos...@suse.cz wrote:
On Mon, 6 Apr 2015, Dmitry Torokhov wrote:
With
https://git.kernel.org/cgit/linux/kernel/git/jikos/hid.git/commit/?h=for-4.1/wacomid=9a1c001298fd567c0f0776ab54ab9965eeb9019f
in Jiri's tree, scheduled for 4.1, this patch
On Thu, Apr 23, 2015 at 11:47:09AM -0700, Dmitry Torokhov wrote:
On Thu, Apr 23, 2015 at 02:38:27PM -0400, Benjamin Tissoires wrote:
On Apr 23 2015 or thereabouts, Dmitry Torokhov wrote:
On Thu, Apr 23, 2015 at 07:10:55PM +0200, Henrik Rydberg wrote:
Creation, replacement and
On Mon, 6 Apr 2015, Dmitry Torokhov wrote:
> > With
> > https://git.kernel.org/cgit/linux/kernel/git/jikos/hid.git/commit/?h=for-4.1/wacom=9a1c001298fd567c0f0776ab54ab9965eeb9019f
> > in Jiri's tree, scheduled for 4.1, this patch should not break any existing
> > driver. I'd like us to stage it
On Mon, 6 Apr 2015, Dmitry Torokhov wrote:
With
https://git.kernel.org/cgit/linux/kernel/git/jikos/hid.git/commit/?h=for-4.1/wacomid=9a1c001298fd567c0f0776ab54ab9965eeb9019f
in Jiri's tree, scheduled for 4.1, this patch should not break any existing
driver. I'd like us to stage it
On Mon, Mar 30, 2015 at 02:54:15PM -0400, Benjamin Tissoires wrote:
> The case occurred recently with a touchscreen using twice a slot during a
> single EV_SYN event:
>
> E: 0.288415 # SYN_REPORT (0) --
> E: 0.296207 0003 002f # EV_ABS /
On Mon, Mar 30, 2015 at 02:54:15PM -0400, Benjamin Tissoires wrote:
The case occurred recently with a touchscreen using twice a slot during a
single EV_SYN event:
E: 0.288415 # SYN_REPORT (0) --
E: 0.296207 0003 002f # EV_ABS / ABS_MT_SLOT
The case occurred recently with a touchscreen using twice a slot during a
single EV_SYN event:
E: 0.288415 # SYN_REPORT (0) --
E: 0.296207 0003 002f # EV_ABS / ABS_MT_SLOT 0
E: 0.296207 0003 0039 -001 # EV_ABS / ABS_MT_TRACKING_ID
The case occurred recently with a touchscreen using twice a slot during a
single EV_SYN event:
E: 0.288415 # SYN_REPORT (0) --
E: 0.296207 0003 002f # EV_ABS / ABS_MT_SLOT 0
E: 0.296207 0003 0039 -001 # EV_ABS / ABS_MT_TRACKING_ID
26 matches
Mail list logo
