All of lore.kernel.org
 help / color / mirror / Atom feed
* First QCA6174 firmware release
@ 2015-02-08 13:12 Austin Hendrix
  2015-02-08 13:17 ` Sebastian Gottschall
  2015-02-09 10:14 ` Austin Hendrix
  0 siblings, 2 replies; 13+ messages in thread
From: Austin Hendrix @ 2015-02-08 13:12 UTC (permalink / raw)
  To: ath10k

I have the same issue as Joris; my QCA6174 appears to be a hw2.1 
version. lspci -vvv returns similar results.

The wireless card is a " Killer N1525 Combo (2x2 ac)", in an MSI GS60 
Ghost Pro 4K laptop; purchased in January of 2015.

Similar to Joris, I've also found what appears to be firmware as part of 
the existing Windows installation, but it looks like it's missing the 
header information and magic bits that will allow it to load.

Does anyone have any pointers on how I might go about confirming that 
this is the correct firmware; preparing it for the ath10k driver with 
the appropriate header, and preparing the matching board.bin file?

Thanks,
-Austin

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

^ permalink raw reply	[flat|nested] 13+ messages in thread

* Re: First QCA6174 firmware release
  2015-02-08 13:12 First QCA6174 firmware release Austin Hendrix
@ 2015-02-08 13:17 ` Sebastian Gottschall
  2015-02-12  6:04   ` Austin Hendrix
  2015-02-09 10:14 ` Austin Hendrix
  1 sibling, 1 reply; 13+ messages in thread
From: Sebastian Gottschall @ 2015-02-08 13:17 UTC (permalink / raw)
  To: ath10k

Am 08.02.2015 um 14:12 schrieb Austin Hendrix:
> I have the same issue as Joris; my QCA6174 appears to be a hw2.1 
> version. lspci -vvv returns similar results.
>
> The wireless card is a " Killer N1525 Combo (2x2 ac)", in an MSI GS60 
> Ghost Pro 4K laptop; purchased in January of 2015.
>
> Similar to Joris, I've also found what appears to be firmware as part 
> of the existing Windows installation, but it looks like it's missing 
> the header information and magic bits that will allow it to load.
>
> Does anyone have any pointers on how I might go about confirming that 
> this is the correct firmware; preparing it for the ath10k driver with 
> the appropriate header, and preparing the matching board.bin file?
>
the format is very simple. you can write such a tool in about 30 minutes 
if you are a skilled programmer. i already did it. just need to find it 
on my hdd
> Thanks,
> -Austin
>
> _______________________________________________
> ath10k mailing list
> ath10k@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/ath10k
>


_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

^ permalink raw reply	[flat|nested] 13+ messages in thread

* Re: First QCA6174 firmware release
  2015-02-08 13:12 First QCA6174 firmware release Austin Hendrix
  2015-02-08 13:17 ` Sebastian Gottschall
@ 2015-02-09 10:14 ` Austin Hendrix
  1 sibling, 0 replies; 13+ messages in thread
From: Austin Hendrix @ 2015-02-09 10:14 UTC (permalink / raw)
  To: ath10k

I have the same issue as Joris; my QCA6174 appears to be a hw2.1
version. lspci -vvv returns similar results.

The wireless card is a " Killer N1525 Combo (2x2 ac)", in an MSI GS60
Ghost Pro 4K laptop; purchased in January of 2015.

Similar to Joris, I've also found what appears to be firmware as part of
the existing Windows installation, but it looks like it's missing the
header information and magic bits that will allow it to load.

Does anyone have any pointers on how I might go about confirming that
this is the correct firmware; preparing it for the ath10k driver with
the appropriate header, and preparing the matching board.bin file?

Thanks,
-Austin




_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

^ permalink raw reply	[flat|nested] 13+ messages in thread

* Re: First QCA6174 firmware release
  2015-02-08 13:17 ` Sebastian Gottschall
@ 2015-02-12  6:04   ` Austin Hendrix
  2015-02-12  6:31     ` Michal Kazior
  0 siblings, 1 reply; 13+ messages in thread
From: Austin Hendrix @ 2015-02-12  6:04 UTC (permalink / raw)
  To: ath10k

I consider myself a fairly skilled programmer; if the format is 
documented somewhere, I have no doubt that I can write a tool to put the 
firmware into the proper format. Does anyone know where the firmware 
format is documented, or do I have to go read the source for the driver 
to figure out the firmware format?

