On 8 July 2016 at 10:55, Ben Greear <gree...@candelatech.com> wrote: > 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...
I don't know if we can disable hardware FCS calculation. :-) It looks like we can only make it be corrupted, for testing. -adrian > > Thanks, > Ben > > >> >> >> -a >> >> >> On 8 July 2016 at 00:08, 김상혁 <tkdgur7...@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@lists.ath9k.org >>> https://lists.ath9k.org/mailman/listinfo/ath9k-devel >> >> _______________________________________________ >> ath9k-devel mailing list >> ath9k-devel@lists.ath9k.org >> https://lists.ath9k.org/mailman/listinfo/ath9k-devel >> > > > -- > Ben Greear <gree...@candelatech.com> > Candela Technologies Inc http://www.candelatech.com > _______________________________________________ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
