From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Latest 2.6.16-mh1 patch.
Date: Thu, 22 Jun 2006 09:06:39 +0200 [thread overview]
Message-ID: <1150959999.13991.9.camel@localhost> (raw)
In-Reply-To: <449A297B.7010009@mail.utexas.edu>
Hi Philip,
> I tried with 17-mh1 and the behaviour is not as bad. I only see one
> problem: If I turn off the mouse and then quickly turn it back on,
> the mouse doesn't work until the old connection times out on the host
> side. At that point, the mouse can reconnect and life returns to normal.
>
> Reconnecting after a timeout disconnect or after turning off and waiting
> for the host to clean up is no longer a problem.
>
> In the problem case, hcidump reports no incoming packets between when
> I turn off and on and when it reports the disconnect. Then I see the
> reconnect and new packets.
>
> It's obviously not a big problem.
this seems that you have to wait for the link supervision timeout on the
host side. Play a little bit with it. If you turn off the Bluetooth chip
in the mouse the host simply needs some time to detect this.
What kind of chip is in your mouse? Is it CSR or Broadcom based?
Regards
Marcel
All the advantages of Linux Managed Hosting--Without the Cost and Risk!
Fully trained technicians. The highest number of Red Hat certifications in
the hosting industry. Fanatical Support. Click to learn more
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2006-06-22 7:06 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-07 6:26 Latest 2.6.16-mh1 patch Philip Langdale
2006-06-07 7:15 ` [Bluez-devel] " Marcel Holtmann
2006-06-07 15:18 ` Philip Langdale
2006-06-07 21:05 ` [Bluez-devel] " Marcel Holtmann
2006-06-08 5:05 ` Philip Langdale
2006-06-08 7:17 ` [Bluez-devel] " Marcel Holtmann
2006-06-08 21:56 ` Marcel Holtmann
2006-06-10 3:59 ` Philip Langdale
2006-06-11 0:33 ` [Bluez-devel] " Marcel Holtmann
2006-06-12 15:14 ` Philip Langdale
2006-06-15 2:07 ` Philip Langdale
2006-06-21 7:18 ` [Bluez-devel] " Marcel Holtmann
2006-06-21 13:29 ` Ulisses Furquim
2006-06-21 13:51 ` Marcel Holtmann
2006-06-22 5:24 ` Philip Langdale
2006-06-22 7:06 ` Marcel Holtmann [this message]
2006-06-22 14:34 ` Ulisses Furquim
2006-06-22 18:12 ` Marcel Holtmann
2006-06-23 4:24 ` Mayank Batra
2006-06-23 8:10 ` Marcel Holtmann
2006-06-26 14:25 ` Ulisses Furquim
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=1150959999.13991.9.camel@localhost \
--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