All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: ath10k <ath10k@lists.infradead.org>
Subject: htt_rx questions in 4.0 kernel.
Date: Tue, 05 May 2015 15:35:04 -0700	[thread overview]
Message-ID: <55494598.2060603@candelatech.com> (raw)

I am slowly tracking down problems with receiving data frames
on 3.19 and higher kernels, when using my rx-sw-crypt patch
and CT firmware.

I think the main thing my patch is changing in this case is that
the frames are received in raw mode with this patch enabled.

Hard to do a bisect, because the rx logic changed so much and I
have to apply fairly tricky patches to make my feature work, but
3.18 and earlier seem to work fine, and 3.19 and 4.0 does not.

Latest clue appears to be that ARP frames are received fine (data
contents looks right), but the stack fails the is_data() check.

While poking at this further, I noticed that ath10k_htt_rx_h_undecap
defines 'hdr' and assigns it, but never uses it.

I also do not see the first_hdr used when decapping raw
frames.

Maybe that is part of the problem?

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:[~2015-05-05 22:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-05 22:35 Ben Greear [this message]
2015-05-06  5:38 ` htt_rx questions in 4.0 kernel Michal Kazior
2015-05-06 14:54   ` Ben Greear
2015-05-07 22:59     ` Ben Greear
2015-05-06 10:39 ` changing hw address of ath10k card Sebastian Gottschall
2015-05-06 11:06   ` Michal Kazior
2015-05-06 11:16     ` Sebastian Gottschall
2015-05-06 11:32       ` Michal Kazior
2015-05-06 13:21         ` Sebastian Gottschall

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=55494598.2060603@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 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.