All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Bastien Nocera <hadess@hadess.net>
Cc: Dan Tian <Dan.Tian@Atheros.com>,
	linux-bluetooth@vger.kernel.org,
	Haijun Liu <Haijun.Liu@Atheros.com>,
	Luis Rodriguez <Luis.Rodriguez@Atheros.com>
Subject: Re: [PATCH 1/3] Add BT3 AMP device support, by Atheros Linux BT3 team.
Date: Sat, 17 Jul 2010 19:00:53 -0700	[thread overview]
Message-ID: <1279418453.6282.93.camel@localhost.localdomain> (raw)
In-Reply-To: <1279411461.2424.9.camel@localhost.localdomain>

Hi Bastien,

> I'll take this opportunity to ask whether this chip is actually being
> used in currently sold devices, because I'd quite like to add a BT3
> device (or 2) to my collection.

so in theory you can use a Bluetooth 2.1 controller and an AMP driven in
software by mac80211 and you get a Bluetooth 3.0 + HS system.

There are Bluetooth 3.0 controller (note the missing HS), but the
difference to 2.1 is only an extra HCI command and some unicast support.
Otherwise they are the same. For a 3.0 + HS system you need a WiFi
controller that can act as a AMP as well. So essentially you see two HCI
devices. One will be the BR/EDR the other the AMP.

Regards

Marcel



  reply	other threads:[~2010-07-18  2:00 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-15  7:37 [PATCH 1/3] Add BT3 AMP device support, by Atheros Linux BT3 team Dan Tian
2010-07-15 14:29 ` David Vrabel
2010-07-15 15:09 ` Gustavo F. Padovan
2010-07-15 18:43   ` Luis R. Rodriguez
2010-07-15 19:42     ` Gustavo F. Padovan
2010-07-16  2:02       ` Dan Tian
2010-07-16  2:14       ` Haijun Liu
2010-07-16 16:08       ` Marcel Holtmann
2010-07-20  2:24         ` Dan Tian
2010-07-18  0:04 ` Bastien Nocera
2010-07-18  2:00   ` Marcel Holtmann [this message]
2010-07-27 12:00 ` David Vrabel
2010-07-28  5:39   ` Haijun Liu
2010-08-02 14:39 ` David Vrabel

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=1279418453.6282.93.camel@localhost.localdomain \
    --to=marcel@holtmann.org \
    --cc=Dan.Tian@Atheros.com \
    --cc=Haijun.Liu@Atheros.com \
    --cc=Luis.Rodriguez@Atheros.com \
    --cc=hadess@hadess.net \
    --cc=linux-bluetooth@vger.kernel.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.