Am 2011-01-31 16:28, schrieb Kalle Valo: > Sorry, but this was an awful hack in the fremantle kernel and I really > would not like to see this in the upstream driver. We should do better > than that :) And besides, who would use it? The only user I know is > maemo's wlancond and maemo is dead and buried anyway. RIP > > I'm not saying that we don't need this, I just want to understand > where we need this. And also sysfs is not the best choise imho, maybe > debugfs is better? I understand that you don't like this patch upstream, but I also think that it is a very useful feature to switch btcoex on/off. Moreover I think 3 states aren't needed at all, but we should at least be able to disable it completely. Maybe we could also detect if bt is enabled/disabled in kernel and switch the btcoex automatically? By the way, how is this problem solved in other drivers? >> It should be noted that this driver always enabled bt-coexistence before >> and enabled bt-coexistence directly affects the receiving performance, >> rendering it unusable in some low-signal situations. Especially monitor >> mode is affected very badly with bt-coexistence enabled. > > Yes, btcoex is very tricky to get right. Also one problem is that > wl1251's btcoex implementation significantly increases power > consumption. One more point to make it switchable. -- 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
