linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Vrabel <david.vrabel@csr.com>
To: tmonahan@codeaurora.org
Cc: Marcel Holtmann <marcel@holtmann.org>, linux-bluetooth@vger.kernel.org
Subject: Re: RFC: QuIC's AMP + eL2CAP Technical Plans
Date: Mon, 09 Aug 2010 23:12:28 +0100	[thread overview]
Message-ID: <4C607D4C.8090407@csr.com> (raw)
In-Reply-To: <4C607B43.2050207@csr.com>

David Vrabel wrote:
> Tim Monahan-Mitchell wrote:
>>
>> If the HCI_80211 symbol in hci.h is changed instead to HCI_AMP, where
>> should the 0x01 value for '802.11 AMP Controller' (listed in
>> Bluetooth.org's Assigned Number listing for Controller_Type) go?e
> 
> I don't think it needs to go anywhere, the actual values aren't 
> important from the point of view of the AMP manager.

I may have misunderstood your question.  There will need to be an 
additional "controller_type" field which will get filled in when the 
local amp info is read from the controller.

There will also need to be a table somewhere mapping controller types to 
dedicated amp link key length and KeyID.  The will be filled in from the 
assigned numbers and will be a very short table one 1 entry for now.

I do not think we need #define for the various AMP controller types.

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

  reply	other threads:[~2010-08-09 22:12 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
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 [this message]
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=4C607D4C.8090407@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).