From: "Shu, Nick" <Nick.Shu@spirent.com>
To: "kvalo@qca.qualcomm.com" <kvalo@qca.qualcomm.com>
Cc: "ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: ath10k driver and firmware upgrade
Date: Wed, 9 Apr 2014 21:18:35 +0000 [thread overview]
Message-ID: <153F35912E69C446A72CF7D6417EBADE7CF57F@SPCCOREXCMBX01.AD.SPIRENTCOM.COM> (raw)
Hi, Kalle and all:
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?).
But how can I find out have drivers been changed?
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?
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?
Thank you!
Nick Shu
E-mail confidentiality.
--------------------------------
This e-mail contains confidential and / or privileged information belonging to Spirent Communications plc, its affiliates and / or subsidiaries. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution and / or the taking of any action based upon reliance on the contents of this transmission is strictly forbidden. If you have received this message in error please notify the sender by return e-mail and delete it from your system.
Spirent Communications plc
Northwood Park, Gatwick Road, Crawley, West Sussex, RH10 9XN, United Kingdom.
Tel No. +44 (0) 1293 767676
Fax No. +44 (0) 1293 767677
Registered in England Number 470893
Registered at Northwood Park, Gatwick Road, Crawley, West Sussex, RH10 9XN, United Kingdom.
Or if within the US,
Spirent Communications,
26750 Agoura Road, Calabasas, CA, 91302, USA.
Tel No. 1-818-676- 2300
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next reply other threads:[~2014-04-09 21:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-09 21:18 Shu, Nick [this message]
2014-04-10 1:41 ` ath10k driver and firmware upgrade Ben Greear
2014-04-10 4:34 ` Kalle Valo
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=153F35912E69C446A72CF7D6417EBADE7CF57F@SPCCOREXCMBX01.AD.SPIRENTCOM.COM \
--to=nick.shu@spirent.com \
--cc=ath10k@lists.infradead.org \
--cc=kvalo@qca.qualcomm.com \
/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