The bigger question is, how can I confirm that I'm wrapping the correct 
firmware?

I found a qca61x420.bin file (probably firmware; definitely compiled 
code) in /Windows/System32/drivers/qca61x420.bin , but the ath10k driver 
doesn't recognize it as firmware.

Thanks,
-Austin

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

^ permalink raw reply	[flat|nested] 13+ messages in thread

* Re: First QCA6174 firmware release
  2015-02-12  6:04   ` Austin Hendrix
@ 2015-02-12  6:31     ` Michal Kazior
  2015-02-13  7:25       ` Austin Hendrix
  0 siblings, 1 reply; 13+ messages in thread
From: Michal Kazior @ 2015-02-12  6:31 UTC (permalink / raw)
  To: Austin Hendrix; +Cc: ath10k

On 12 February 2015 at 07:04, Austin Hendrix <namniart@gmail.com> wrote:
> I consider myself a fairly skilled programmer; if the format is documented
> somewhere, I have no doubt that I can write a tool to put the firmware into
> the proper format. Does anyone know where the firmware format is documented,
> or do I have to go read the source for the driver to figure out the firmware
> format?

Take a look at ath10k_core_fetch_firmware_api_n(). You can derive an
encoder logic from this easily.


> The bigger question is, how can I confirm that I'm wrapping the correct
> firmware?

If ath10k parses it later and boots then it's correct? :-)


> I found a qca61x420.bin file (probably firmware; definitely compiled code)
> in /Windows/System32/drivers/qca61x420.bin , but the ath10k driver doesn't
> recognize it as firmware.

The blob you found is the raw binary that is pushed to the device.
ath10k expects to find it in a wrapped "FW API" which also contains an
OTP program. You also need to make sure to setup correct
fw_features/op_version (you can disassemble the hw3.0 wrapper blob).


Michał

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

^ permalink raw reply	[flat|nested] 13+ messages in thread

* Re: First QCA6174 firmware release
  2015-02-12  6:31     ` Michal Kazior
@ 2015-02-13  7:25       ` Austin Hendrix
  0 siblings, 0 replies; 13+ messages in thread
From: Austin Hendrix @ 2015-02-13  7:25 UTC (permalink / raw)
  To: ath10k

On 02/11/2015 10:31 PM, Michal Kazior wrote:
> On 12 February 2015 at 07:04, Austin Hendrix <namniart@gmail.com> wrote:
>> I consider myself a fairly skilled programmer; if the format is documented
>> somewhere, I have no doubt that I can write a tool to put the firmware into
>> the proper format. Does anyone know where the firmware format is documented,
>> or do I have to go read the source for the driver to figure out the firmware
>> format?
> Take a look at ath10k_core_fetch_firmware_api_n(). You can derive an
> encoder logic from this easily.
>
>
>> The bigger question is, how can I confirm that I'm wrapping the correct
>> firmware?
> If ath10k parses it later and boots then it's correct? :-)
>
>
>> I found a qca61x420.bin file (probably firmware; definitely compiled code)
>> in /Windows/System32/drivers/qca61x420.bin , but the ath10k driver doesn't
>> recognize it as firmware.
> The blob you found is the raw binary that is pushed to the device.
> ath10k expects to find it in a wrapped "FW API" which also contains an
> OTP program. You also need to make sure to setup correct
> fw_features/op_version (you can disassemble the hw3.0 wrapper blob).
>
>
> Michał
>
> _______________________________________________
> ath10k mailing list
> ath10k@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/ath10k

Thanks! I can work with that.

The FW API data structure is pretty simple - I can reproduce it.

Looking at the firmware blob that I have, and comparing it to the 
existing firmware-4 image suggests that it contains several different 
firmware images. I'm going to spend some time trying to chop it up and 
figure out how it's laid out, and then try to re-pack it appropriately 
for linux.

-Austin


_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

^ permalink raw reply	[flat|nested] 13+ messages in thread

* Re: First QCA6174 firmware release
  2015-04-25 18:22 ` Oscar Rydberg
