CHROMIUM: iwl7000: don't treat EAPOLs like mgmt frames wrt rate

When the initial rate is _not_ chosen by RSSI conditions, the original
patch causes EAPOL frames to be sent with bad rates. This in turn
hinders connections to some APs.
The issue is most likely with using rates that are too low in p2p/11a
scenarios. Revert to the old behaviour until further debugging is done.
This make the behavior the same as before the RSSI-conditions patch.

Additionally, this fixes a warning that was hit in the bug, but doesn't
address the other issues in that bug.

BUG=chrome-os-partner:34666
TEST=run tests to reproduce the warning and see it's gone

Change-Id: I26d0c141e66a64dc176e172ad665362b08cc1037
Signed-off-by: Arik Nemtsov <arikx.nemtsov@intel.com>
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Reviewed-on: https://chromium-review.googlesource.com/236542
Reviewed-by: Paul Stewart <pstew@chromium.org>
CHROMIUM: iwl7000: small Core7 updates

This addresses a few issues, among them
 * an issue with 7265 device support,
 * a potential NULL-dereference in the debug/trace code
 * BT coexistence priorities
 * channel switch announcement going to the wrong chandef

BUG=N/A
TEST=autotest run

Change-Id: Ib38153d5349944ad83af1e8ecb745a9b2477cab7
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Reviewed-on: https://chromium-review.googlesource.com/236543
Reviewed-by: Paul Stewart <pstew@chromium.org>
Merge branch 'chromeos-3.8' of https://chromium.googlesource.com/chromiumos/third_party/kernel into chromeos-3.8