From: Ben Greear <greearb@candelatech.com>
To: ath10k <ath10k@lists.infradead.org>
Subject: Should TARGET_NUM_PEER_KEYS == WMI_MAX_KEY_INDEX + 1?
Date: Mon, 17 Feb 2014 12:02:35 -0800 [thread overview]
Message-ID: <53026ADB.2090206@candelatech.com> (raw)
Maybe this is the reason my firmware is running out of space for keys...
When adding keys, the driver checks for index > WMI_MAX_KEY_INDEX (which is 3),
but when configuring the firmware, TARGET_NUM_PEER_KEYS (2) is used for both
firmware branches.
Maybe the firmware should be told to allocate space for 4 keys for each peer?
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
reply other threads:[~2014-02-17 20:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=53026ADB.2090206@candelatech.com \
--to=greearb@candelatech.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox