ATH10K Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "B R Manjula" <brm@cdot.in>
To: ath10k@lists.infradead.org
Subject: Fw: ath10k drivers on t1024 freescale board
Date: Tue, 12 Jan 2016 13:26:21 +0530	[thread overview]
Message-ID: <20160112075557.M17068@cdot.in> (raw)
In-Reply-To: <20160112065332.M45517@cdot.in>

kernel being used is 3.12
---------- Forwarded Message -----------
From: "B R Manjula" <brm@cdot.in>
To: ath10k@lists.infradead.org 
Sent: Tue, 12 Jan 2016 12:35:31 +0530
Subject: ath10k drivers on t1024 freescale board

Hello ,

We are using kernel 3.11 on FREESCALE reference board T1024RDB-64bit board trying to 
bringup ath10k drivers we are using WLE-900VX-7AA (11ac pcie mini card) we downloaded 
the 
firmware from the following site:
https://github.com/kvalo/ath10k-firmware/blob/master/QCA988X/main/firmware-
2.bin_999.999.0.636
replaced as firmware.bin in the directory /lib/firmware/ath10k/QCA988X/hw2.0

board.bin is downloaded from 
https://github.com/kvalo/ath10k-firmware/blob/master/QCA988X/board.bin

and otp.bin was not found we just placed some file in the name as otp.bin

we are getting the following issue:

ath10k_pci 0000:01:00.0: BAR 0: assigned [mem 0xc00000000-0xc001fffff 64bit] 
ath10k: MSI-X didn't succeed (1), trying MSI 
ath10k: MSI interrupt handling 
ath10k: Hardware name qca988x hw2.0 version 0x4100016c 
ath10k: early firmware event indicated 
ath10k: unable to write to the device 
ath10k: could not write otp (-110) 
ath10k: could not init core (-110) 
ath10k: could not probe fw (-110) 
ath10k: could not register driver core (-110) 
ath10k_pci: probe of 0000:01:00.0 failed with error -110

what could be the reason.
please reply as early as possible we are struck..

regards,
manjula

Disclaimer:
----------
This email and any files transmitted with it are confidential and intended solely for 
the use of the individual or entity to whom they are addressed.  If you are not the 
intended recipient you are notified that disclosing, copying, distributing or taking 
any action in reliance on the contents of this information is strictly prohibited. The 
sender does not accept liability for any errors or omissions in the contents of this 
message, which arise as a result of e-mail t
------- End of Forwarded Message -------


Disclaimer:
----------
This email and any files transmitted with it are confidential and intended solely for 
the use of the individual or entity to whom they are addressed.  If you are not the 
intended recipient you are notified that disclosing, copying, distributing or taking 
any action in reliance on the contents of this information is strictly prohibited. The 
sender does not accept liability for any errors or omissions in the contents of this 
message, which arise as a result of e-mail t


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

  reply	other threads:[~2016-01-12  7:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-12  7:05 ath10k drivers on t1024 freescale board B R Manjula
2016-01-12  7:56 ` B R Manjula [this message]
2016-01-12  8:04 ` Michal Kazior
2016-01-12  8:09   ` B R Manjula
2016-01-12  8:17   ` B R Manjula
2016-01-12 12:02     ` Michal Kazior
2016-01-12 16:56       ` B R Manjula
2016-01-12 11:29   ` B R Manjula
2016-01-12 12:06     ` Michal Kazior
2016-01-12 12:04   ` B R Manjula

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160112075557.M17068@cdot.in \
    --to=brm@cdot.in \
    --cc=ath10k@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox