All of lore.kernel.org
 help / color / mirror / Atom feed
From: wangdc <wangdc@dhc.com.cn>
To: 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 09:10:44 +0800	[thread overview]
Message-ID: <5345EF94.1010104@dhc.com.cn> (raw)
In-Reply-To: <mailman.297.1397087917.1064.ath10k@lists.infradead.org>


On 2014年04月10日 07:58, ath10k-request@lists.infradead.org wrote:
> Message: 4
> Date: Wed, 9 Apr 2014 21:18:35 +0000
> 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
> Message-ID:
>          <153F35912E69C446A72CF7D6417EBADE7CF57F@SPCCOREXCMBX01.AD.SPIRENTCOM.COM>
>
>
> 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?
>

May be you can get the mac address correctly using the following method.
http://lists.infradead.org/pipermail/ath10k/2014-March/001452.html

----

Rex



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

       reply	other threads:[~2014-04-10  1:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.297.1397087917.1064.ath10k@lists.infradead.org>
2014-04-10  1:10 ` wangdc [this message]
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
2014-04-10 14:09   ` Shu, Nick

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=5345EF94.1010104@dhc.com.cn \
    --to=wangdc@dhc.com.cn \
    --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 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.