All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Young <dyoung@pobox.com>
To: radiotap@radiotap.org, linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [Proposal]TX flags
Date: Thu, 16 Apr 2009 15:33:54 -0500	[thread overview]
Message-ID: <20090416203353.GC25412@ojctech.com> (raw)
In-Reply-To: <1239908374.26575.20.camel@johannes.local>

On Thu, Apr 16, 2009 at 08:59:34PM +0200, Johannes Berg wrote:
> On Thu, 2009-04-16 at 20:47 +0200, G?bor Stefanik wrote:
> 
> > Alternatively, the meanings of the {0,0} and {1,1} cases could be
> > switched around (making the {0,0} case more logical, at the expense of
> > the {1,1} one):
> > 
> > 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?

Dave

-- 
David Young             OJC Technologies
dyoung@ojctech.com      Urbana, IL * (217) 278-3933

WARNING: multiple messages have this Message-ID (diff)
From: David Young <dyoung-e+AXbWqSrlAAvxtiuMwx3w@public.gmane.org>
To: radiotap-sUITvd46vNxg9hUCZPvPmw@public.gmane.org,
	linux-wireless
	<linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [Proposal]TX flags
Date: Thu, 16 Apr 2009 15:33:54 -0500	[thread overview]
Message-ID: <20090416203353.GC25412@ojctech.com> (raw)
In-Reply-To: <1239908374.26575.20.camel-YfaajirXv2244ywRPIzf9A@public.gmane.org>

On Thu, Apr 16, 2009 at 08:59:34PM +0200, Johannes Berg wrote:
> On Thu, 2009-04-16 at 20:47 +0200, G?bor Stefanik wrote:
> 
> > Alternatively, the meanings of the {0,0} and {1,1} cases could be
> > switched around (making the {0,0} case more logical, at the expense of
> > the {1,1} one):
> > 
> > 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?

Dave

-- 
David Young             OJC Technologies
dyoung-eZodSLrBbDpBDgjK7y7TUQ@public.gmane.org      Urbana, IL * (217) 278-3933

  parent reply	other threads:[~2009-04-16 20:33 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 [this message]
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
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=20090416203353.GC25412@ojctech.com \
    --to=dyoung@pobox.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=radiotap@radiotap.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.