From: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
To: Mike Tsai <Mike.Tsai@atheros.com>
Cc: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Subject: Re: detecting dead link
Date: Fri, 16 Apr 2010 16:19:13 +0300 [thread overview]
Message-ID: <h2x2d5a2c101004160619w9bc99d1es5ecee3acb6caf615@mail.gmail.com> (raw)
In-Reply-To: <35B17FE5076C7040809188FBE7913F983A1E128B77@SC1EXMB-MBCL.global.atheros.com>
Hi,
On Thu, Apr 15, 2010 at 12:09 AM, Mike Tsai <Mike.Tsai@atheros.com> wrote:
>>>Ok, so I do miss understanding the situation. In that case, host can program link supervision timeout to a shorter time (like 3 or 4 seconds) as suggested. So the link supervision timeout shall kick in far ahead of LMP response timeout. The user will get disconnect notification sooner,
It seems that somebody already give us a favor and patented it:
http://www.freepatentsonline.com/y2009/0258596.html
That is exactly what I was looking for, depending on the link usage
(a2dp, sco) reduce the link supervision timeout to detect the link
loss faster. Well I guess the only option now is to do this
statically, which I don't think will address the problem completely
since we can only change the timeout once due to this patent.
Grrr, it is so obvious why people patent such generic usage, I really
hate software patents. Very frustrating.
--
Luiz Augusto von Dentz
Computer Engineer
next prev parent reply other threads:[~2010-04-16 13:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-14 8:10 detecting dead link Luiz Augusto von Dentz
2010-04-14 16:31 ` Mike Tsai
2010-04-14 19:29 ` Luiz Augusto von Dentz
2010-04-14 19:49 ` Mike Tsai
2010-04-14 20:34 ` Luiz Augusto von Dentz
2010-04-14 21:09 ` Mike Tsai
2010-04-16 13:19 ` Luiz Augusto von Dentz [this message]
2010-04-15 7:54 ` Andrei Emeltchenko
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=h2x2d5a2c101004160619w9bc99d1es5ecee3acb6caf615@mail.gmail.com \
--to=luiz.dentz@gmail.com \
--cc=Mike.Tsai@atheros.com \
--cc=linux-bluetooth@vger.kernel.org \
/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).