lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-ID: <874mr3xjnx.fsf_-_@kamboji.qca.qualcomm.com> Date: Tue, 03 Feb 2015 14:29:38 +0200 From: Kalle Valo <kvalo@...eaurora.org> To: Marcel Holtmann <marcel@...tmann.org> Cc: Larry Finger <Larry.Finger@...inger.net>, linux-wireless <linux-wireless@...r.kernel.org>, Troy Tan <troy_tan@...lsil.com.cn>, netdev@...r.kernel.org, linux-bluetooth@...r.kernel.org Subject: btcoex subsystem Marcel Holtmann <marcel@...tmann.org> writes: >> I will work on combining the latest BT drivers from Realtek with >> btusb to see if I can achieve a patch that will both work with the >> Realtek hardware, and get approval from the reviewers. >> >> What would be an approved method of communicating between two kernel >> modules? Is there some example in the kernel that I could study? > > We need a btcoex subsystem that both WiFi and Bluetooth can register > to and communicate with. The need for this seems to periodically come up, I remember needing something like that back in the Maemo wl1251 days and also ath6kl needed this. Are there any ideas for this subsystem? How would this btcoex subsystem work? What kind of information would it provide? Is this something we should discuss at Ottawa? -- Kalle Valo -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists