From: David Vrabel <david.vrabel@csr.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: tmonahan@codeaurora.org, linux-bluetooth@vger.kernel.org
Subject: Re: RFC: QuIC's AMP + eL2CAP Technical Plans
Date: Mon, 08 Mar 2010 11:56:42 +0000 [thread overview]
Message-ID: <4B94E5FA.1020202@csr.com> (raw)
In-Reply-To: <1267753300.29510.25.camel@localhost.localdomain>
Marcel Holtmann wrote:
>
> The block-based flow control is a missing piece, but the AMP type
> extension has been merged upstream. We can create HCI_BREDR and
> HCI_80211 controllers now. The AMP controllers are for now forced to be
> raw devices, but that can be changed easily once we have the controller
> init for AMP up and ready.
Why HCI_80211 and not HCI_AMP? The stack shouldn't care what the AMP's
radio actually is and with some devices (e.g., standard SDIO ones) it's
not even possible to tell what the radio is.
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-03-08 11:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-04 22:49 RFC: QuIC's AMP + eL2CAP Technical Plans tmonahan
2010-03-05 1:41 ` Marcel Holtmann
2010-03-05 12:45 ` Luiz Augusto von Dentz
2010-03-07 4:37 ` tmonahan
2010-03-07 5:13 ` Marcel Holtmann
2010-03-08 11:56 ` David Vrabel [this message]
2010-03-08 14:52 ` tmonahan
2010-03-08 18:22 ` Marcel Holtmann
2010-08-09 21:30 ` Tim Monahan-Mitchell
2010-08-09 22:03 ` David Vrabel
2010-08-09 22:12 ` David Vrabel
2010-08-09 22:21 ` Tim Monahan-Mitchell
2010-03-13 17:30 ` Gustavo F. Padovan
-- strict thread matches above, loose matches on Subject: below --
2010-03-08 5:32 tmonahan
2010-03-08 6:31 ` 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=4B94E5FA.1020202@csr.com \
--to=david.vrabel@csr.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=tmonahan@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).