Linux IEEE 802.15.4 and 6LoWPAN development
 help / color / mirror / Atom feed
From: Alexander Aring <alex.aring@gmail.com>
To: Martin Townsend <martin.townsend@xsilon.com>
Cc: linux-wpan@vger.kernel.org
Subject: Re: Promiscuous patches
Date: Mon, 15 Sep 2014 14:01:59 +0200	[thread overview]
Message-ID: <20140915120158.GA15047@omega> (raw)
In-Reply-To: <20140915115618.GC13603@omega>

On Mon, Sep 15, 2014 at 01:56:18PM +0200, Alexander Aring wrote:
> On Mon, Sep 15, 2014 at 01:56:07AM +0200, Alexander Aring wrote:
> > On Mon, Sep 15, 2014 at 01:45:51AM +0200, Alexander Aring wrote:
> > > Hi Martin,
> > > 
> > > On Fri, Sep 12, 2014 at 02:14:01PM +0100, Martin Townsend wrote:
> > > > Hi Alex,
> > > > 
> > > > You sent me a patch not long ago to allow automatic setting of promiscous mode.  I seem to have lost this patch, could you resend as I want to look into it.
> > > > 
> > > 
> > > some of my old branch [0].
> > > 
> > > btw.
> > > 
> > > I added to the rework now the promiscous mode and decided to not enable
> > > this mode while setting promiscous mode flag.
> > > 
> > > It's now setted by doing a ifup of a monitor interface. See [1].
> > > 
> > > Maybe you will change it like this (it's better) but there are so many
> > > issue to think about (Disable promiscous if netif on non MONITOR
> > > interfaces etc...).
> > > 
> > > And also you can't have NODE and MONITOR running because it's phy mac
> > > sublayer attribute.
> > > 
> > 
> > I mean with mac sublayer here, some timing critical mac operations/algorithmn
> > done by phy's. Like AACK/ARET, CSMA, etc handling. I don't beleieve that we can
> > ever handle these timing ciriticals inside mac802154.
> > 
> > So we have multiple interfaces but one phy. :-)
> > 
> > One phy means we need to check the constraints that these parameters are
> > always the same on each interface.
> > 
> > On phy pib handling we don't need that. This is no MAC algorithmn, it's
> > only physical changes to the phy rf handling and for the rework we don't
> > have the multiple phy handling anymore.
> > 
> 
> grml s/promiscous/promiscuous everywhere. I need to remember that.
> Sorry.
> 
> I will fix it on the branch.
> 

Seems to be a common error, "grep -r promiscous .":

./drivers/net/ethernet/wiznet/w5100.c:#define   S0_MR_MACRAW		  0x04 /* MAC RAW mode (promiscous) */
./drivers/net/ethernet/wiznet/w5300.c:#define   S0_MR_MACRAW		  0x0004  /* MAC RAW mode (promiscous) */
./drivers/net/wireless/ath/ath10k/htt.h:	/* Non-data in promiscous mode */

- Alex

  reply	other threads:[~2014-09-15 12:02 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5412F199.7010803@xsilon.com>
2014-09-14 23:45 ` Promiscuous patches Alexander Aring
2014-09-14 23:56   ` Alexander Aring
2014-09-15 11:56     ` Alexander Aring
2014-09-15 12:01       ` Alexander Aring [this message]
2014-09-18  8:57   ` Martin Townsend
2014-09-18  9:41     ` Alexander Aring
2014-09-18 10:04       ` Martin Townsend
2014-09-18 10:43         ` Alexander Aring
2014-09-18 12:00           ` Martin Townsend
2014-09-18 12:21             ` Alexander Aring
2014-09-18 12:30               ` Alexander Aring
2014-09-18 12:44                 ` Alexander Aring
2014-09-18 13:25                   ` Martin Townsend
2014-09-18 13:34                     ` Alexander Aring
2014-09-18 13:42                       ` Alexander Aring
2014-09-18 14:36                         ` Martin Townsend
2014-09-18 16:05                           ` Alexander Aring
2014-09-18 16:54                             ` Martin Townsend
2014-09-18 17:07                               ` Alexander Aring
2014-09-18 17:54                                 ` Alexander Aring
2014-09-18 17:56                                   ` Alexander Aring
2014-09-18 18:30                                     ` Martin Townsend
2014-09-18 18:53                                       ` Alexander Aring
2014-09-18 20:34                                         ` Alexander Aring
2014-09-19 10:11                                           ` Alexander Aring
2014-09-20  7:03                                             ` Martin Townsend
2014-09-21 10:06                                               ` Alexander Aring

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=20140915120158.GA15047@omega \
    --to=alex.aring@gmail.com \
    --cc=linux-wpan@vger.kernel.org \
    --cc=martin.townsend@xsilon.com \
    /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