[ath9k-devel] MCI howto?
Adrian Chadd <[email protected]>
| Newsgroups | org.ath9k.lists.ath9k-devel |
|---|---|
| Message-ID | <CAJ-VmonHMVhQ7u76sHSs6_r2w1odCqAWRuAj6fYPLmZcB1dBKQ@mail.gmail.com> |
github.com/freebsd/freebsd - in sys/dev/ath/if_ath_btcoex_mci.[ch] and the HAL in sys/contrib/dev/ath/ath_hal/ar9300/ -a On 5 June 2016 at 23:37, sandeep suresh <[email protected]> wrote: > Thanks Adrian. In the meatime, can you share the link in FreeBSD where we > can look into the code? > Thanks. > Sandeep. > > > On Saturday, 4 June 2016 10:32 PM, Adrian Chadd <[email protected]> wrote: > > > i'm documenting more details in freebsd as I figure stuff out. I'll > write up a webpage with what I can glean from the drivers/headers. > > > > -adrian > > > On 2 June 2016 at 21:44, sandeep suresh <[email protected]> wrote: >> Adrian, can you please share the details on the MCI protocol >> specifications? >> Thanks & regards >> Sandeep. >> >> >> On Sunday, 29 May 2016 11:44 PM, Adrian Chadd <[email protected]> wrote: >> >> >> 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 >> _______________________________________________ >> ath9k-devel mailing list >> ath9k-devel at lists.ath9k.org >> https://lists.ath9k.org/mailman/listinfo/ath9k-devel >> >> > >