From: Timur Mehrvarz <timur.mehrvarz@googlemail.com>
To: Peter Krystad <pkrystad@codeaurora.org>
Cc: linux-bluetooth@vger.kernel.org
Subject: Add BT 3.0+HS signalling definitions
Date: Tue, 25 Oct 2011 03:43:26 +0200 [thread overview]
Message-ID: <4EA6143E.4000606@googlemail.com> (raw)
In-Reply-To: <1319497579-8859-1-git-send-email-pkrystad@codeaurora.org>
When will HS become available to Linux devices (PC/Smartphone)?
Thank you.
Timur
On 25.10.2011 01:06, Peter Krystad wrote:
> This patchset adds definitions for BT 3.0+HS signalling
>
> Peter Krystad (2):
> Add L2CAP Create/Move Channel definitions
> Add A2MP definitions
>
> lib/a2mp.h | 131 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> lib/l2cap.h | 44 ++++++++++++++++++++
> 2 files changed, 175 insertions(+), 0 deletions(-)
> create mode 100644 lib/a2mp.h
>
next prev parent reply other threads:[~2011-10-25 1:43 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-24 23:06 [PATCH bluez 0/2] Add BT 3.0+HS signalling definitions Peter Krystad
2011-10-24 23:06 ` [PATCH bluez 1/2] Add L2CAP Create/Move Channel definitions Peter Krystad
2011-10-24 23:06 ` [PATCH bluez 2/2] Add A2MP definitions Peter Krystad
2011-10-25 1:43 ` Timur Mehrvarz [this message]
2011-10-25 7:38 ` GATT Dbus API on BlueZ Ganir, Chen
2011-10-25 12:52 ` Claudio Takahasi
2011-10-25 13:19 ` Ganir, Chen
2011-10-26 0:06 ` Claudio Takahasi
2011-10-26 7:20 ` GATT Dbus API on BlueZ - attirbute-api.txt modifications Ganir, Chen
2011-10-27 7:16 ` Mat Martineau
2011-10-27 8:22 ` Ganir, Chen
2011-10-27 11:30 ` Mat Martineau
2011-10-27 13:31 ` Luiz Augusto von Dentz
2011-10-27 13:57 ` Anderson Lizardo
2011-10-27 14:02 ` Anderson Lizardo
2011-10-27 14:58 ` Ganir, Chen
2011-10-27 15:13 ` Anderson Lizardo
2011-10-27 15:18 ` Ganir, Chen
2011-10-27 15:35 ` Anderson Lizardo
2011-10-27 15:06 ` Ganir, Chen
2011-10-27 15:29 ` Anderson Lizardo
2011-10-27 15:48 ` Ganir, Chen
2011-10-27 16:29 ` Anderson Lizardo
2011-10-27 16:47 ` Ganir, Chen
2011-10-27 17:32 ` Anderson Lizardo
2011-10-30 6:56 ` Ganir, Chen
2011-10-30 14:23 ` Anderson Lizardo
2011-10-30 15:48 ` Ganir, Chen
2011-10-30 18:02 ` Anderson Lizardo
2011-10-31 6:38 ` Ajay Pillai
2011-10-31 6:57 ` Ganir, Chen
2011-10-31 8:04 ` Ajay Pillai
2011-10-31 10:47 ` Anderson Lizardo
2011-10-31 7:19 ` Ganir, Chen
2011-10-31 11:07 ` Anderson Lizardo
2011-10-31 13:35 ` Ajay Pillai
2011-10-31 14:53 ` Luiz Augusto von Dentz
2011-10-28 16:19 ` Brian Gix
2011-10-28 20:09 ` Anderson Lizardo
2011-10-27 13:32 ` Anderson Lizardo
2011-10-31 17:41 ` Tsai, Mike
2012-01-11 14:25 ` GATT Dbus API on BlueZ Vijaykumar Dadmode
2012-01-11 14:57 ` Claudio Takahasi
2011-10-25 14:41 ` Add BT 3.0+HS signalling definitions Peter Krystad
2011-10-26 0:15 ` Timur Mehrvarz
2011-10-26 7:54 ` Andrei Emeltchenko
2011-10-27 13:39 ` BT 3.0+HS Timur Mehrvarz
2011-10-27 16:46 ` tim.howes
2011-11-03 16:38 ` Timur Mehrvarz
2011-10-26 7:36 ` [PATCH bluez 0/2] Add BT 3.0+HS signalling definitions Andrei Emeltchenko
2011-10-26 17:44 ` Peter Krystad
2011-10-27 8:00 ` 'Andrei Emeltchenko'
2011-10-28 0:23 ` Peter Krystad
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=4EA6143E.4000606@googlemail.com \
--to=timur.mehrvarz@googlemail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=pkrystad@codeaurora.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).