@ 2015-04-27  5:34   ` Michal Kazior
  0 siblings, 0 replies; 13+ messages in thread
From: Michal Kazior @ 2015-04-27  5:34 UTC (permalink / raw)
  To: Oscar Rydberg; +Cc: ath10k

On 25 April 2015 at 20:22, Oscar Rydberg <oscarrydberg@gmail.com> wrote:
> Olaf Dreyer <olaf <at> dreyero.de> writes:
>
>>
>> I have a new Acer Aspire VN7-591 Laptop with a Qualcom Atheros
> QCNF344
>> wireless chip, which is shown by lspci as:
>>
>> Qualcomm Atheros Device 003e (rev 20)
>> Subsystem: Foxconn International, Inc. Device e08e
>>
>> I have installed the linux-next kernel from today 8:00 UTC.
>> I was able to load the ath10k_pci driver, but the driver complains
> about
>> missing firmware.
>> I installed a firmware from here: https://github.com/kvalo/ath10k-
> firmware
>> under /lib/firmware/ath10k/QCA6174/hw2.1/
>> But also the card is not working.
>>
>> The output from dmesg is:
>> [ 9360.538767] ath10k_pci 0000:07:00.0: pci irq msi interrupts 1
>> irq_mode 0 reset_mode 0
>> [ 9360.788588] ath10k_pci 0000:07:00.0: Direct firmware load for
>> ath10k/cal-pci-0000:07:00.0.bin failed with error -2
>> [ 9362.729118] ath10k_pci 0000:07:00.0: unable to write to the
> device
>> [ 9362.729120] ath10k_pci 0000:07:00.0: failed to download normal
>> firmware: -110
>> [ 9362.729121] ath10k_pci 0000:07:00.0: could not init core (-110)
>> [ 9362.729156] ath10k_pci 0000:07:00.0: could not probe fw (-110)
>>
>> I would like to know, as Austin Hendrix wrote it at 8 Feb 14:12
> 2015
>> too, where can I find the firmware on the
>> internet / my Windows7 partition and how can I prepare the needed
> files.
>>
>> Many thanks,
>>
>> Olaf
>>
>
> Hi did you advance anything on this?
>
> Trying to run a QCA6164 card myself on a Lenovo 3-14 laptop.
> Sems I've gotten as far as you.
> Prepared Ath10k hw2.1 board.bin and firmware-4.bin for hw2.1 using
> windows binary driver. (And assemble.py, disassemble.py tools linked
> elsewhere)
>
> Board.bin seems to load and execute fine. But after that when
> loading firmware-4.bin, it ends up with Unable to write to the
> device.
>
> I see it starts sending firmware-4.bin and first 256 bytes ce_send
> fine.
> 2nd ce_send 256 bytes seem to also ce_send fine, however after that
> bmi_wait times out. (-110)

You're most likely trying to push something that isn't an actual
firmware blob to the device. You might be interested in the other
thread: http://lists.infradead.org/pipermail/ath10k/2015-April/005072.html


Michał

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

^ permalink raw reply	[flat|nested] 13+ messages in thread

* Re: First QCA6174 firmware release
  2015-02-11 13:44 Olaf Dreyer
@ 2015-04-25 18:22 ` Oscar Rydberg
  2015-04-27  5:34   ` Michal Kazior
  0 siblings, 1 reply; 13+ messages in thread
From: Oscar Rydberg @ 2015-04-25 18:22 UTC (permalink / raw)
  To: ath10k

Olaf Dreyer <olaf <at> dreyero.de> writes:

> 
> I have a new Acer Aspire VN7-591 Laptop with a Qualcom Atheros 
QCNF344
> wireless chip, which is shown by lspci as:
> 
> Qualcomm Atheros Device 003e (rev 20)
> Subsystem: Foxconn International, Inc. Device e08e
> 
> I have installed the linux-next kernel from today 8:00 UTC.
> I was able to load the ath10k_pci driver, but the driver complains 
about
> missing firmware.
> I installed a firmware from here: https://github.com/kvalo/ath10k-
firmware
> under /lib/firmware/ath10k/QCA6174/hw2.1/
> But also the card is not working.
> 
> The output from dmesg is:
> [ 9360.538767] ath10k_pci 0000:07:00.0: pci irq msi interrupts 1
> irq_mode 0 reset_mode 0
> [ 9360.788588] ath10k_pci 0000:07:00.0: Direct firmware load for
> ath10k/cal-pci-0000:07:00.0.bin failed with error -2
> [ 9362.729118] ath10k_pci 0000:07:00.0: unable to write to the 
device
> [ 9362.729120] ath10k_pci 0000:07:00.0: failed to download normal
> firmware: -110
> [ 9362.729121] ath10k_pci 0000:07:00.0: could not init core (-110)
> [ 9362.729156] ath10k_pci 0000:07:00.0: could not probe fw (-110)
> 
> I would like to know, as Austin Hendrix wrote it at 8 Feb 14:12 
2015
> too, where can I find the firmware on the
> internet / my Windows7 partition and how can I prepare the needed 
files.
> 
> Many thanks,
> 
> Olaf
> 

Hi did you advance anything on this?

Trying to run a QCA6164 card myself on a Lenovo 3-14 laptop.
Sems I've gotten as far as you. 
Prepared Ath10k hw2.1 board.bin and firmware-4.bin for hw2.1 using 
windows binary driver. (And assemble.py, disassemble.py tools linked 
elsewhere)

Board.bin seems to load and execute fine. But after that when 
loading firmware-4.bin, it ends up with Unable to write to the 
device.

I see it starts sending firmware-4.bin and first 256 bytes ce_send 
fine.
2nd ce_send 256 bytes seem to also ce_send fine, however after that 
bmi_wait times out. (-110)




_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

^ permalink raw reply	[flat|nested] 13+ messages in thread

* First QCA6174 firmware release
@ 2015-02-11 13:44 Olaf Dreyer
  2015-04-25 18:22 ` Oscar Rydberg
  0 siblings, 1 reply; 13+ messages in thread
