All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Jouni Malinen <jkm@devicescape.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
	Elliot Schwartz <elliot@devicescape.com>,
	David Kimdon <david.kimdon@devicescape.com>,
	netdev@vger.kernel.org, Jiri Benc <jbenc@suse.cz>
Subject: Re: [patch 5/5] d80211: add ioctl to stop data frame tx
Date: Thu, 31 Aug 2006 09:23:37 +0200	[thread overview]
Message-ID: <1157009017.3065.14.camel@ux156> (raw)
In-Reply-To: <20060830160115.GB18041@instant802.com>

On Wed, 2006-08-30 at 09:01 -0700, Jouni Malinen wrote:

> Well, it would be nice to get these in quite soon. I know that the
> current mechanism works since it has been used for years, but if the
> netlink-based solution is considered stable and working and unlikely to
> require major changes soon, I don't have anything against using it here.

:)
May I ask you to take a look at nl80211 to see if it matches your
expectations/needs? It obviously needs to be expanded and we may want to
add some multicast groups that applications can subscribe to for scan
results/radar detection/management frames/...
What really should be done soon is implementing transmit status
notification for injected packets since injection is already working. I
just happen to not need it at the moment and have a bunch of other
things to do.

> Once there is mechanism to replace all the current functionality, I
> would just drop it. There is some meta information, like signal
> strength, in the header, so this does not only include event
> notifications, but also additional data for frames.

That meta information can be transmitted through other channels too
though :)

johannes

  reply	other threads:[~2006-08-31  7:23 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20060822173241.313859000@devicescape.com>
2006-08-22 17:33 ` [patch 1/5] d80211: allow for large scan results David Kimdon
2006-08-22 17:33 ` [patch 2/5] d80211: fix multiple device support David Kimdon
2006-08-22 17:33 ` [patch 3/5] d80211: fix interface removal David Kimdon
2006-08-23  7:20   ` Johannes Berg
2006-08-23 16:05     ` Jiri Benc
2006-08-22 17:34 ` [patch 4/5] d80211/bcm43xx: fix build for ARM David Kimdon
2006-08-22 18:58   ` Michael Buesch
2006-08-22 17:34 ` [patch 5/5] d80211: add ioctl to stop data frame tx David Kimdon
2006-08-23  7:25   ` Johannes Berg
2006-08-23 16:09     ` Jiri Benc
2006-08-28 18:34       ` Elliot Schwartz
2006-08-23 19:20     ` Simon Barber
2006-08-28 18:29     ` Elliot Schwartz
2006-08-29  7:30       ` Johannes Berg
2006-08-29 11:45         ` John W. Linville
2006-08-29 18:39           ` Jouni Malinen
2006-08-30  7:26             ` Johannes Berg
2006-08-30 16:01               ` Jouni Malinen
2006-08-31  7:23                 ` Johannes Berg [this message]
2006-09-22 12:13   ` Jiri Benc

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=1157009017.3065.14.camel@ux156 \
    --to=johannes@sipsolutions.net \
    --cc=david.kimdon@devicescape.com \
    --cc=elliot@devicescape.com \
    --cc=jbenc@suse.cz \
    --cc=jkm@devicescape.com \
    --cc=linville@tuxdriver.com \
    --cc=netdev@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 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.