Hello, On 8/10/10, Jon Smirl <[email protected]> wrote: > Other network hardware has a include/linux/if_xxxx.h file describing > it. IEEE 802.15.4 has the same info, it is just spread out over > different files. There are also naming conventions that don't match. > For example IEEE80215_ADDR_LEN vs ARCNET_ALEN, ETH_ALEN, etc...
I don't like this change: *_ALEN usually means the length of the _whole_ address as used on the wire. OTOH IEEE802154_ADDR_LEN is the length only of 64bit part of the address. > Do you want to reorganize the headers or should I try? You can try. Several conditions: * af_ieee802154.h should be self-contained. * linux/nl802154.h should contain userspace-exportable information related to netlink interface. I don't see real point in this reorganization. Maybe before writing/sending patches you can just narrow what you'd like to do so we can discuss it? -- With best wishes Dmitry ------------------------------------------------------------------------------ This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev _______________________________________________ Linux-zigbee-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/linux-zigbee-devel
