From: David Vrabel <david.vrabel@csr.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: "Luis R. Rodriguez" <lrodriguez@atheros.com>,
Marcel Holtmann <marcel@holtmann.org>,
linux-wireless <linux-wireless@vger.kernel.org>,
linux-bluetooth <linux-bluetooth@vger.kernel.org>,
Dan Tian <Dan.Tian@atheros.com>, Kevin Hayes <kevin@atheros.com>
Subject: Re: Coordinating development for Bluetooth 3.0 between 802.11 and BT trees
Date: Fri, 12 Feb 2010 18:48:17 +0000 [thread overview]
Message-ID: <4B75A271.7010705@csr.com> (raw)
In-Reply-To: <20100212183309.GB4983@tuxdriver.com>
John W. Linville wrote:
>
> In any case, I was under the impression that at least the initial
> parts of the 802.11 AMP implementation could happen independently
> from any bluetooth stack changes...?
You should be able to do (almost) all of the AMP PAL development and
testing without a Bluetooth stack.
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-02-12 18:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-11 20:10 Coordinating development for Bluetooth 3.0 between 802.11 and BT trees Luis R. Rodriguez
2010-02-12 18:33 ` John W. Linville
2010-02-12 18:48 ` David Vrabel [this message]
2010-02-12 19:16 ` Marcel Holtmann
2010-02-13 0:09 ` 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=4B75A271.7010705@csr.com \
--to=david.vrabel@csr.com \
--cc=Dan.Tian@atheros.com \
--cc=kevin@atheros.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=lrodriguez@atheros.com \
--cc=marcel@holtmann.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).