From: Adrian Chadd <adrian@freebsd.org>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] I can't find ath9k ofdm mapping part
Date: Tue, 25 Oct 2016 20:29:05 -0700 [thread overview]
Message-ID: <CAJ-VmonSvxV3GmLQB6dXQ5fpLeeS+zZrcxNjY+tNqxsuKrFU-g@mail.gmail.com> (raw)
In-Reply-To: <CA+eadOCiwV0xAw=7yhLGX=h=0Fh-YFy3GZfhk_UUY83HFRz70Q@mail.gmail.com>
On 19 October 2016 at 17:47, SangHyuk Kim <tkdgur7896@gmail.com> wrote:
> Thank you for your reply.
>
> Then can I control (modify) hardware operating ?
>
> If it's possible, how can I approach that ?
You can control what TX rate is used, TX power, number of streams, etc
by TX descriptor fields. But it all maps to the known 11abgn encoding
types.
-adrian
>
>
> 2016-10-20 5:54 GMT+09:00 Adrian Chadd <adrian@freebsd.org>:
>>
>> hi,
>>
>> it's done for you in the chip in hardware. not firmware.
>>
>>
>> -a
>>
>>
>> On 17 October 2016 at 22:46, SangHyuk Kim <tkdgur7896@gmail.com> wrote:
>> > 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.
>> >
>> > _______________________________________________
>> > ath9k-devel mailing list
>> > ath9k-devel at lists.ath9k.org
>> > https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>> >
>
>
prev parent reply other threads:[~2016-10-26 3:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-18 5:46 [ath9k-devel] I can't find ath9k ofdm mapping part SangHyuk Kim
2016-10-19 20:54 ` Adrian Chadd
2016-10-20 0:47 ` SangHyuk Kim
2016-10-26 3:29 ` Adrian Chadd [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=CAJ-VmonSvxV3GmLQB6dXQ5fpLeeS+zZrcxNjY+tNqxsuKrFU-g@mail.gmail.com \
--to=adrian@freebsd.org \
--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).