From: Kalle Valo <kvalo@codeaurora.org>
To: <tehuang@realtek.com>
Cc: <yhchuang@realtek.com>, <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 1/5] rtw88: increse the size of rx buffer size
Date: Tue, 29 Sep 2020 08:23:20 +0000 (UTC) [thread overview]
Message-ID: <20200929082320.20502C433CB@smtp.codeaurora.org> (raw)
In-Reply-To: <20200925061219.23754-2-tehuang@realtek.com>
<tehuang@realtek.com> wrote:
> From: Tzu-En Huang <tehuang@realtek.com>
>
> The vht capability of MAX_MPDU_LENGTH is 11454 in rtw88; however, the rx
> buffer size for each packet is 8192. When receiving packets that are
> larger than rx buffer size, it will leads to rx buffer ring overflow.
>
> Signed-off-by: Tzu-En Huang <tehuang@realtek.com>
5 patches applied to wireless-drivers-next.git, thanks.
ee755732b7a1 rtw88: increse the size of rx buffer size
5c831644e1f4 rtw88: handle and recover when firmware crash
0fbc2f0f34cc rtw88: add dump firmware fifo support
714f71f94ab3 rtw88: add dump fw crash log
fada09311d17 rtw88: show current regulatory in tx power table
--
https://patchwork.kernel.org/patch/11799087/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2020-09-29 8:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-25 6:12 [PATCH 0/5] rtw88: add firmware crash recovery and some fixes tehuang
2020-09-25 6:12 ` [PATCH 1/5] rtw88: increse the size of rx buffer size tehuang
2020-09-29 8:23 ` Kalle Valo [this message]
2020-09-25 6:12 ` [PATCH 2/5] rtw88: handle and recover when firmware crash tehuang
2020-09-29 8:20 ` Kalle Valo
2020-09-25 6:12 ` [PATCH 3/5] rtw88: add dump firmware fifo support tehuang
2020-10-01 19:06 ` Nathan Chancellor
2020-10-02 8:14 ` Kalle Valo
2020-10-02 8:43 ` Nathan Chancellor
2020-10-06 5:53 ` Kalle Valo
2020-09-25 6:12 ` [PATCH 4/5] rtw88: add dump fw crash log tehuang
2020-09-25 6:12 ` [PATCH 5/5] rtw88: show current regulatory in tx power table tehuang
2020-09-25 16:29 ` 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=20200929082320.20502C433CB@smtp.codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
--cc=tehuang@realtek.com \
--cc=yhchuang@realtek.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 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.