Sjoerd and I started dissecting our NM-0.6 divergence so that we can begin porting that necessary pieces of that divergence to NM-0.7. Several highlights from our reading of two important files follow. NM-specific terminology is /emphasized/.
nm-device-802-11-mesh-olpc.c [1] contains: * A nice description of the state machine currently used to decide change network associations. http://tinyurl.com/5xnxgw * The flag-file MESH_STEP_FILE (/etc/NetworkManager/mesh-step) which can be used to alter the initial state of the aforementioned connectivity state machine. http://tinyurl.com/4ltm2u * The callbacks and setup/teardown logic on lines 536-661 which sync the 'scanning' flag between the /mesh device/ (a.k.a. the msh0 network interface) and its /companion (wireless) device/. http://tinyurl.com/5ydns6 * Hoary netlink socket code (perhaps duplicating functionality of iwconfig?) in the second quarter of the file. http://tinyurl.com/427fxg * Hoary /mpp/ (mesh portal point) - http://tinyurl.com/4yxbyr /aipd/ (avahi-autoipd) - http://tinyurl.com/43kygw and device association logic - http://tinyurl.com/4fstfh in the second half of the file. * The init method of the Mesh Device gobject class, showing off all the Device methods we have overriden. http://tinyurl.com/537awj nm-dbus-nm.c [2] contains: * The construction and implemenation of the D-Bus interface used by Sugar for /device activation/ (associating with networks) radio discipline. http://tinyurl.com/3fcabp, http://tinyurl.com/3ozy7n More details to come, Michael [1]: http://dev.laptop.org/git?p=users/mstone/NetworkManager;a=blob;f=src/nm-device-802-11-mesh-olpc.c;h=7c0808a77513d8f8d2f3029b6bb6d390ee370027;hb=olpc-0.6 [2]: http://dev.laptop.org/git?p=users/mstone/NetworkManager;a=blob;f=src/nm-dbus-nm.c;h=06694d625949f316ef3b4bdec1a71bb2f1ffb3a2;hb=olpc-0.6 _______________________________________________ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel