From: Robert Siemer <Robert.Siemer@backsla.sh>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Re: Jumpy cursor with Wacom Graphire Bluetooth
Date: Sun, 27 Nov 2005 22:38:35 +0100 [thread overview]
Message-ID: <20051127213835.GF15156@polar.elf12.net> (raw)
In-Reply-To: <1133119580.13629.13.camel@blade>
Hi Marcel!
> maybe the HID inside the Wacom is broken and needs a special quirk. This
> wouldn't be the first time. However also the Linux HID code can be at
> fault here. You still haven't send in enough information about that
> device to tell.
>
> Use "hcitool info..." and "sdptool browse --raw" to get some more
> information about the device.
panorama:/etc/udev# sdptool browse --raw
Inquiring ...
Should there be something? ("local" or the tablet address do the same:
empty)
panorama:/etc/udev# hcitool info 00:13:C2:00:11:2C
Requesting information ...
BD Address: 00:13:C2:00:11:2C
Device Name: WACOM Pen Tablet
LMP Version: 1.2 (0x2) LMP Subversion: 0x5df
Manufacturer: Cambridge Silicon Radio (10)
Features: 0xff 0xff 0x8f 0x78 0x18 0x18 0x00 0x80
<3-slot packets> <5-slot packets> <encryption> <slot offset>
<timing accuracy> <role switch> <hold mode> <sniff mode>
<park state> <RSSI> <channel quality> <SCO link> <HV2 packets>
<HV3 packets> <u-law log> <A-law log> <CVSD> <paging scheme>
<power control> <transparent SCO> <broadcast encrypt>
<enhanced iscan> <interlaced iscan> <interlaced pscan>
<inquiry with RSSI> <AFH cap. slave> <AFH class. slave>
<AFH cap. master> <AFH class. master> <extended features>
My questions were:
-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?
Thanks,
Robert
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-11-27 21:38 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-08 13:25 [Bluez-devel] Jumpy cursor with Wacom Graphire Bluetooth Robert Siemer
2005-10-08 13:29 ` 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 [this message]
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=20051127213835.GF15156@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).