From: Adrian Chadd <adrian@freebsd.org>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] MCI howto?
Date: Sun, 29 May 2016 11:14:23 -0700 [thread overview]
Message-ID: <CAJ-Vmonq+8ESvmO2bpwejQRhMAHXm3e98CCuKoPWJswn83PiWQ@mail.gmail.com> (raw)
hiya!
I'm trying to bring up MCI bluetooth coexistence on the QCA9565 on
FreeBSD. I'm having no end of trouble - it seems that no matter what I
do, the bluetooth always wins and the wifi side disconnects when the
bt does an active scan (HCI "inquiry".)
Does anyone remember the deep and amusing details about MCI support
and how to debug this? I'm sure it's something stupid, but my time at
QCA involved 2-wire and 3-wire coex (which you can debug with a
scope), not MCI :(
Thanks!
-adrian
next reply other threads:[~2016-05-29 18:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-29 18:14 Adrian Chadd [this message]
2016-06-03 4:44 ` [ath9k-devel] MCI howto? sandeep suresh
2016-06-04 17:02 ` Adrian Chadd
2016-06-06 6:37 ` sandeep suresh
2016-06-06 23:58 ` Adrian Chadd
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=CAJ-Vmonq+8ESvmO2bpwejQRhMAHXm3e98CCuKoPWJswn83PiWQ@mail.gmail.com \
--to=adrian@freebsd.org \
--cc=ath9k-devel@lists.ath9k.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 read-only IMAP folder(s) and NNTP newsgroup(s).