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] Re: Jumpy cursor with Wacom Graphire Bluetooth
Date: Sun, 27 Nov 2005 19:26:30 +0100	[thread overview]
Message-ID: <1133115990.13629.1.camel@blade> (raw)
In-Reply-To: <20051127174209.GB15156@polar.elf12.net>

Hi Robert,

> I'm picking up this thread because it is still unresolved...
> 
> 1) Finally I could update from 2.6.12-mh3 to 2.6.14-mh2.
>    With that I can prove Marcel wrong without repeating myself once
>    again: the tablet works as bad as before; no visible difference
>    between these two patched kernels.
> 
> 2) I would like to get some answers to my questions below. Marcel,
>    why are you ignoring them?

I think that I need the tablet by myself to do any further analysis. Try
to create a new hcidump which includes all HCI traffic. The latest
versions even decode HIDP for you. Send in the output of "hciconfig -a".

Regards

Marcel




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

  reply	other threads:[~2005-11-27 18:26 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 [this message]
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=1133115990.13629.1.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).