From: Olaf Dreyer @ 2015-02-11 13:44 UTC (permalink / raw)
  To: ath10k

I have a new Acer Aspire VN7-591 Laptop with a Qualcom Atheros QCNF344
wireless chip, which is shown by lspci as:

Qualcomm Atheros Device 003e (rev 20)
Subsystem: Foxconn International, Inc. Device e08e

I have installed the linux-next kernel from today 8:00 UTC.
I was able to load the ath10k_pci driver, but the driver complains about
missing firmware.
I installed a firmware from here: https://github.com/kvalo/ath10k-firmware
under /lib/firmware/ath10k/QCA6174/hw2.1/
But also the card is not working.
 
The output from dmesg is:
[ 9360.538767] ath10k_pci 0000:07:00.0: pci irq msi interrupts 1
irq_mode 0 reset_mode 0
[ 9360.788588] ath10k_pci 0000:07:00.0: Direct firmware load for
ath10k/cal-pci-0000:07:00.0.bin failed with error -2
[ 9362.729118] ath10k_pci 0000:07:00.0: unable to write to the device
[ 9362.729120] ath10k_pci 0000:07:00.0: failed to download normal
firmware: -110
[ 9362.729121] ath10k_pci 0000:07:00.0: could not init core (-110)
[ 9362.729156] ath10k_pci 0000:07:00.0: could not probe fw (-110)

I would like to know, as Austin Hendrix wrote it at 8 Feb 14:12 2015
too, where can I find the firmware on the
internet / my Windows7 partition and how can I prepare the needed files.

Many thanks,

Olaf


_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

^ permalink raw reply	[flat|nested] 13+ messages in thread

* Re: First QCA6174 firmware release
  2015-02-04 12:08   ` Kalle Valo
@ 2015-02-04 18:13     ` Joris Guisson
  0 siblings, 0 replies; 13+ messages in thread
From: Joris Guisson @ 2015-02-04 18:13 UTC (permalink / raw)
  To: Kalle Valo; +Cc: ath10k

This is what lspci -vvv says:

04:00.0 Network controller: Qualcomm Atheros Device 003e (rev 20)
        Subsystem: Bigfoot Networks, Inc. Device 1525
        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B- DisINTx+
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0, Cache Line Size: 64 bytes
        Interrupt: pin A routed to IRQ 31
        Region 0: Memory at f7200000 (64-bit, non-prefetchable) [size=2M]
        Capabilities: [40] Power Management version 3
                Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA
PME(D0+,D1-,D2-,D3hot+,D3cold+)
                Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
        Capabilities: [50] MSI: Enable+ Count=8/8 Maskable+ 64bit-
                Address: fee00518  Data: 0000
                Masking: 00000000  Pending: 00000000
        Capabilities: [70] Express (v2) Endpoint, MSI 00
                DevCap: MaxPayload 256 bytes, PhantFunc 0, Latency L0s
unlimited, L1 <64us
                        ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
                DevCtl: Report errors: Correctable- Non-Fatal- Fatal-
Unsupported-
                        RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
                        MaxPayload 128 bytes, MaxReadReq 512 bytes
                DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq-
AuxPwr+ TransPend-
                LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1,
Exit Latency L0s <4us, L1 <64us
                        ClockPM+ Surprise- LLActRep- BwNot-
                LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk-
                        ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
                LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train-
