From: Solomon Peachy <pizza@shaftnet.org>
To: Kevin Groeneveld <kgroeneveld@gmail.com>
Cc: Dmitry Tarnyagin <abi.dmitryt@gmail.com>,
Dmitry Tarnyagin <dmitry.tarnyagin@stericsson.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCHv2 00/21] cw1200: ST-Ericsson cw1200 wlan device driver
Date: Thu, 10 May 2012 09:07:11 -0400 [thread overview]
Message-ID: <20120510130711.GA15533@shaftnet.org> (raw)
In-Reply-To: <CABF+-6VUMoueQTA5_JUEOjiya5eQY=bAzt=cnr23HJ=ssedQSw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1066 bytes --]
On Wed, May 09, 2012 at 04:59:21PM -0400, Kevin Groeneveld wrote:
> As I mentioned in a previous post I am using the SG901-1091 module
> from Sagrad. The only SDD file I have tried that works is also from
> Sagrad. It makes perfect sense now that SDD files from other sources
> do not work.
>
> I still wonder why there is a PTA record in the SDD file if the
> SG901-1091 module does not have Bluetooth. Could this negatively
> effect performance if it is trying to play nice with Bluetooth when
> Bluetooth is not being used?
I don't believe it will cause any problems, as the bluetooth pins aren't
hooked up on the SG901-1091 module. That said, the PTA record on the
current Sagrad SDD files for the 1091/1098 modules specifies that BT
coexistence is disabled (ePTA mode = 0), so it should be functionally
equivalent to no PTA record being present.
- Solomon
--
Solomon Peachy pizza at shaftnet dot org
Melbourne, FL ^^ (mail/jabber/gtalk) ^^
Quidquid latine dictum sit, altum viditur.
[-- Attachment #2: Type: application/pgp-signature, Size: 190 bytes --]
next prev parent reply other threads:[~2012-05-10 13:07 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-02 15:22 [PATCHv2 00/21] cw1200: ST-Ericsson cw1200 wlan device driver Kevin Groeneveld
2012-05-02 16:01 ` Dmitry Tarnyagin
[not found] ` <CABF+-6XbdG_QMa0iQJMpbOsr4bXCq4mDEB6unkM8jxNGWYwFyQ@mail.gmail.com>
2012-05-02 16:51 ` Kevin Groeneveld
[not found] ` <4FA23DA0.3030207@stericsson.com>
2012-05-03 16:42 ` Kevin Groeneveld
2012-05-03 17:23 ` Dmitry Tarnyagin
2012-05-03 18:57 ` Kevin Groeneveld
2012-05-03 21:57 ` Janusz Dziedzic
2012-05-04 0:10 ` Kevin Groeneveld
2012-05-04 21:40 ` Kevin Groeneveld
2012-05-05 7:20 ` Janusz Dziedzic
2012-05-07 9:25 ` Janusz Dziedzic
2012-05-07 19:54 ` Kevin Groeneveld
2012-05-09 17:03 ` Kevin Groeneveld
2012-05-09 18:24 ` Dmitry Tarnyagin
2012-05-09 18:33 ` Johannes Berg
2012-05-09 18:56 ` Kevin Groeneveld
2012-05-09 19:37 ` Dmitry Tarnyagin
2012-05-09 20:37 ` Solomon Peachy
2012-05-09 20:59 ` Kevin Groeneveld
2012-05-10 13:07 ` Solomon Peachy [this message]
2012-05-10 20:03 ` Kevin Groeneveld
[not found] <983b0e2d75af161b8e4dec02fc3497926a0080df-submit>
2012-03-02 20:26 ` Dmitry Tarnyagin
2012-05-09 6:58 ` Dmitry Tarnyagin
2012-05-31 5:45 ` Janusz Dziedzic
2012-07-05 18:16 ` Steev Klimaszewski
2012-07-06 20:18 ` John W. Linville
2012-12-11 23:23 ` Solomon Peachy
2012-12-12 14:40 ` Kalle Valo
2012-12-12 15:13 ` Christian Lamparter
2012-12-12 16:18 ` Solomon Peachy
2012-12-12 16:20 ` Johannes Berg
2012-12-13 14:53 ` Solomon Peachy
2012-12-12 18:19 ` John W. Linville
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=20120510130711.GA15533@shaftnet.org \
--to=pizza@shaftnet.org \
--cc=abi.dmitryt@gmail.com \
--cc=dmitry.tarnyagin@stericsson.com \
--cc=kgroeneveld@gmail.com \
--cc=linux-wireless@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 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).