Active Antenna Persistent Configuration: Difference between revisions

From OLPC
Jump to navigation Jump to search
(New page: The following persistent parameters can be set on a standalone module (active antenna): Note: if you cannot find the /sys pseudo files listed bellow you probably need to update your module...)
 
m (categorize)
 
(One intermediate revision by one other user not shown)
Line 1: Line 1:
<noinclude>{{OLPC}}[[Category:Network]]</noinclude>
The following persistent parameters can be set on a standalone module (active antenna):

Note: if you cannot find the /sys pseudo files listed bellow you probably need to update your module, check [http://wiki.laptop.org/go/Active_Antenna_Reprogramming this page]
The following persistent parameters can be set on a standalone module (active antenna): [Note: if you cannot find the /sys pseudo files listed bellow you probably need to update your module, check [[Active_Antenna_Reprogramming |this page]]]


* bootflag - each module can store two copies of the firmware, this flag sets which one should be used to boot the module
* bootflag - each module can store two copies of the firmware, this flag sets which one should be used to boot the module
* boottime - the time (in seconds) the module will wait for the host to send it a firmware, before loading the firmware version stored on its flash
* boottime - the time (in seconds) the module will wait for the host to upload a firmware. After this time, the module will load the firmware stored in its flash
* channel - in what channel should the module operate (0 means do not operate in standalone mode)
* channel - in what channel should the module operate (0 means do not operate in standalone mode)
* capability -
* capability -

Latest revision as of 17:33, 14 September 2011

  This page is monitored by the OLPC team.

The following persistent parameters can be set on a standalone module (active antenna): [Note: if you cannot find the /sys pseudo files listed bellow you probably need to update your module, check this page]

  • bootflag - each module can store two copies of the firmware, this flag sets which one should be used to boot the module
  • boottime - the time (in seconds) the module will wait for the host to upload a firmware. After this time, the module will load the firmware stored in its flash
  • channel - in what channel should the module operate (0 means do not operate in standalone mode)
  • capability -
  • mesh_id - the mesh ssid
  • metric_id, protocol_id - the metric and protocol in use on the mesh (currently there is only option 0)

In order to set any of these parameters, you should simply write to the appropriate file in the tree bellow.

/sys/class/net/<inteface>...
              |-- boot_options
              |   |-- bootflag
              |   |-- boottime
              |   `-- channel
              ...
              |-- mesh_ie
              |   |-- capability
              |   |-- mesh_id
              |   |-- metric_id
              |   `-- protocol_id

Example - Set the channel to 6 in a standalone module in msh1:

echo 6 > /sys/class/net/msh1/boot_options/channel