From: Kalle Valo <kvalo@codeaurora.org>
To: Miles Hu <milehu@codeaurora.org>
Cc: ath11k@lists.infradead.org
Subject: Re: [PATCH v5 0/6] ath11k: add monitor mode support
Date: Tue, 23 Apr 2019 17:05:07 +0300 [thread overview]
Message-ID: <87a7ggzujw.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1555373576-4771-1-git-send-email-milehu@codeaurora.org> (Miles Hu's message of "Mon, 15 Apr 2019 17:12:50 -0700")
Miles Hu <milehu@codeaurora.org> writes:
> Adding monitor mode in ath11k. It can be enabled
> by commands below:
>
> ifconfig wlan0 down
> iw wlan0 set type monitor
> ifconfig wlan0 up
>
> change channel:
> iw wlan0 set freq 5805 80 5775
>
> Change summary:
> 1. create monitor status/destination/buffer/link descriptor rings.
> 2. enable these rings and push ring filters to buffer/status rings.
> 3. add napi entry point for monitor status and destination rings process.
> 4. implement monitor status/buffer rings replenish.
> 5. process entries from the status ring to get ppdu id and tlv status.
> 6. process entries from the destination ring by comparing ppdu id to build
> msdu list.
> 7. merge msdu list to mpdu and copy rx status to cb.
> 8. deliver mpdu to upper layer.
>
> Known issues:
> - Coexist with other interface type (AP/STA) not fully supported.
> - higher data rates (11ax) not supported. radiotap needs proper info.
> - signal strength and rate idx not accurate in some packets.
This does not apply:
Applying: ath11k: init/deinit monitor rings
fatal: sha1 information is lacking or useless (drivers/net/wireless/ath/ath11k/core.h).
error: could not build fake ancestor
Patch failed at 0001 ath11k: init/deinit monitor rings
And the sha1 id is incorrect so I can't use 3-way merge to correct it
myself. Please ALWAYS use the ath11k-bringup branch as the baseline and
make sure you don't have other patches applied, otherwise it will be
pain to handle conflicts.
--
Kalle Valo
_______________________________________________
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
prev parent reply other threads:[~2019-04-23 14:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-16 0:12 [PATCH v5 0/6] ath11k: add monitor mode support Miles Hu
2019-04-16 0:12 ` [PATCH v5 1/6] ath11k: init/deinit monitor rings Miles Hu
2019-04-16 0:12 ` [PATCH v5 2/6] ath11k: monitor filter set function Miles Hu
2019-04-16 0:12 ` [PATCH v5 3/6] ath11k: htt setup monitor rings Miles Hu
2019-04-16 0:12 ` [PATCH v5 4/6] ath11k: monitor mode attach/detach Miles Hu
2019-04-16 0:12 ` [PATCH v5 5/6] ath11k: enable/disable monitor mode and destination ring entry process Miles Hu
2019-04-16 0:12 ` [PATCH v5 6/6] ath11k: merge msdu tlv process and status/destination ring process Miles Hu
2019-04-23 14:05 ` Kalle Valo [this message]
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=87a7ggzujw.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=ath11k@lists.infradead.org \
--cc=milehu@codeaurora.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