From: Robert Siemer <Robert.Siemer@backsla.sh>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] Jumpy cursor with Wacom Graphire Bluetooth
Date: Sat, 8 Oct 2005 15:25:33 +0200 [thread overview]
Message-ID: <20051008132533.GA954@polar.elf12.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 1712 bytes --]
Hello everybody!
hcidump is telling me that my tablet sends packets only after six pixels
of mouse movement or together with button events. - I suppose that some
parameters exchanged during connection handshake are the cause.
-Who is making the connectinon? (hidp kernel module?)
-Who can/could influence it's outcome? (hidd userspace daemon? Plays
hcid an important role?)
-Has the latency thing something to do with it?
-Which spec should I first dig into - Bluetooth or HID?
I played already around with role switching (forced, voluntary from the
tablet, none). - Has no influence.
A "hcidump -w" connection dumps are attached. Here inline some tablet
mouse movements:
panorama:/tmp# hcidump -V -X
HCI sniffer - Bluetooth packet analyzer ver 1.23
device: hci0 snap_len: 1028 filter: 0xffffffff
> ACL data: handle 41 flags 0x02 dlen 10
L2CAP(d): cid 0x0041 len 6 [psm 0]
0000: a1 02 00 fa 02 00 ......
^^ ^^
Curser moved six "entities" to the left. While already sending a packet,
the tablet also reports some down movements ("02").
> ACL data: handle 41 flags 0x02 dlen 13
L2CAP(d): cid 0x0041 len 9 [psm 0]
0000: a1 03 00 00 00 00 00 00 20 ........
> ACL data: handle 41 flags 0x02 dlen 10
L2CAP(d): cid 0x0041 len 6 [psm 0]
0000: a1 02 00 fd 06 00 ......
^^ ^^
The same, but moved 06 entities ("pixel") down. Obviously I also moved 3
pixels left (0xfd).
> ACL data: handle 41 flags 0x02 dlen 13
L2CAP(d): cid 0x0041 len 9 [psm 0]
0000: a1 03 00 00 00 00 00 00 20 ........
Thanks for comments!
Robert
[-- Attachment #2: hcidump.connect.bin --]
[-- Type: application/octet-stream, Size: 1513 bytes --]
[-- Attachment #3: hcidump.connect_no_rswitch.bin --]
[-- Type: application/octet-stream, Size: 1352 bytes --]
[-- Attachment #4: hcidump.connect_voluntary_rswitch.bin --]
[-- Type: application/octet-stream, Size: 1611 bytes --]
next reply other threads:[~2005-10-08 13:25 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-08 13:25 Robert Siemer [this message]
2005-10-08 13:29 ` [Bluez-devel] Jumpy cursor with Wacom Graphire Bluetooth Marcel Holtmann
2005-10-08 14:23 ` Robert Siemer
2005-10-08 15:01 ` Marcel Holtmann
2005-10-08 16:30 ` Robert Siemer
2005-10-08 17:28 ` Dimitry Andric
2005-11-27 17:42 ` [Bluez-devel] " Robert Siemer
2005-11-27 18:26 ` Marcel Holtmann
2005-11-27 18:49 ` Robert Siemer
2005-11-27 19:26 ` Marcel Holtmann
2005-11-27 21:38 ` Robert Siemer
2005-11-27 21:56 ` Marcel Holtmann
2005-11-27 23:04 ` Robert Siemer
2005-11-27 23:11 ` Marcel Holtmann
2005-11-27 23:49 ` Robert Siemer
2005-11-28 0:02 ` Marcel Holtmann
2005-11-28 1:53 ` Robert Siemer
2005-11-28 2:08 ` Marcel Holtmann
2005-11-28 2:29 ` Robert Siemer
2005-11-28 2:57 ` Marcel Holtmann
2005-11-28 8:44 ` Robert Siemer
2005-11-28 9:00 ` Marcel Holtmann
2005-11-28 9:21 ` Robert Siemer
2005-11-28 9:36 ` Marcel Holtmann
2005-11-28 10:22 ` Robert Siemer
2005-11-28 10:29 ` Marcel Holtmann
2005-11-27 23:13 ` Robert Siemer
2005-11-27 21:24 ` Robert Siemer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20051008132533.GA954@polar.elf12.net \
--to=robert.siemer@backsla.sh \
--cc=bluez-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).