The QCA99X0 4 addresses RX packets pad 2 bytes at the beginning of
MSDU instead the end of ieee80211 header to keep align. The currently
RX data path can't parse the header correctly in this case. This
patch fixes it for QCA99X0
Signed-off-by: Yanbo Li
diff --git a/drivers/net/wireless/ath/ath10
"Li, Yanbo" writes:
>> > + /* The padding bytes's location is different on various chips */
>> > + enum ath10k_loc_4addr_pad loc_4addr_pad;
>>
>> I think that loc prefix is a bit misleading, it reminds me of
>> locationing/positioning etc. What about ath10k_hw_4addr_pad?
>>
>
Hi Kalle\Yanbo,
On Mon, Nov 16, 2015 at 10:57:44PM +0200, Kalle Valo wrote:
> "Li, Yanbo" writes:
>
> >> > +/* The padding bytes's location is different on various
> >> > chips */
> >> > +enum ath10k_loc_4addr_pad loc_4addr_pad;
> >>
> >> I think that loc prefix
> -Original Message-
> From: Shajakhan, Mohammed Shafi (Mohammed Shafi)
> Sent: Friday, November 20, 2015 5:32 AM
> To: Valo, Kalle
> Cc: Li, Yanbo; linux-wireless@vger.kernel.org; ath...@lists.infradead.org
> Subject: Re: [PATCH] ath10k: Adjust the RX packet pad
Yanbo Li writes:
> The QCA99X0 4 addresses RX packets pad 2 bytes at the beginning of
> MSDU instead the end of ieee80211 header to keep align. The currently
> RX data path can't parse the header correctly in this case. This
> patch fixes it for QCA99X0
>
> Signed-off-by: Yanbo Li
Applied, than
Yanbo Li writes:
> The QCA99X0 4 addresses RX packets pad 2 bytes at the beginning of
> MSDU instead the end of ieee80211 header to keep align. The currently
> RX data path can't parse the header correctly in this case. This
> patch fixes it for QCA99X0
>
> Signed-off-by: Yanbo Li
>
> diff --git
> -Original Message-
> From: Valo, Kalle
> Sent: Thursday, October 22, 2015 10:25 PM
> To: Li, Yanbo
> Cc: dreamfly...@gmail.com; ath...@lists.infradead.org; linux-
> wirel...@vger.kernel.org
> Subject: Re: [PATCH] ath10k: Adjust the RX packet pad offset at