All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Krupp <michaelkrupp@gmx.net>
To: Ganesh GR <ganeshgr6@gmail.com>
Cc: ath10k@lists.infradead.org
Subject: Re: QCA6174 bringup
Date: Tue, 27 Oct 2015 12:53:19 +0100	[thread overview]
Message-ID: <562F65AF.8020905@gmx.net> (raw)
In-Reply-To: <1445926088032-08658f66-eef54963-c02dda7f@gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1072 bytes --]

Hello Ganesh,


I downloaded the official Windows 10 driver from acer.com and extracted the
setup file using InstallShield [1] Cab Viewer [2]. The 30-day trial version
is sufficient to do this.

Inside the "main" setup file, there was another setup.exe for the atheros
driver itself. I extracted it using UniExtract [3].

The inner setup file contained a couple of eeprom_* files inside the "drivers"
directory. I then copied the one matching my device to "board.bin".

In my case: /lib/firmware/ath10k/QCA6174/hw3.0/board.bin


Michael

[1] http://learn.flexerasoftware.com/IS-EVAL-InstallShield-Professional-DE
[2] http://helpnet.installshield.com/installshield22helplib/helplibrary/IsCabView.htm
[3] http://legroom.net/software/uniextract

On 10/27/2015 07:07 AM, Ganesh GR wrote:
> Hi Michael,
> 
> I am very excited to know how did you you extract board binary from windows driver, do you have windows driver source ?.
> 
> Regards
> Ganesh
> 
> Sent using CloudMagic <https://cloudmagic.com/k/d/mailapp?ct=pi&cv=6.0.64&pv=7.1.2>
> 


[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

[-- Attachment #2: Type: text/plain, Size: 146 bytes --]

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

           reply	other threads:[~2015-10-27 11:53 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <1445926088032-08658f66-eef54963-c02dda7f@gmail.com>]

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=562F65AF.8020905@gmx.net \
    --to=michaelkrupp@gmx.net \
    --cc=ath10k@lists.infradead.org \
    --cc=ganeshgr6@gmail.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 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.