From: poh <poh@qca.qualcomm.com>
To: Ben Greear <greearb@candelatech.com>, <ath10k@lists.infradead.org>
Cc: <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] ath10k: unregister and remove frag_threshold callback
Date: Wed, 10 Dec 2014 10:33:31 -0800 [thread overview]
Message-ID: <548891FB.2060500@qca.qualcomm.com> (raw)
In-Reply-To: <54827F30.8050005@candelatech.com>
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.
>
> Thanks,
> Ben
>
WARNING: multiple messages have this Message-ID (diff)
From: poh <poh@qca.qualcomm.com>
To: Ben Greear <greearb@candelatech.com>, ath10k@lists.infradead.org
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH] ath10k: unregister and remove frag_threshold callback
Date: Wed, 10 Dec 2014 10:33:31 -0800 [thread overview]
Message-ID: <548891FB.2060500@qca.qualcomm.com> (raw)
In-Reply-To: <54827F30.8050005@candelatech.com>
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.
>
> Thanks,
> Ben
>
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2014-12-10 18:33 UTC|newest]
Thread overview: 12+ 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-05 17:16 ` Peter Oh
2014-12-06 3:59 ` Ben Greear
2014-12-06 3:59 ` Ben Greear
2014-12-10 18:33 ` poh [this message]
2014-12-10 18:33 ` poh
2014-12-10 19:03 ` Ben Greear
2014-12-10 19:03 ` Ben Greear
2014-12-10 19:55 ` Peter Oh
2014-12-10 19:55 ` Peter Oh
2014-12-16 7:14 ` Kalle Valo
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=548891FB.2060500@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 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.