From: SangHyuk Kim <tkdgur7896@gmail.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] I can't find ath9k ofdm mapping part
Date: Tue, 18 Oct 2016 14:46:37 +0900 [thread overview]
Message-ID: <CA+eadOCPtGNMjxMUxbbDR5nyJkwni-cOBfqgeSYkVGCQN-nJdA@mail.gmail.com> (raw)
Dear all,
I'm using ath9k_ar9003 type and ath9k_htc type.
And I'm studying how packet be transmitted through wifi driver.
I have researched from application layer to phy and I'm done to the MAC
layer.
However, I can't find any parts about data mapping to carriers.
As I know, for OFDM, there're several subcarrier in specific bandwidth and
user data(payload) fills subcarrier.
Which part responsible for mapping?
It is implemented at firmware level ?
Please help me !
Thanks.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20161018/62bb302a/attachment.htm
next reply other threads:[~2016-10-18 5:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-18 5:46 SangHyuk Kim [this message]
2016-10-19 20:54 ` [ath9k-devel] I can't find ath9k ofdm mapping part Adrian Chadd
2016-10-20 0:47 ` SangHyuk Kim
2016-10-26 3:29 ` Adrian Chadd
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=CA+eadOCPtGNMjxMUxbbDR5nyJkwni-cOBfqgeSYkVGCQN-nJdA@mail.gmail.com \
--to=tkdgur7896@gmail.com \
--cc=ath9k-devel@lists.ath9k.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).