linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: linux-wireless@vger.kernel.org
Subject: [RFC 0/2] remain-on-channel HW offload
Date: Thu, 16 Dec 2010 15:15:18 +0100	[thread overview]
Message-ID: <20101216141518.879668720@sipsolutions.net> (raw)

This adds functionality to enable remain-on-channel
hardware offload to mac80211 drivers. Any frames
transmitted during that time get a new TX flag and
must be transmitted correctly by the driver -- any
other activity isn't stopped, so the device must
have different queues for the different frames.

johannes


             reply	other threads:[~2010-12-16 14:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-16 14:15 Johannes Berg [this message]
2010-12-16 14:15 ` [RFC 1/2] mac80211: implement hardware offload for remain-on-channel Johannes Berg
2010-12-16 14:15 ` [RFC 2/2] mac80211: implement off-channel TX using hw r-o-c offload Johannes Berg
     [not found] ` <14A60364A8914B6FA548CF6DCEDDBD06@ChuckPC>
2010-12-16 14:40   ` [RFC 0/2] remain-on-channel HW offload Johannes Berg

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=20101216141518.879668720@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --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;
as well as URLs for NNTP newsgroup(s).