Linux wireless drivers development
 help / color / mirror / Atom feed
From: "David Lynch Jr." <ml@dlasys.net>
To: Christian Lamparter <chunkeey@googlemail.com>
Cc: linux-wireless@vger.kernel.org
Subject: CARL9170 driver/firmware questions
Date: Sat, 16 Jun 2012 22:53:47 -0400	[thread overview]
Message-ID: <1339901627.7998.15.camel@hp-dhlii> (raw)
In-Reply-To: <201204252201.50803.chunkeey@googlemail.com>

I am working on another AR9170 project. 
This essentially requires injecting broadcast packets of specific size,
frequency, ... at extremely precise intervals.

I am trying to understand the data flow in the firmware. 

Initially I was looking to generate the frames in the firmware. 
The payload is simple. Though I am pondering the wisdom of that right
now. Regardless, I will have to control my frames in firmware, so I need
to separate them from normal traffic and then feed them into the Radio
Queues at the appropriate times. 

Am I correct that the same struct dma_desc is being used by both USB and
the Radio ?

Each dma_desc points to a payload, for tx packets this is a  struct
carl9170_tx_superframe, which must also be what the skb pointed to by 
void carl9170_usb_tx(struct ar9170 *ar, struct sk_buff *skb) is
sending ?

Can I construct a carl9170_tx_superframe on the host side, with
something to allow me to identify it in handle_download in the firmware,
perform minor mangling of the contents, and repeatedly transmit it at
fixed intervals using wlan_tx() ?


 

 


  reply	other threads:[~2012-06-17  2:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-25 19:29 AR9170 documentation for a driver port? Stephen P
2012-04-25 20:01 ` Christian Lamparter
2012-06-17  2:53   ` David Lynch Jr. [this message]
2012-06-17 10:42     ` CARL9170 driver/firmware questions Christian Lamparter
     [not found] ` <201206172048.59657.chunkeey@googlemail.com>
     [not found]   ` <1341734893.20243.15.camel@hp-dhlii>
     [not found]     ` <201207081443.03106.chunkeey@googlemail.com>
2012-07-08 16:54       ` David Lynch Jr.

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=1339901627.7998.15.camel@hp-dhlii \
    --to=ml@dlasys.net \
    --cc=chunkeey@googlemail.com \
    --cc=linux-wireless@vger.kernel.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