Changes between Version 37 and Version 38 of Internal/NewNodeAgent

Timestamp:

May 13, 2015, 4:44:16 PM (9 years ago)

Author:

ssugrim

Comment:

—

Internal/NewNodeAgent

@@ -9 +9 @@
  * timeout
 
+----
+''' TODOS: '''
+ * Agent Commands should have a scan method that reports back to the controller. It should call the respective scan method of the driver.
+ * For completeness we can move the scan method functionality down the the device.rb level. At that context it will raise an exception.
+ * In the Ethernet context, it will return a string that says "Why are you trying to scan with ethernet?"
+ * What other configure directives should wimiax/LTE repspond to beside network name.
 
 ----
@@ -388 +394 @@
   * isConnected
  * Wimax:
+  * isUp
   * isActive
-  * ?
+  * isStarted
+  * isConnected
 
 ----
@@ -397 +405 @@
 
 Each indivdual driver will have to know about this problem and handle it if needed. The specific case is iwldvm for iwlwifi. The logic here will be to load iwlwifi and then check if iwldvm is loaded. If it is, when a call to unload is made, we must unload iwldvm first. 
+
+This is handled by overriding the activate and deactivate methods. In activate, it calls the super() and then checks for the respective module. In deactivate it unloads the respective module and then calls super. 
+
+There may still be a degeneracy where calling 'modprobe -r iwldvm' removes the iwlwifi module, which may cause the kmodule state model to become inconsistent. 
+
+----
+
+A little background on iwldvm. It's apparently a firmware compatibility module that provides an interface to iwlwifi. According to the comments on  [http://lxr.free-electrons.com/source/drivers/net/wireless/iwlwifi/Kconfig this] doc, one can either run iwldvm or IWLMVM. Both are compatiblity layers but all the commands funnel through iwlwifi. That said then, as far as command capability with iw, as long as one of those modules is present (or baked into the kernel), the iw command feature set should be available.