From: Michael Stahn <m1kes@web.de>
To: linux-wireless@vger.kernel.org
Subject: Re: [Proposal]TX flags
Date: Tue, 23 Mar 2010 15:50:31 +0000 (UTC) [thread overview]
Message-ID: <loom.20100323T162144-640@post.gmane.org> (raw)
In-Reply-To: 201003230942.15718.br1@einfach.org
> similar to this we would also need to be able to specify that the beacon TSF
> should not be overwritten. maybe a general flag like "do not change" would do?
Is TSF really overwritten at manual injection from userspace?
Yes such a flag would be handy, the question is: is there a
need for controlling every individual TX-option (min 3 with
Sequence, Duration and TSF). If not this would be a good
solution and easy to implement. Are there any other things
which are commonly changed?
next prev parent reply other threads:[~2010-03-23 15:50 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-15 0:33 [Proposal]TX flags Gábor Stefanik
2009-04-15 0:33 ` Gábor Stefanik
2009-04-16 15:37 ` David Young
2009-04-16 15:37 ` David Young
2009-04-16 17:28 ` Johannes Berg
2009-04-16 17:28 ` Johannes Berg
2009-04-16 18:47 ` Gábor Stefanik
2009-04-16 18:47 ` Gábor Stefanik
2009-04-16 18:59 ` Johannes Berg
2009-04-16 18:59 ` Johannes Berg
2009-04-16 19:10 ` Michael Buesch
2009-04-16 19:10 ` Michael Buesch
2009-04-16 20:48 ` David Young
2009-04-16 20:48 ` David Young
2009-04-17 1:24 ` Gábor Stefanik
2009-04-17 1:24 ` Gábor Stefanik
2009-04-17 9:50 ` Johannes Berg
2009-04-17 9:50 ` Johannes Berg
2009-04-16 20:33 ` David Young
2009-04-16 20:33 ` David Young
2009-04-16 20:48 ` Johannes Berg
2009-04-16 20:48 ` Johannes Berg
2010-03-22 19:32 ` Michael Stahn
2010-03-23 0:42 ` Bruno Randolf
2010-03-23 15:50 ` Michael Stahn [this message]
2010-03-24 11:15 ` Bruno Randolf
2010-03-24 19:43 ` Pavel Roskin
2010-03-24 20:26 ` Gábor Stefanik
2010-03-25 1:22 ` Michael Stahn
2010-03-25 20:32 ` Gábor Stefanik
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=loom.20100323T162144-640@post.gmane.org \
--to=m1kes@web.de \
--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 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.