SlotClk+ DLActive- BWMgmt- ABWMgmt-
                DevCap2: Completion Timeout: Not Supported,
TimeoutDis+, LTR+, OBFF Via message
                DevCtl2: Completion Timeout: 50us to 50ms,
TimeoutDis-, LTR+, OBFF Disabled
                LnkCtl2: Target Link Speed: 2.5GT/s, EnterCompliance- SpeedDis-
                         Transmit Margin: Normal Operating Range,
EnterModifiedCompliance- ComplianceSOS-
                         Compliance De-emphasis: -6dB
                LnkSta2: Current De-emphasis Level: -6dB,
EqualizationComplete-, EqualizationPhase1-
                         EqualizationPhase2-, EqualizationPhase3-,
LinkEqualizationRequest-
        Capabilities: [100 v2] Advanced Error Reporting
                UESta:  DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt-
UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
                UEMsk:  DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt-
UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
                UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt-
UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
                CESta:  RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr-
                CEMsk:  RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
                AERCap: First Error Pointer: 00, GenCap- CGenEn- ChkCap- ChkEn-
        Capabilities: [148 v1] Virtual Channel
                Caps:   LPEVC=0 RefClk=100ns PATEntryBits=1
                Arb:    Fixed- WRR32- WRR64- WRR128-
                Ctrl:   ArbSelect=Fixed
                Status: InProgress-
                VC0:    Caps:   PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
                        Arb:    Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256-
                        Ctrl:   Enable+ ID=0 ArbSelect=Fixed TC/VC=01
                        Status: NegoPending- InProgress-
        Capabilities: [168 v1] Device Serial Number 00-00-00-00-00-00-00-00
        Capabilities: [178 v1] Latency Tolerance Reporting
                Max snoop latency: 71680ns
                Max no snoop latency: 71680ns
        Capabilities: [180 v1] L1 PM Substates
                L1SubCap: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+
ASPM_L1.1+ L1_PM_Substates+
                          PortCommonModeRestoreTime=50us PortTPowerOnTime=10us
        Kernel driver in use: ath10k_pci


What other information do you need to know ?

Where are you actually getting these firmwares from ? Are these
firmwares just taken from windows drivers ?

 I did a quick find -name '*.bin' on my windows C partition, and I found these:

./Program Files/Qualcomm Atheros/Network
Manager/11AC/eeprom_ar6320_2p1_NFA344i.bin
./Program Files/Qualcomm Atheros/Network
Manager/11AC/eeprom_ar6320_2p1_NFA345i.bin
./Program Files/Qualcomm Atheros/Network
Manager/11AC/eeprom_ar6320_2p1_NFA354xp.bin
./Program Files/Qualcomm Atheros/Network
Manager/11AC/eeprom_ar6320_2p1_NFA355i.bin
./Program Files/Qualcomm Atheros/Network Manager/11AC/qca61x420.bin


Joris,

On Wed, Feb 4, 2015 at 1:08 PM, Kalle Valo <kvalo@qca.qualcomm.com> wrote:
> Joris Guisson <joris.guisson@gmail.com> writes:
>
>> Where is the QCA6174 v2.1 firmware ?
>
> I only have hw3.0 and no hw2.1. Can you give me more details what kind
> of device you are using?
>
> --
> Kalle Valo

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

^ permalink raw reply	[flat|nested] 13+ messages in thread

