#2177 BLOC Trial-2: Need a document describing supported firmware features

[Zarro Boogs per Child]

#2177: Need a document describing supported firmware features
-----------------------+----------------------------------------------------
  Reporter:  dcbw      |       Owner:  rchokshi
      Type:  defect    |      Status:  new     
  Priority:  blocker   |   Milestone:  Trial-2 
 Component:  wireless  |     Version:          
Resolution:            |    Keywords:          
  Verified:  0         |  
-----------------------+----------------------------------------------------
Comment (by rchokshi):

 Further information regarding features incorporated and tested as part of
 the wireless system:

 {{{
 List of features supported and verified:

 Core 802.11abg client (infra mode, adhoc mode)
 Marvell mesh support
 WPA in infra mode
 WEP, TKIP and AES encryption
 USB host i/f
 Enhanced host sleep
 Linux 2.6 only
 Monitor/Sniffer mode

 Mesh features:
 Marvell Mesh routing which is similar to IEEE 802.11s D1.05 HWMP routing
 protocol.
 Mesh auto start feature, when there is no association for a given time;
 this feature can be disabled or enabled from the host.
 Mesh basic rate adaptation for data frames based on route discovery.
 However, this rate adaptation mechanism uses same rate for the entire link
 lifetime –no periodic or dynamic rate adjustment after frame exchange. For
 a given link its data rate is derived at the time of route discovery.
 Support for configuring mesh default TTL for mesh data and RREQ frames.
 Support for mesh per packet TTL.
 Monitor mode operation, which allows all frames, except 802.11 control
 frames, to be received at the host.
 Enhanced host sleep mode.
 Support for Mesh Port Point MPP. Support for 32 anycast address for MPP.
 MAC Address C0:27:C0:27:C0:[00-1f] are reserved for anycast addresses.
 Mesh Beacon and probe response containing Marvell mesh IE.
 Mesh visual indicator: LED1 On if associated to infra AP or mesh
 join/start. LED2 blinks with frames rx/tx.
 Blinding table feature to setup the desired multi-hop topologies.
 APIs to monitor or change mesh mode operation. This include APIs to
 1) get/set mesh routing table
 2) get/set mesh neighbour
 3) get/set link cost
 4) get/set blinding table
 5) get/set RREQ broadcast rate.
 6) get mesh stats (total forwarded packet, dropped packet, received, tx
 error etc.)
 7) get/set mesh default TTL
 8) get/set mesh route properties
 9) get/set mesh auto start enable/disable
 10) get/set monitor mode
 }}}

-- 
Ticket URL: <https://dev.laptop.org/ticket/2177#comment:7>
One Laptop Per Child <http://laptop.org/>