linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Jumpy cursor with Wacom Graphire Bluetooth
Date: Sat, 08 Oct 2005 15:29:27 +0200	[thread overview]
Message-ID: <1128778167.5212.8.camel@blade> (raw)
In-Reply-To: <20051008132533.GA954@polar.elf12.net>

Hi Robert,

> 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?

try again with patch-2.6.13-mh1 to add report mode protocol support.

> I played already around with role switching (forced, voluntary from the
> tablet, none). - Has no influence.

Forget about that. Use the default settings.

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2005-10-08 13:29 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 [this message]
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=1128778167.5212.8.camel@blade \
    --to=marcel@holtmann.org \
    --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).