From: David Vrabel <david.vrabel@csr.com>
To: Inga Stotland <ingas@codeaurora.org>
Cc: linux-bluetooth@vger.kernel.org, rshaffer@codeaurora.org,
johan.hedberg@gmail.com, marcel@holtmann.org
Subject: Re: Enhancements to allow l2cap channel to use either AMP or BR/EDR
Date: Mon, 02 Aug 2010 13:04:00 +0100 [thread overview]
Message-ID: <4C56B430.4040901@csr.com> (raw)
In-Reply-To: <1280514626-22559-1-git-send-email-ingas@codeaurora.org>
Inga Stotland wrote:
> AMP vs BR/EDR preference for L2CAP channel can be configured as
> command line argument using new option "-J". Possible values:
> "require_br_edr",
> "prefer_amp",
> "prefer_br_edr"
> If no preference indicated, the default is set to require BR/EDR.
I think an explicit channel move command and a channel move complete
event are what many applications/profiles will need to be able to use an
AMP effectively.
David
--
David Vrabel, Senior Software Engineer, Drivers
CSR, Churchill House, Cambridge Business Park, Tel: +44 (0)1223 692562
Cowley Road, Cambridge, CB4 0WZ http://www.csr.com/
Member of the CSR plc group of companies. CSR plc registered in England and Wales, registered number 4187346, registered office Churchill House, Cambridge Business Park, Cowley Road, Cambridge, CB4 0WZ, United Kingdom
next prev parent reply other threads:[~2010-08-02 12:04 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-30 18:30 Enhancements to allow l2cap channel to use either AMP or BR/EDR Inga Stotland
2010-07-30 18:30 ` [PATCH 1/4] Constants for L2CAP and AMP extensions Inga Stotland
2010-07-30 18:30 ` [PATCH 2/4] Use defines for the default values of txwin_size and max_transmit Inga Stotland
2010-07-30 18:30 ` [PATCH 3/4] Added command argument "-J" to indicate preference of using AMP vs BR/EDR Inga Stotland
2010-07-31 23:14 ` Gustavo F. Padovan
2010-08-02 6:18 ` ingas
2010-07-30 18:30 ` [PATCH 4/4] Allow changing AMP vs BR/EDR preference from stdin when connection is up Inga Stotland
2010-08-02 12:04 ` David Vrabel [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-08-02 16:55 Enhancements to allow l2cap channel to use either AMP or BR/EDR tmonahan
2010-08-02 18:53 ` Marcel Holtmann
2010-08-02 22:41 ` Kevin Hayes
2010-08-02 22:58 ` Marcel Holtmann
2010-08-03 0:51 ` Kevin Hayes
[not found] ` <B7132A25476D334D9130FE7532F2A56310A0B08A61@SC1EXMB-MBCL.global.athero s.com>
2010-08-03 1:30 ` Peter Krystad
2010-08-03 1:59 ` Marcel Holtmann
2010-08-03 8:07 ` Gustavo F. Padovan
2010-08-03 13:40 ` Tim Monahan-Mitchell
2010-08-03 1:59 ` Marcel Holtmann
2010-08-03 4:47 ` Kevin Hayes
2010-08-03 12:59 ` David Vrabel
2010-08-03 16:14 ` 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=4C56B430.4040901@csr.com \
--to=david.vrabel@csr.com \
--cc=ingas@codeaurora.org \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=rshaffer@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.