* Re: First QCA6174 firmware release
       [not found] ` <CAAmLN2Y8L_BZbZBCvUEw_i9OJoWvzaUT6H5UsyBymaozLubcOA@mail.gmail.com>
@ 2015-02-04 12:08   ` Kalle Valo
  2015-02-04 18:13     ` Joris Guisson
  0 siblings, 1 reply; 13+ messages in thread
From: Kalle Valo @ 2015-02-04 12:08 UTC (permalink / raw)
  To: Joris Guisson; +Cc: ath10k

Joris Guisson <joris.guisson@gmail.com> writes:

> Where is the QCA6174 v2.1 firmware ?

I only have hw3.0 and no hw2.1. Can you give me more details what kind
of device you are using?

-- 
Kalle Valo

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

^ permalink raw reply	[flat|nested] 13+ messages in thread

* Re: First QCA6174 firmware release
  2015-01-27 13:45 Kalle Valo
@ 2015-02-03 17:04 ` Joris Guisson
       [not found] ` <CAAmLN2Y8L_BZbZBCvUEw_i9OJoWvzaUT6H5UsyBymaozLubcOA@mail.gmail.com>
  1 sibling, 0 replies; 13+ messages in thread
From: Joris Guisson @ 2015-02-03 17:04 UTC (permalink / raw)
  To: Kalle Valo; +Cc: ath10k

Where is the QCA6174 v2.1 firmware ?

I'm getting these errors from the latest ath kernel:

[ 1660.748740] ath10k_pci 0000:04:00.0: Direct firmware load for
ath10k/cal-pci-0000:04:00.0.bin failed with error -2
[ 1660.748767] ath10k_pci 0000:04:00.0: Direct firmware load for
ath10k/QCA6174/hw2.1/firmware-4.bin failed with error -2
[ 1660.748770] ath10k_pci 0000:04:00.0: could not fetch firmware file
'ath10k/QCA6174/hw2.1/firmware-4.bin': -2
[ 1660.748777] ath10k_pci 0000:04:00.0: Direct firmware load for
ath10k/QCA6174/hw2.1/firmware-3.bin failed with error -2
[ 1660.748779] ath10k_pci 0000:04:00.0: could not fetch firmware file
'ath10k/QCA6174/hw2.1/firmware-3.bin': -2
[ 1660.748785] ath10k_pci 0000:04:00.0: Direct firmware load for
ath10k/QCA6174/hw2.1/firmware-2.bin failed with error -2
[ 1660.748787] ath10k_pci 0000:04:00.0: could not fetch firmware file
'ath10k/QCA6174/hw2.1/firmware-2.bin': -2
[ 1660.748793] ath10k_pci 0000:04:00.0: Direct firmware load for
ath10k/QCA6174/hw2.1/board.bin failed with error -2
[ 1660.748795] ath10k_pci 0000:04:00.0: could not fetch board data (-2)
[ 1660.748797] ath10k_pci 0000:04:00.0: could not fetch firmware files (-2)
[ 1660.748799] ath10k_pci 0000:04:00.0: could not probe fw (-2)

Seeing, that I don't have these firmware files, this is logical. So
where can I find them ?

Joris,

On Tue, Jan 27, 2015 at 2:45 PM, Kalle Valo <kvalo@qca.qualcomm.com> wrote:
> Hi,
>
> I pushed the first QCA6174 firmware release to ath10k-firmware.git:
>
> https://github.com/kvalo/ath10k-firmware/tree/master/ath10k/QCA6174/hw3.0
>
> --
> Kalle Valo
>
> _______________________________________________
> ath10k mailing list
> ath10k@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/ath10k

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

^ permalink raw reply	[flat|nested] 13+ messages in thread

* First QCA6174 firmware release
@ 2015-01-27 13:45 Kalle Valo
  2015-02-03 17:04 ` Joris Guisson
       [not found] ` <CAAmLN2Y8L_BZbZBCvUEw_i9OJoWvzaUT6H5UsyBymaozLubcOA@mail.gmail.com>
  0 siblings, 2 replies; 13+ messages in thread
From: Kalle Valo @ 2015-01-27 13:45 UTC (permalink / raw)
  To: ath10k

Hi,

I pushed the first QCA6174 firmware release to ath10k-firmware.git:

https://github.com/kvalo/ath10k-firmware/tree/master/ath10k/QCA6174/hw3.0

-- 
Kalle Valo

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

^ permalink raw reply	[flat|nested] 13+ messages in thread

end of thread, other threads:[~2015-04-27  5:34 UTC | newest]

Thread overview: 13+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-02-08 13:12 First QCA6174 firmware release Austin Hendrix
2015-02-08 13:17 ` Sebastian Gottschall
2015-02-12  6:04   ` Austin Hendrix
2015-02-12  6:31     ` Michal Kazior
2015-02-13  7:25       ` Austin Hendrix
2015-02-09 10:14 ` Austin Hendrix
  -- strict thread matches above, loose matches on Subject: below --
2015-02-11 13:44 Olaf Dreyer
2015-04-25 18:22 ` Oscar Rydberg
2015-04-27  5:34   ` Michal Kazior
2015-01-27 13:45 Kalle Valo
2015-02-03 17:04 ` Joris Guisson
     [not found] ` <CAAmLN2Y8L_BZbZBCvUEw_i9OJoWvzaUT6H5UsyBymaozLubcOA@mail.gmail.com>
2015-02-04 12:08   ` Kalle Valo
2015-02-04 18:13     ` Joris Guisson

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.