New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 755852 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Closed: May 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Task



Sign in to add a comment

Add 4.14 kernel entries to autotest network_WlanDriver when kernel is ready

Project Member Reported by kirtika@google.com, Aug 16 2017

Issue description

RVG as 4.12 may not be announced and this is more of a To-Do for wifi team. 

See missing entries for 4.4 kernel in network_WlanDriver test that were corrected here - 
https://chromium-review.googlesource.com/#/c/chromiumos/third_party/autotest/+/599032/2/client/site_tests/network_WlanDriver/network_WlanDriver.py

For 4.12, we should proactively add them before the kernel hits CQ on ToT. 

 
Cc: kirtika@google.com maxbann...@gmail.com ecgh@chromium.org
Labels: -Restrict-View-Google
Summary: Add 4.14 kernel entries to autotest network_WlanDriver when kernel is ready (was: Add 4.12 kernel entries to autotest network_WlanDriver when kernel is ready)
4.14 is public. But we still don't know what driver we're using...

Related issue open here: https://issuetracker.google.com/67425872
Owner: briannorris@chromium.org
Status: Started (was: Untriaged)
I believe this is Fixed for Intel. I put up one more CL for ath10k:

https://chromium-review.googlesource.com/c/chromiumos/third_party/autotest/+/1049272
Project Member

Comment 3 by bugdroid1@chromium.org, May 9 2018

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/autotest/+/8b9812e3c13db2ec632765a59e05b42f89b68751

commit 8b9812e3c13db2ec632765a59e05b42f89b68751
Author: Brian Norris <briannorris@chromium.org>
Date: Wed May 09 00:44:34 2018

network_WlanDriver: update QCA6174A support list

1. We never brought up complete support for QCA6174A on 3.18, and no
   platforms are launching with it. Drop it.
2. Add ath10k entry (note: not ar10k) for 4.14, since we're using the
   native driver stack
3. Drop the "NFA344A" name and just merge it into the main QCA6174A
   label; we don't really need to differentiate these, AFAICT; it's not
   the first time that we'd have multiple IDs mapping to the same base
   chipset

BUG= chromium:755852 , b:67425872
TEST=network_WlanDriver on Scarlet still passes

Change-Id: Id09696569a48181ee1ead3c255b4ec68c0655338
Signed-off-by: Brian Norris <briannorris@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/1049272
Reviewed-by: Kirtika Ruchandani <kirtika@chromium.org>

[modify] https://crrev.com/8b9812e3c13db2ec632765a59e05b42f89b68751/client/common_lib/cros/network/interface.py
[modify] https://crrev.com/8b9812e3c13db2ec632765a59e05b42f89b68751/client/site_tests/network_WlanDriver/network_WlanDriver.py

Status: Fixed (was: Started)
Status: Verified (was: Fixed)

Sign in to add a comment