Guys, I'd like to join the foray too :) > I'm sorry but your suggestions make nearly no sense. The current design > is targeted different applications and different types of interfaces which > can be bound to each radio. Ability to bind different types of interfaces to the same radio is desirable. However, is there any scenario where multiple interfaces would be simultaneously bound to the same radio at the same time? Or did I misunderstand the purpose of storing a list of slaves in mac802154_priv? Also, wouldn't this cause some confusion as to which specific interface should handle packets received over a particular radio?
> other types are mesh, AP, monitor, maybe more). For LoWPAN we don't > have such sane default. LoWPAN != IEEE 802.15.4, so we don't want > to enforce users to have that interface by default. Doesn't IEEE802.15.4 qualify as a sane default? Even if it doesn't, and we require the user to explicitly add an interface before he can use the radio, can we not restrict him to one interface per radio at any given time, thereby preventing the aforementioned confusion? Warm Regards, Felix. ------------------------------------------------------------------------------ Virtualization & Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ _______________________________________________ Linux-zigbee-devel mailing list Linux-zigbee-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-zigbee-devel
