linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Oh <poh@qca.qualcomm.com>
To: Ben Greear <greearb@candelatech.com>
Cc: <ath10k@lists.infradead.org>, <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] ath10k: unregister and remove frag_threshold callback
Date: Wed, 10 Dec 2014 11:55:36 -0800	[thread overview]
Message-ID: <5488A538.4000005@qca.qualcomm.com> (raw)
In-Reply-To: <5488991A.9000604@candelatech.com>


On 12/10/2014 11:03 AM, Ben Greear wrote:
> On 12/10/2014 10:33 AM, poh wrote:
>> On 12/05/2014 07:59 PM, Ben Greear wrote:
>>>
>>> On 12/05/2014 09:16 AM, Peter Oh wrote:
>>>> Setting fragmentation threshold has not been supported by
>>>> any of firmware versions, hence unregister the callback and
>>>> remove the function.
>>> How hard is it to just fix the firmware instead?
>> It's due to hardware limitation such as lack of buffers/RAM size limitation, hence it's very hard from sw perspective.
> Out of curiosity, how much more RAM do you need?  I was able to squeeze somewhere around 80k out of the firmware
> in my quest to support 64 station vdevs....
I don't have exact number of memory since the answer is from our 
firmware team.
I assume it's not coming in near future to firmware.
> Thanks,
> Ben
>
Thanks,
Peter

  reply	other threads:[~2014-12-10 19:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-05 17:16 [PATCH] ath10k: unregister and remove frag_threshold callback Peter Oh
2014-12-06  3:59 ` Ben Greear
2014-12-10 18:33   ` poh
2014-12-10 19:03     ` Ben Greear
2014-12-10 19:55       ` Peter Oh [this message]
2014-12-16  7:14 ` Kalle Valo

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=5488A538.4000005@qca.qualcomm.com \
    --to=poh@qca.qualcomm.com \
    --cc=ath10k@lists.infradead.org \
    --cc=greearb@candelatech.com \
    --cc=linux-wireless@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).