linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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: Wed, 21 Jun 2006 15:51:45 +0200	[thread overview]
Message-ID: <1150897905.3950.42.camel@localhost> (raw)
In-Reply-To: <d23110170606210629g2c9f9cd3ue7c886987615718a@mail.gmail.com>

Hi Ulisses,

> > > >>> okay. I released patch-2.6.16-mh2 with doesn't contain the automatic
> > > >>> sniff mode feature anymore. Please check if your mouse is now working as
> > > >>> expected.
> > > >> Yep, that did the trick, but I hope you can get the two to play well
> > > >> together.
> > >
> > > I've been working with mh3 over the last couple of days and have
> > > noticed another regression. The mouse no longer auto-reconnects
> > > after being turned off and on or after it auto-disconnects due
> > > to a timeout.
> > >
> > > This didn't happen with mh2.
> >
> > so it is the automatic sniff mode feature mode again. Please get me the
> > hcidump when it times out and when it disconnects due to turned off. It
> > might include something that gives me a clue, because right now, I have
> > no idea why this might happen.
> 
> Yeah, I have no clue either. I've just went through the patch again
> looking for something wrong related to the disconnect timer but
> everything seemed ok. :-(

I can't think of anything either, but maybe setting idle_timeout to 0
makes it work again.

Regards

Marcel




_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2006-06-21 13:51 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 [this message]
2006-06-22  5:24                   ` Philip Langdale
2006-06-22  7:06                     ` Marcel Holtmann
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=1150897905.3950.42.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;
as well as URLs for NNTP newsgroup(s).