Hi Suraj, > > Why would this need a userspace utility? Are you cloning some sort of > > windows architecture here? > > Ugh, please trim your quotes and use a useful mailer that will indent things. > > > It will be the userpace bluez dbus events that can provide information > > regarding the status of variout Bluetooth events. > > On receiving that information, it can send corresponding NL80211 > > command. > > Doesn't the kernel's bluetooth subsystem already know anyway? > > Not all of the information I believe. Things like A2DP streaming will be best known at the userspace. Also, there is no way to tap these information at the kernel subsystem right now. But, there is a clear defined way to get these information at the userspace. Also, profile based information might not be available at the kernel space. this looks like the total wrong approach to me. This needs to be done between mac80211 and Bluetooth subsystems in the kernel directly. Going through userspace for this is a pretty bad idea. Especially if you wanna listen on D-Bus events from bluetoothd and then run another process to then execute nl80211 commands looks like total overhead at no gain. Not to talk about potential latency effects that might be counterproductive. What you really want is a way to mark A2DP channels for streaming from userspace as streaming/realtime/priority so the Bluetooth subsystem knows on what to do with it and that way can also tell mac80211 correctly about coex settings. We are already settings flushable flags for A2DP streaming channels and there is work ongoing for SO_PRIORITY support with L2CAP sockets. Regards Marcel -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
