Re: Intel Wireless 7260 failed to work

On Wed, 2016-12-28 at 11:59 +0800, Peter Xu wrote: > On Tue, Dec 27, 2016 at 09:46:55PM +0200, Kalle Valo wrote: > > Peter Xu writes: > > > > > Looks like latest Linux master (4.10-rc1, 7ce7d89f) cannot work well > > > with my wireless card, which is: > > > > > > Intel

Re: Intel Wireless 7260 failed to work

On Tue, Dec 27, 2016 at 09:46:55PM +0200, Kalle Valo wrote: > Peter Xu writes: > > > Looks like latest Linux master (4.10-rc1, 7ce7d89f) cannot work well > > with my wireless card, which is: > > > > Intel Corporation Wireless 7260 (rev bb) > > > > Boot message shows that no

Re: Intel Wireless 7260 failed to work

On Tue, Dec 27, 2016 at 10:41:22AM -0600, Larry Finger wrote: > On 12/27/2016 03:17 AM, Peter Xu wrote: > >Hello, > > > >Looks like latest Linux master (4.10-rc1, 7ce7d89f) cannot work well > >with my wireless card, which is: > > > > Intel Corporation Wireless 7260 (rev bb) > > > >Boot message

Re: Intel Wireless 7260 failed to work

Peter Xu writes: > Looks like latest Linux master (4.10-rc1, 7ce7d89f) cannot work well > with my wireless card, which is: > > Intel Corporation Wireless 7260 (rev bb) > > Boot message shows that no suitable firmware found: > > # journalctl -kp3 > Dec 27 16:38:00

[PATCH 2/2] ath9k: ar9003_mac: kill off ACCESS_ONCE()

For several reasons, it is desirable to use {READ,WRITE}_ONCE() in preference to ACCESS_ONCE(), and new code is expected to use one of the former. So far, there's been no reason to change most existing uses of ACCESS_ONCE(), as these aren't currently harmful. However, for some new features (e.g.

[PATCH 0/2] ath9k: kill of ACCESS_ONCE() in MAC drivers

For several reasons, it would be beneficial to kill off ACCESS_ONCE() tree-wide, in favour of {READ,WRITE}_ONCE(). These work with aggregate types, more obviously document their intended behaviour, and are necessary for tools like KTSAN to work correctly (as otherwise reads and writes cannot be

[PATCH 1/2] ath9k: ar9002_mac: kill off ACCESS_ONCE()

For several reasons, it is desirable to use {READ,WRITE}_ONCE() in preference to ACCESS_ONCE(), and new code is expected to use one of the former. So far, there's been no reason to change most existing uses of ACCESS_ONCE(), as these aren't currently harmful. However, for some new features (e.g.

Re: Intel Wireless 7260 failed to work

On 12/27/2016 03:17 AM, Peter Xu wrote: Hello, Looks like latest Linux master (4.10-rc1, 7ce7d89f) cannot work well with my wireless card, which is: Intel Corporation Wireless 7260 (rev bb) Boot message shows that no suitable firmware found: # journalctl -kp3 Dec 27 16:38:00

[PATCH] ath10k: Enable advertising support for channel 169, 5Ghz

From: Mohammed Shafi Shajakhan Enable advertising support for channel 169, 5Ghz so that based on the regulatory domain(country code) this channel shall be active for use. For example in countries like India this channel shall be available for use with latest regulatory

Re: [PATCH v3 3/3] nfc: trf7970a: Prevent repeated polling from crashing the kernel

Mark - I will split this off soon. In the meantime - here is some more info about how we use it. We do use NFC structures.I did find an interesting clue in that there are certain bottles that cause neard to segfault, I'm not sure what is different about them. We write a string, like

[PATCH] ath10k: Remove passing unused argument for ath10k_mac_tx

From: Mohammed Shafi Shajakhan 'ath10k_mac_tx' does not seems to use the per station table entry pointer 'sta' (struct ieee80211_sta), hence remove passing this unused argument Signed-off-by: Mohammed Shafi Shajakhan ---

Intel Wireless 7260 failed to work

Hello, Looks like latest Linux master (4.10-rc1, 7ce7d89f) cannot work well with my wireless card, which is: Intel Corporation Wireless 7260 (rev bb) Boot message shows that no suitable firmware found: # journalctl -kp3 Dec 27 16:38:00 kernel: Error parsing PCC subspaces from PCCT