From: Geoff Levand <geoffrey.levand@am.sony.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: BlueZ development <bluez-devel@lists.sourceforge.net>,
cbe-oss-dev@ozlabs.org, bluez-devel@lists.sf.net
Subject: Re: [Cbe-oss-dev] [Bluez-devel] [PATCH] bluetooth: reset unexpected connections
Date: Tue, 03 Jul 2007 11:26:25 -0700 [thread overview]
Message-ID: <468A94D1.7050107@am.sony.com> (raw)
In-Reply-To: <1183433306.6351.19.camel@aeonflux.holtmann.net>
Marcel Holtmann wrote:
> Hi Ranulf,
>
>> Send a reset command to any device that sends us data when there is no
>> active
>> connection to that device. This hopefully discourages the device from
>> sending
>> any more data which causes the syslog to fill up rapidly otherwise.
>>
>> Signed-off-by: Ranulf Doswell <ralf@ranulf.net>
>>
>> ---
>>
>> An example device which causes this problem is the Sony Playstation
>> six-axis
>> controller which continues sending data even after the host is
>> rebooted as
>> the linux kernel stack returns before the controller's stack times
>> out.
>
> this is not a proper fix for this problem. And you only reset the local
> host controller. There is no way to send a reset to the remote device.
>
> Did you ever used hcidump and try to find out, why the other side still
> things that we are connected. Especially why the local controller things
> that we are still connected.
>
> The PS3 remote controller (and the PS3 itself) have special hacked up
> version of Bluetooth firmware to play nice with remote wakeup. So it
> might simply be an issue with them and it might be better we declare
> them broken instead of adding nasty crap in a clean Bluetooth core. Your
> patch is nasty crap since I haven't seen any real argument why we should
> reset our local controller in that case. It is wild guessing.
I'll look at this in more detail when I have some time, maybe in a month or so.
-Geoff
next prev parent reply other threads:[~2007-07-03 18:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-02 19:04 [Bluez-devel] [PATCH] bluetooth: reset unexpected connections Ranulf Doswell
2007-07-03 3:28 ` Marcel Holtmann
2007-07-03 18:26 ` Geoff Levand [this message]
2007-07-03 19:38 ` Ranulf Doswell
2007-07-04 1:55 ` Marcel Holtmann
2007-07-04 7:05 ` [Cbe-oss-dev] " Ranulf Doswell
2007-07-04 9:56 ` [Bluez-devel] [Cbe-oss-dev] " Geert Uytterhoeven
2007-07-05 8:11 ` Marcel Holtmann
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=468A94D1.7050107@am.sony.com \
--to=geoffrey.levand@am.sony.com \
--cc=bluez-devel@lists.sf.net \
--cc=bluez-devel@lists.sourceforge.net \
--cc=cbe-oss-dev@ozlabs.org \
--cc=marcel@holtmann.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