From: Johannes Berg <johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
To: radiotap <radiotap-sUITvd46vNxg9hUCZPvPmw@public.gmane.org>
Cc: linux-wireless <linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [Proposal]TX flags
Date: Thu, 16 Apr 2009 22:48:27 +0200 [thread overview]
Message-ID: <1239914907.26575.28.camel@johannes.local> (raw)
In-Reply-To: <20090416203353.GC25412-eZodSLrBbDpBDgjK7y7TUQ@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1241 bytes --]
On Thu, 2009-04-16 at 15:33 -0500, David Young wrote:
> > > TX Flags absent: Use RTS & CTS as needed.
> > > TX Flags present: {
> > > RTS=0, CTS=0: Use RTS & CTS as needed.
> > > RTS=0, CTS=1: Use CTS-to-self.
> > > RTS=1, CTS=0: Use RTS/CTS-handshake.
> > > RTS=1, CTS=1: Use neither RTS nor CTS.
> > > }
> > >
> > > (By reading the second proposal again, I find it more and more
> > > sympathetic... but let the discussion decide.)
> >
> > That _works_, but is impossible to describe in any feature discovery.
>
> The discovery mechanism that we have begun to discuss would have a hard
> time describing that feature at its current level of development, but
> that is not the only feature that it will have a hard time describing.
> Feature discovery may need more development before we measure new
> proposals against it. What do you think?
True, but why make the job harder than it is? Michael has a good point
too. And we have free bits, I don't see why we can't add one for "do
what I said" (wrt. rts/cts), which, if unset means to do be in automatic
mode and ignore the other bits.
Or we really do use a two-bit field with values;
0 automatic
1 neither
2 rts
3 cts
or something.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2009-04-16 20:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-15 0:33 [Proposal]TX flags Gábor Stefanik
[not found] ` <69e28c910904141733m72ce521ap8f1865bec991fff7-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-04-16 15:37 ` David Young
2009-04-16 17:28 ` Johannes Berg
[not found] ` <1239902910.26575.14.camel-YfaajirXv2244ywRPIzf9A@public.gmane.org>
2009-04-16 18:47 ` Gábor Stefanik
[not found] ` <69e28c910904161147h5a68d3b5nd054b043d6ad2719-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-04-16 18:59 ` Johannes Berg
[not found] ` <1239908374.26575.20.camel-YfaajirXv2244ywRPIzf9A@public.gmane.org>
2009-04-16 19:10 ` Michael Buesch
[not found] ` <200904162110.05150.mb-fseUSCV1ubazQB+pC5nmwQ@public.gmane.org>
2009-04-16 20:48 ` David Young
[not found] ` <20090416204806.GD25412-eZodSLrBbDpBDgjK7y7TUQ@public.gmane.org>
2009-04-17 1:24 ` Gábor Stefanik
[not found] ` <69e28c910904161824t7af6860dxebf3a13069b924d5-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-04-17 9:50 ` Johannes Berg
2009-04-16 20:33 ` David Young
[not found] ` <20090416203353.GC25412-eZodSLrBbDpBDgjK7y7TUQ@public.gmane.org>
2009-04-16 20:48 ` Johannes Berg [this message]
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=1239914907.26575.28.camel@johannes.local \
--to=johannes-cdvu00un1vgdhxzaddlk8q@public.gmane.org \
--cc=linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=radiotap-sUITvd46vNxg9hUCZPvPmw@public.gmane.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).