All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] Fully control ethernet frame
Date: Fri, 8 Jul 2016 10:55:34 -0700	[thread overview]
Message-ID: <577FE916.5010608@candelatech.com> (raw)
In-Reply-To: <CAJ-VmomvDWVk1Ebur03mUAdnSz4rUVsR2QY3aJDoOmr7ezv5dQ@mail.gmail.com>

On 07/08/2016 10:46 AM, Adrian Chadd wrote:
> hi,
>
> There's a transmit descriptor bit, AR_CorruptFCS, which you can set
> and it will negate the FCS so it always fails.
>
> Look in the ar9002_mac.c / ar9003_mac.c where NoAck is set; i think
> AR_CorruptFCS should also be set in that (ctl1 for ar9002 and below,
> ctl12 for ar9003)

Neat.

e1000e (I think?) and some other drivers I mucked with long ago have
the ability to accept FCS from user-space.  If someone adds that
same support to ath9k then that would make applications supporting
this API able to work on ath9k devices as well...

Thanks,
Ben

>
>
> -a
>
>
> On 8 July 2016 at 00:08, ??? <tkdgur7896@gmail.com> wrote:
>> Hi all,
>>
>> I want to make corrupted packet by wrong CRC/FCS
>>
>> I have two questions.
>>
>> 1) Can I handle CRC/FCS when ethernet frame be made at Tx ?
>>
>> 2-1) If can, how can I ? or where is related source?
>>
>> 2-2) If can?t, is there any way to control CRC/FCS at Tx ?
>>
>> Thanks.
>> _______________________________________________
>> ath9k-devel mailing list
>> ath9k-devel at lists.ath9k.org
>> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
> _______________________________________________
> ath9k-devel mailing list
> ath9k-devel at lists.ath9k.org
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>


-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com

  reply	other threads:[~2016-07-08 17:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-08  7:08 [ath9k-devel] Fully control ethernet frame 김상혁
2016-07-08 17:46 ` Adrian Chadd
2016-07-08 17:55   ` Ben Greear [this message]
2016-07-08 23:56     ` Adrian Chadd
2016-07-13  8:52       ` SangHyuk Kim
2016-07-13 20:45         ` 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=577FE916.5010608@candelatech.com \
    --to=greearb@candelatech.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 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.