From: Szymon Janc <szymon.janc@gmail.com>
To: simon@mungewell.org
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH 1/5] lib: Add flag to double L2CAP IMTU size used for SDP connection
Date: Mon, 20 Jan 2014 21:00:17 +0100 [thread overview]
Message-ID: <5584991.ragWnAIfdC@athlon> (raw)
In-Reply-To: <649bfd2b8da26f5cf4b19f59d40d26fc.squirrel@mungewell.org>
Hi Simon,
On Monday 20 January 2014 12:31:14 simon@mungewell.org wrote:
<snip>
> I also noticed a weird log at one point, although only saw this once and
> don't know what triggered it.
> --
> [bluetooth]#
> [CHG] Device 1C:66:6D:07:C3:E0 Class: 0x200404
> [CHG] Device 1C:66:6D:07:C3:E0 Icon: audio-card <--------!!
> [CHG] Device 1C:66:6D:07:C3:E0 Class: 0x002508
> [CHG] Device 1C:66:6D:07:C3:E0 Icon: input-gaming
> --
Yes, I've seen this as well. I suspect that DS4 has some extra features
related to audio (it has jack for headphones) and it enables that for PS4
only, possibly switching to 'gamepad mode' if not connected to PS4. Maybe
related to connecting USB first or sth...
But this is just my suspicion...
--
Szymon K. Janc
szymon.janc@gmail.com
prev parent reply other threads:[~2014-01-20 20:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-20 0:31 [PATCH 1/5] lib: Add flag to double L2CAP IMTU size used for SDP connection Szymon Janc
2014-01-20 0:31 ` [PATCH 2/5] core: Opencode get_sdp_session in sdp-client Szymon Janc
2014-01-20 0:31 ` [PATCH 3/5] core: Add flags parameter to bt_search_service Szymon Janc
2014-01-20 0:31 ` [PATCH 4/5] device: Add workaround for Sony Dualshock 4 broken SDP Szymon Janc
2014-01-20 0:31 ` [PATCH 5/5] device: Match Dualshock4 with name and class Szymon Janc
2014-01-20 17:31 ` [PATCH 1/5] lib: Add flag to double L2CAP IMTU size used for SDP connection simon
2014-01-20 20:00 ` Szymon Janc [this message]
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=5584991.ragWnAIfdC@athlon \
--to=szymon.janc@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=simon@mungewell.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).