From: wwguy <wey-yi.w.guy@intel.com>
To: Stanislaw Gruszka <sgruszka@redhat.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
Intel Linux Wireless <ilw@linux.intel.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: bt coex active on iwlegacy?
Date: Wed, 08 Jun 2011 07:31:24 -0700 [thread overview]
Message-ID: <1307543484.5115.6.camel@wwguy-ubuntu> (raw)
In-Reply-To: <20110608140524.GB2283@redhat.com>
On Wed, 2011-06-08 at 07:05 -0700, Stanislaw Gruszka wrote:
> Is bt_coex_active=true useful on iwlegacy? Or could be removed,
> or assigned to false by default? I'm asking regarding random, rare
> connections hangs and microcode errors that some people have on 4965.
>
Back in 6000 time (2 years ago), we encounter problem on some of the
OEM's system has one of the pin raise high(I don't remember which pin)
all the time which cause our WiFi device believe there were BT traffic,
since BT traffic has higher priority then WiFi traffic, so the WiFi can
not establish connection. that is the main reason behind this module
parameter which used to disable bt coex. By default, the flag should set
to "true" unless the problem is being seen.
We continue to see this problem from time to time even it is not so
often.
Thanks
Wey
prev parent reply other threads:[~2011-06-08 14:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-08 14:05 bt coex active on iwlegacy? Stanislaw Gruszka
2011-06-08 14:31 ` wwguy [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=1307543484.5115.6.camel@wwguy-ubuntu \
--to=wey-yi.w.guy@intel.com \
--cc=ilw@linux.intel.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=sgruszka@redhat.com \
/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