From: Kalle Valo <kvalo@qca.qualcomm.com>
To: "Shu, Nick" <Nick.Shu@spirent.com>
Cc: "ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: ath10k driver and firmware upgrade
Date: Thu, 10 Apr 2014 07:34:36 +0300 [thread overview]
Message-ID: <87a9btiyzn.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <153F35912E69C446A72CF7D6417EBADE7CF57F@SPCCOREXCMBX01.AD.SPIRENTCOM.COM> (Nick Shu's message of "Wed, 9 Apr 2014 21:18:35 +0000")
Hi Nick,
"Shu, Nick" <Nick.Shu@spirent.com> writes:
> I have a question about upgrade the diver and firmware for my wifi ac
> pcie card. I read through the docs in your /ath10k website and did the
> driver and firmware update. After that, here is what I read back from
> system:
>
> root@coast198:/home/spirent# ethtool -i wlan0
> driver: ath10k_pci
> version: 3.11.0-12-generic
> firmware-version: 999.999.0.636
> bus-info: 0000:03:00.0
> supports-statistics: yes
> supports-test: no
> supports-eeprom-access: no
> supports-register-dump: no
> supports-priv-flags: no
>
> So, I can see the firmware has been updated (I used
> firmware-2.bin_999.999.0.636 for STA, right?).
Like Ben said, if you still see 00:03:07:12:34:56 you should use
firmware version 10.1.467.2-1.
> But how can I find out have drivers been changed?
I added some tips to the wiki:
----------------------------------------------------------------------
To check that you are really using ath10k from backports make sure that
compat module is loaded and ath10k_pci module uses it:
$ lsmod | grep compat
compat 36104 6 iwldvm,iwlwifi,ath10k_pci,ath10k_core,mac80211,cfg80211
To check version of backports project:
$ dmesg | grep backport
[ 23.210662] Loading modules backported from Linux version next-20140221-0-gfaa2e6f
[ 23.210665] Backport generated by backports.git
backports-20140221-0-g8e94650
----------------------------------------------------------------------
http://wireless.kernel.org/en/users/Drivers/ath10k/backports
> I did following to change the driver:
> 1. Download the tarball from "backports-3.13.2-1" to my PC.
> 2. FTP it to my Linux box (test server running on Ubuntu 13.10 server).
> 3. Unpack it to my working directory.
> 4. Run "make defconfig-ath10k"
> "make"
> "make install".
> 5. But auto install failed because of some initramfs issue (no key? from error message), so I manually "rmmod" all drivers ( ath10k_pci.ko, ath10k_core.ko, mac80211.ko, ath.ko, cfg80211.ko, compat.ko) and then "Insmod" all drivers back.
> 6. Run "update-initramfs -u" and reboot.
>
> Did I do everything correct?
The initramfs issues look odd, I haven't seen those before. But
otherwise this looks good.
> I used "dhcpcd wlan0" to get a valid IP address from a Netgear wifiac
> ac access point, but from access point manager, the MAC for my card is
> still "00:03:07:12:34:56". From your last email, you said this default
> MAC was caused by wrong driver and firmware, so why it's still there
> after I changed driver and firmware? Do I miss something?
The problem is that firmware 999.999.0.636 doesn't support all hw
versions, that's why you need to use firmware from 10.1 branch.
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2014-04-10 4:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-09 21:18 ath10k driver and firmware upgrade Shu, Nick
2014-04-10 1:41 ` Ben Greear
2014-04-10 4:34 ` Kalle Valo [this message]
2014-04-10 14:09 ` Shu, Nick
[not found] <mailman.297.1397087917.1064.ath10k@lists.infradead.org>
2014-04-10 1:10 ` wangdc
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=87a9btiyzn.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=Nick.Shu@spirent.com \
--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