From: Tobias Predel <tobias.predel@gmail.com>
To: "Hsu, Ryan" <ryanhsu@qca.qualcomm.com>
Cc: Adrian Chadd <adrian@freebsd.org>,
"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>,
vagner_ <vagnerrener@gmail.com>
Subject: Re: ath10k and QCA3977 - random transfer rate losses
Date: Sun, 21 Feb 2016 15:44:19 +0100 [thread overview]
Message-ID: <20160221144419.GA9138@localhost.fritz.box> (raw)
In-Reply-To: <a65854576afe4e5c84ec772f7202f709@NALASEXR01G.na.qualcomm.com>
Hello again,
one last word about the the board files:
I extracted the board files from an AsusTek Windows Driver installer
that included the Qualcomm driver files for diverse variants of QCA9377
built in Samsung, Asus (Askey), Acer, Lenovo notebooks.
An archive with all these files can be found at the comment 10 of my bug report
<https://bugzilla.kernel.org/show_bug.cgi?id=112451#c10>
including board files (eeprom_*.bin) for NFA425, NFA435 (A), NFA455.
If some people experience trouble, those might look at the netathr10x.inf
to find out which eeprom board file is needed or try out by installing
it to /lib/firmware/ath10k/QCA9377/hw1.0/board.bin.
Those board files are using api 1 and must be named board.bin.
firmware-5.bin is still to be pulled from kvalo's github repo.
Thank you to all for your support. I wish the best!
Tobias
On Fri, Feb 19, 2016 at 05:55:26PM +0000, Hsu, Ryan wrote:
> Glad that help!
>
> I've cc that file to Kalle, hope we can see that get merged soon.
>
> Ryan
>
> > -----Original Message-----
> > From: Tobias Predel [mailto:tobias.predel@gmail.com]
> > Sent: Friday, February 19, 2016 09:23 AM
> > To: Adrian Chadd
> > Cc: Hsu, Ryan; ath10k@lists.infradead.org; vagner_
> > Subject: Re: ath10k and QCA3977 - random transfer rate losses
> >
> > On Fri, Feb 19, 2016 at 08:07:49AM -0800, Adrian Chadd wrote:
> > > Ok, so it's a board file problem? this can be solved by telling kvalo@
> > > about it, right?
> > >
> > >
> > > -a
> >
> > Yes, they differ and the board-2.bin file isn't included neither in linux-
> > firmware nor in kvalo's repository.
> >
> > MD5 checksums:
> > 73cca12b9398f0cecaa3cfa35c8961b7 board-2.bin
> > 44349f6ae93cf9ceffb164f58d4fb124 board.bin
> >
> > I'll try to contact him and send the board file.
> >
> > Tobias
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2016-02-21 14:44 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-12 20:30 ath10k and QCA3977 - random transfer rate losses Tobias Predel
2016-02-13 12:06 ` vagner_
2016-02-14 15:46 ` Tobias Predel
2016-02-14 16:00 ` Adrian Chadd
2016-02-14 16:22 ` Tobias Predel
2016-02-14 16:35 ` Adrian Chadd
2016-02-14 19:54 ` Tobias Predel
2016-02-14 18:02 ` vagner_
2016-02-14 21:40 ` Tobias Predel
2016-02-19 7:10 ` Hsu, Ryan
2016-02-19 9:16 ` Tobias Predel
2016-02-19 16:07 ` Adrian Chadd
2016-02-19 17:23 ` Tobias Predel
2016-02-19 17:55 ` Hsu, Ryan
2016-02-21 14:44 ` Tobias Predel [this message]
2016-02-21 18:33 ` Adrian Chadd
2016-02-21 19:20 ` Tobias Predel
2016-02-21 19:25 ` Adrian Chadd
2016-02-21 21:54 ` Tobias Predel
2016-02-22 1:40 ` Adrian Chadd
2016-02-22 9:12 ` vagner_
2016-02-22 20:31 ` Tobias Predel
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=20160221144419.GA9138@localhost.fritz.box \
--to=tobias.predel@gmail.com \
--cc=adrian@freebsd.org \
--cc=ath10k@lists.infradead.org \
--cc=ryanhsu@qca.qualcomm.com \
--cc=vagnerrener@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox