Bug 1368159

Summary: [DELL 7.3 FEAT]update QCA6174/hw3.0/board-2.bin file to support Dell ath10k devices
Product: Red Hat Enterprise Linux 7 Reporter: Stanislaw Gruszka <sgruszka>
Component: linux-firmwareAssignee: Rafael Aquini <aquini>
Status: CLOSED ERRATA QA Contact: Ken Benoit <kbenoit>
Severity: high Docs Contact:
Priority: unspecified    
Version: 7.3CC: aquini, kasmith, kbenoit, perry_yuan, yijun_shen
Target Milestone: rcKeywords: FutureFeature
Target Release: 7.3   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: linux-firmware-20160830-49.git7534e19.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-11-04 03:37:17 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1171868, 1258937, 1298484    

Description Stanislaw Gruszka 2016-08-18 14:38:52 UTC
Description of problem:

Add Dell specific ids/board/eeprom data (all included in board-2.bin file) in order to support Dell ath10k devices (bug 1298484). This data is not yet in upstream linux-firmware tree, for now it was posted only to kvalo/ath10k-firmware:

https://github.com/kvalo/ath10k-firmware/commit/7c0411643b195b246d3871f409f9219f528b39c1

Comment 2 Rafael Aquini 2016-08-19 20:00:27 UTC
(In reply to Stanislaw Gruszka from comment #0)
> Description of problem:
> 
> Add Dell specific ids/board/eeprom data (all included in board-2.bin file)
> in order to support Dell ath10k devices (bug 1298484). This data is not yet
> in upstream linux-firmware tree, for now it was posted only to
> kvalo/ath10k-firmware:
> 
> https://github.com/kvalo/ath10k-firmware/commit/
> 7c0411643b195b246d3871f409f9219f528b39c1

If the blob is not committed to linux-firwmare upstream, we'll not take it. Setting Devel NACK, for now.

Comment 3 yijun_shen 2016-08-22 03:19:07 UTC
(In reply to Rafael Aquini from comment #2)
> (In reply to Stanislaw Gruszka from comment #0)
> > Description of problem:
> > 
> > Add Dell specific ids/board/eeprom data (all included in board-2.bin file)
> > in order to support Dell ath10k devices (bug 1298484). This data is not yet
> > in upstream linux-firmware tree, for now it was posted only to
> > kvalo/ath10k-firmware:
> > 
> > https://github.com/kvalo/ath10k-firmware/commit/
> > 7c0411643b195b246d3871f409f9219f528b39c1
> 
> If the blob is not committed to linux-firwmare upstream, we'll not take it.
> Setting Devel NACK, for now.


 We need this FW be merged into RHEL 7.3, we need know how to accelerate the process of "committed to linux-firwmare upstream"?
Is it owned by QCA or by community?

Comment 4 Stanislaw Gruszka 2016-08-22 08:48:18 UTC
(In reply to yijun_shen from comment #3)
 >  We need this FW be merged into RHEL 7.3, we need know how to accelerate the
> process of "committed to linux-firwmare upstream"?
> Is it owned by QCA or by community?

It's up to Kalle Valo from Qualcomm, I asked him already when he plans to push it upstream...

Comment 5 Stanislaw Gruszka 2016-08-24 06:38:04 UTC
Patch was posted upstream:
http://marc.info/?l=linux-wireless&m=147197824810492

Comment 6 yijun_shen 2016-08-24 07:28:28 UTC
(In reply to Stanislaw Gruszka from comment #5)
> Patch was posted upstream:
> http://marc.info/?l=linux-wireless&m=147197824810492

Is there any other block that the FW could be merged into snapshot 1 image?

Comment 7 Stanislaw Gruszka 2016-08-25 09:37:45 UTC
... and it was applied to linux-firmware git:

https://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git/commit/?id=7534e191256629a20c02e04d5f6d0439c48de80a

Comment 10 Ken Benoit 2016-08-31 16:06:36 UTC
Installed RHEL-7.3-20160830.n.0 on a system and verified that /lib/firmware/ath10k/QCA6174/hw2.1/board-2.bin and /lib/firmware/ath10k/QCA6174/hw3.0/board-2.bin exist and appear to be the proper file sizes from the patch. Marking as verified.

Comment 12 errata-xmlrpc 2016-11-04 03:37:17 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHEA-2016-2317.html