From: Alexandre Maloteaux <a.maloteaux@gmail.com>
To: ath10k@lists.infradead.org
Subject: Re: qca6164 support
Date: Wed, 5 Aug 2015 18:10:11 +0100 [thread overview]
Message-ID: <55C24373.20200@gmail.com> (raw)
In-Reply-To: <CALiJtcro6PzcFjJBt38UrZFwoM0BYU7x=Btw+k75Q1ryr2SU_Q@mail.gmail.com>
Hi Victor
Concerning the timeout issue; i faced it on Archlinux with kvalo kernel.
The issue was related to the kernel option
CONFIG_FW_LOADER_USER_HELPER_FALLBACK (Fallback user-helper invocation
for firmware loading). This option if activated will create a 1 minute
timeout on each firmware try as udev does not implemented this feature
anymore.
Best Regards
On 08/05/2015 04:32 PM, Victor van Poppelen wrote:
>> I think you should have called your firmwware firmware-4.bin and not
>> -5.bin. In fact in the top of the file I have it says ">
>> firmware-4.bin". File names matters as far as I understood. Feel free
>> to check archives of this list I saw somebody talking about this
>> argument not long ago.
> I admit I foolishly only changed the name to firmware-5.bin to prevent
> the minute-long timeout (can we do something about that?), which is
> probably the same reason why others were doing it. But in looking
> through the code, I can't find anywhere where the value of ar->fw_api
> actually affects driver behaviour. Could you point me to where this
> value becomes important?
>
> Victor
>
> _______________________________________________
> ath10k mailing list
> ath10k@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/ath10k
>
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2015-08-05 17:10 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-03 18:45 qca6164 support vvanpo
2015-08-03 21:44 ` Enrico Tagliavini
2015-08-05 15:32 ` Victor van Poppelen
2015-08-05 17:10 ` Alexandre Maloteaux [this message]
2015-08-04 5:18 ` Michal Kazior
2015-08-04 20:45 ` vvanpo
2015-08-06 5:20 ` Michal Kazior
2015-08-06 5:34 ` Michal Kazior
2015-08-06 16:59 ` Victor van Poppelen
2015-08-07 4:53 ` Michal Kazior
2015-08-07 16:04 ` Victor van Poppelen
2015-08-10 4:36 ` Anish Tondwalkar
2015-08-10 4:53 ` Anish Tondwalkar
2015-08-10 6:15 ` Michal Kazior
2015-08-10 6:41 ` Anish Tondwalkar
2015-08-10 8:15 ` Michal Kazior
[not found] ` <CALZPV0DsQXPfq3+O-8iF4H8i1-164s2jRdvmQjMMnW-qd7reFA@mail.gmail.com>
2015-08-10 8:48 ` Michal Kazior
2015-08-10 12:14 ` Kalle Valo
2015-08-10 13:45 ` Anish Tondwalkar
2015-08-10 14:00 ` Michal Kazior
2015-08-10 14:05 ` Anish Tondwalkar
2015-08-10 16:04 ` Anish Tondwalkar
2015-08-10 23:05 ` Anish Tondwalkar
2015-08-10 23:43 ` Ben Greear
2015-08-11 2:09 ` Anish Tondwalkar
2015-08-11 6:00 ` Michal Kazior
2015-08-11 16:25 ` Anish Tondwalkar
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=55C24373.20200@gmail.com \
--to=a.maloteaux@gmail.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.