Long/short addressing is going to take some more work....
For example:
memset(dev->broadcast, 0xff, IEEE802154_ADDR_LEN);
The 0xFF FF FF FF FF FF FF FF comes back in:
int mac802154_header_create(struct sk_buff *skb,
struct net_device *dev,
unsigned short type, const void *_daddr,
const void *_saddr, unsigned len)
Where it gets cast to:
const struct ieee802154_addr *daddr = _daddr;
This also means IEEE802154_ALEN is not 8, it is sizeof(struct ieee802154_addr )
-----------------------------------
I'm wondering if short addresses should be exposed inside the upper
layers. Maybe use a netlink command to associate to a PAN. Then always
use 8 byte addresses inside of Linux. When the 8-byte addresses get to
the lower layers the PAN gets added and the may be converted to short
addresses. Do FFDs always know the whole map of short address to long
address, or it is the map only known to the coordinator?
--
Jon Smirl
[email protected]
------------------------------------------------------------------------------
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
