Hello, On Wed, Nov 30, 2011 at 6:25 PM, Alexander Smirnov <alex.bluesman.smir...@gmail.com> wrote: > Support for IEEE 802.15.4 management information base, > routine like setting of HW address, PAN id, channel etc... > > Signed-off-by: Alexander Smirnov <alex.bluesman.smir...@gmail.com> > --- > include/linux/if.h | 3 + > net/mac802154/Makefile | 2 +- > net/mac802154/mac802154.h | 22 ++++ > net/mac802154/mib.c | 247 > +++++++++++++++++++++++++++++++++++++++++++++ > net/mac802154/mib.h | 35 +++++++ > 5 files changed, 308 insertions(+), 1 deletions(-) > create mode 100644 net/mac802154/mib.c > create mode 100644 net/mac802154/mib.h > > diff --git a/include/linux/if.h b/include/linux/if.h > index 06b6ef6..deaf14c 100644 > --- a/include/linux/if.h > +++ b/include/linux/if.h > @@ -76,6 +76,9 @@ > #define IFF_BRIDGE_PORT 0x4000 /* device used as bridge port > */ > #define IFF_OVS_DATAPATH 0x8000 /* device used as Open vSwitch > * datapath port */ > + > +#define IFF_IEEE802154_COORD 0x400 /* IEEE802.15.4 PAN coordinator */ > +
I remember this define, but I don't remember why we did it this way. Is it suitable to use this namespace for device-specific flags? > #define IFF_TX_SKB_SHARING 0x10000 /* The interface supports sharing > * skbs on transmit */ > #define IFF_UNICAST_FLT 0x20000 /* Supports unicast filtering > */ -- With best wishes Dmitry ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d _______________________________________________ Linux-zigbee-devel mailing list Linux-zigbee-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-zigbee-devel
