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
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Sat, 6 Jun 2015 06:45:23 +0200
From:	Marcel Holtmann <marcel@...tmann.org>
To:	Arend van Spriel <arend@...adcom.com>
Cc:	Jonas Thiem <jonasthiem@...glemail.com>,
	Jeremiah Mahler <jmmahler@...il.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	"linux-wireless@...r.kernel.org" <linux-wireless@...r.kernel.org>,
	linux-bluetooth <linux-bluetooth@...r.kernel.org>,
	Kalle Valo <kvalo@...eaurora.org>
Subject: Re: Interaction issue of intel wifi and broadcom bluetooth - it appears that nobody feels responsible for doing something

Hi Arend,

>> thanks for responding!
>> 
>> I did have my mobile phone very nearby also connected to the bluetooth
>> headphones while my laptop was still using 11n wifi. I didn't have any
>> noticeable issues with bluetooth there.
>> 
>> But I got the feeling that my phone's android drivers + hardware for
>> bluetooth are tuned better than the laptop ones, so maybe that just
>> means the phone is just better at jumping frequencies to avoid.
>> 
>> I guess the best test would be the same laptop model in direct
>> proximity, but sadly I only own that laptop once. ;)
>> 
>> I hope wireless interference wouldn't rule out that some driver work
>> would be considered to make it work better - after all, both chips are
>> in the same laptop and as per the intel comment, bluetooth is supposed
>> to work despite of wifi activity.
>> 
>> Regards,
>> Jonas Thiem
>> 
>> On 06/05/2015 06:45 AM, Jeremiah Mahler wrote:
>>> Jonas,
>>> 
>>> On Fri, Jun 05, 2015 at 01:00:32AM +0200, Jonas Thiem wrote:
>>>> Hi *,
>>>> 
>>>> this is my first post to this mailing list, sorry if it's not supposed
>>>> to go here. (also CC in responses would be nice since I'm not
>>>> subscribed)
>>>> 
>>>> I filed a bug about an intel centrino wifi interaction with broadcom's BCM2045B:
>>>> https://bugzilla.kernel.org/show_bug.cgi?id=97101
>>>> 
>>> Those are some unhelpful replies :-(
> 
> Indeed. Now my reply maybe of a similar nature as my knowledge of the bluetooth part is next to nil.
> 
>>>> In short, the two seem to kinda fight over the wireless spectrum and
>>>> both drop connections all the time - unless the 'iwlwifi' module is
>>>> loaded with 11n_disabled=1.
>>>> 
> 
> I guess you don't have a choice about the channel your access point is operating on. If you can you might move wifi channel to 5GHz although that will likely affect your range.
> 
> To get more info on your setup here a couple of questions.
> 
> What type of device are we talking about here?
> Bugzilla mentions Thinkpad X220, is that correct?
> Is your AP setup for 40MHz bandwidth?
> 
> I suppose both wifi and bt have their own antennas. When sharing antennas it needs to be coordinated who is using the antennas. This is called bt-coex. As said I don't think this is the case for your device, but if so I think there is still major development task needed as I saw email from Marcel about plans to develop a bt-coex subsystem in the kernel. Not sure if that also covers the case where bt and wifi do not share antennas.

from the report, we have to make the assumption that in this design it is two independent antennas. Meaning Bluetooth is going to win the spectrum war. It should play nice due to AFH support in almost every 4.0 device in the market, but there are limits. If your spectrum is busy, then it becomes really hard for AFH to function properly.

So in the case of two independent antennas, the rfres subsystem I am proposing would help indeed. We could tell the Bluetooth controller to block out the frequency that the WiFi chip is currently operating on.

Main problem is that these design are so rare these days that nobody actually cared enough to add this subsystem. If Bluetooth and WiFi are sharing the same antenna, the coex issue is solved by a direct connection between both chips.

Regards

Marcel

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