From: Johannes Berg <johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
To: "Gábor Stefanik" <netrolller.3d-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Michael Buesch <mb-fseUSCV1ubazQB+pC5nmwQ@public.gmane.org>,
radiotap-sUITvd46vNxg9hUCZPvPmw@public.gmane.org,
linux-wireless
<linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [Proposal]TX flags
Date: Fri, 17 Apr 2009 11:50:59 +0200 [thread overview]
Message-ID: <1239961859.26575.44.camel@johannes.local> (raw)
In-Reply-To: <69e28c910904161824t7af6860dxebf3a13069b924d5-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> (sfid-20090417_032507_012632_CF7AA3F9)
[-- Attachment #1: Type: text/plain, Size: 659 bytes --]
On Fri, 2009-04-17 at 03:24 +0200, Gábor Stefanik wrote:
> > I see the point that Michael is making. What do you think? Shall
> > we treat it as a 2-bit wide unsigned integer field in the Tx flags,
> > instead?
> >
>
> IMO that is a good idea, if we accept having non-booleans in a flags
> field. In that case, this proposal comes to my mind:
> -Define the second and third bits (mask 0x0006) as a quad-state flag
> indicating the use of RTS/CTS. So, we can have these values for the
> flag (accessible as (TXFlags & 0x0006) >> 1):
> 0: neither
> 1: rts
> 2: cts
> 3: auto-select (only makes sense when sending & during feature discovery)=
next prev parent reply other threads:[~2009-04-17 9:50 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 [this message]
2009-04-16 20:33 ` David Young
[not found] ` <20090416203353.GC25412-eZodSLrBbDpBDgjK7y7TUQ@public.gmane.org>
2009-04-16 20:48 ` 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=1239961859.26575.44.camel@johannes.local \
--to=johannes-cdvu00un1vgdhxzaddlk8q@public.gmane.org \
--cc=linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mb-fseUSCV1ubazQB+pC5nmwQ@public.gmane.org \
--cc=netrolller.3d-Re5JQEeQqe8AvxtiuMwx3w@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).