From: 'Emeltchenko Andrei' <Andrei.Emeltchenko.news@gmail.com>
To: Peter Krystad <pkrystad@codeaurora.org>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [RFCv0 00/20] RFC A2MP implementation
Date: Fri, 4 Nov 2011 09:47:55 +0200 [thread overview]
Message-ID: <20111104074747.GA1313@aemeltch-MOBL1> (raw)
In-Reply-To: <000f01cc9a87$94d0dc00$be729400$@org>
Hi Peter,
On Thu, Nov 03, 2011 at 05:20:38PM -0700, Peter Krystad wrote:
>
> Hi Andrei,
>
> > From: Andrei Emeltchenko <andrei.emeltchenko@intel.com>
> >
> > RFC meant to indicate our current development status.
> >
> > Code based on Code Aurora (git://codeaurora.org/kernel/msm.git) and
> Atheros
> > (search for: [PATCH 2/3] Add a2mp protocol/AMP manager, by Atheros Linux
> BT3)
> > implementations (mostly Code Aurora). Main difference to the original code
> is
> > - code rebase against recent bluetooth-next
> > - rewritten way to send A2MP msgs
> > - handling fixed channel modifications
> > - I was trying to separate AMP vs A2MP name usage. AMP is used for
> > "Alternate MAC PHY" controller, A2MP for "AMP Manager Protocol".
> > - fixes related to PTS beta A2MP tests
>
> I think your approach looks fine so far. Do you plan to continue on with
> adding detail to the patches in this series or will just do cleanup on them
> and then prepare another set?
I was thinking about rebasing first against recent bluetooth-next (since
my code was based upon a bit different approach (like fixed channel
features list patch).
Then I am planning to add some details to A2MP message
processing. Those I could test and verify with PTS "beta A2MP" tests.
After that I was thinking about adding physlink structure (at least
heplers) and then make interface to create fake/virtual AMP so that I
could use it for A2MP Discover, etc. (maybe we could use real wifi cheap
for e.g. AMPAssoc data).
What are your plans?
Best regards
Andrei Emeltchenko
prev parent reply other threads:[~2011-11-04 7:47 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-02 14:02 [RFCv0 00/20] RFC A2MP implementation Emeltchenko Andrei
2011-11-02 14:02 ` [RFCv0 01/20] Bluetooth: A2MP: create A2MP socket Emeltchenko Andrei
2011-11-02 14:02 ` [RFCv0 02/20] Bluetooth: A2MP: sk_data_ready for a2mp socket Emeltchenko Andrei
2011-11-02 14:02 ` [RFCv0 03/20] Bluetooth: A2MP: sk_state_change " Emeltchenko Andrei
2011-11-02 14:02 ` [RFCv0 04/20] Bluetooth: A2MP: build and send msg helpers Emeltchenko Andrei
2011-11-02 14:02 ` [RFCv0 05/20] Bluetooth: A2MP: AMP Manager basic functions Emeltchenko Andrei
2011-11-02 14:02 ` [RFCv0 06/20] Bluetooth: A2MP: Remove AMP manager in state_change Emeltchenko Andrei
2011-11-02 14:02 ` [RFCv0 07/20] Bluetooth: A2MP: AMP manager initialization Emeltchenko Andrei
2011-11-02 14:02 ` [RFCv0 08/20] Bluetooth: A2MP: Definitions for A2MP commands Emeltchenko Andrei
2011-11-02 14:02 ` [RFCv0 09/20] Bluetooth: A2MP: process A2MP messages Emeltchenko Andrei
2011-11-02 14:02 ` [RFCv0 10/20] Bluetooth: A2MP: processing A2MP command reject Emeltchenko Andrei
2011-11-02 14:02 ` [RFCv0 11/20] Bluetooth: A2MP: helper functions to count HCI devs Emeltchenko Andrei
2011-11-02 14:02 ` [RFCv0 12/20] Bluetooth: A2MP: process A2MP Discover Request Emeltchenko Andrei
2011-11-02 14:02 ` [RFCv0 13/20] Bluetooth: A2MP: process A2MP Change Notify Emeltchenko Andrei
2011-11-02 14:02 ` [RFCv0 14/20] Bluetooth: A2MP: process A2MP Get Info Request Emeltchenko Andrei
2011-11-02 14:02 ` [RFCv0 15/20] Bluetooth: A2MP: process A2MP Get AMP Assoc Request Emeltchenko Andrei
2011-11-02 14:02 ` [RFCv0 16/20] Bluetooth: A2MP: process A2MP Create Physlink Request Emeltchenko Andrei
2011-11-02 14:02 ` [RFCv0 17/20] Bluetooth: A2MP: process A2MP Disc " Emeltchenko Andrei
2011-11-02 14:02 ` [RFCv0 18/20] Bluetooth: A2MP: process A2MP Command Responses Emeltchenko Andrei
2011-11-02 14:02 ` [RFCv0 19/20] Bluetooth: A2MP: handling fixed channel Emeltchenko Andrei
2011-11-02 14:02 ` [RFCv0 20/20] Bluetooth: A2MP: manage incoming connection Emeltchenko Andrei
2011-11-04 0:20 ` [RFCv0 00/20] RFC A2MP implementation Peter Krystad
2011-11-04 7:47 ` 'Emeltchenko Andrei' [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=20111104074747.GA1313@aemeltch-MOBL1 \
--to=andrei.emeltchenko.news@gmail.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