#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):

 Some more information in regards to the WLAN Firmware specification v5.1:

 {{{
 The following is based on firmware specification v 5.1 Doc MV-S 103752-00


 COMMANDS NOT SUPPORTED
 ----------------------
 1. [page 25]
 Per packet transmission rate will not work in mesh mode due to the fact
 that
    mesh mode rate adaption overrides TxControl per packet rate field.

 2. [page 33 ]
  buildModes_HIF_SPI  is not supported.

 3. [page  52]
 CMD_802_11_BG_SCAN_CONFIG
 CMD_802_11_BG_SCAN_QUERY

 4. [page 59]
 CMD_802_11_ASSOCIATE

 5. [page 70]
 rate adaptation commands are not supported for per peer MPs in mesh mode.

 6. [p 73]
 Transmit power control is not supported on per packet/peer basis.

 7. [p 87]
 CMD_802_11_FW_WAKE_METHOD

 8. [p 86]
 CMD_802_11_WAKEUP_CONFIRM

 9
 CMD_802_11_PS_MODE

 10 [p 91]
 CMD_802_11_DEEP_SLEEP

 11. [p 97]
 CMD_802_11_BCA_CONFIG_TIMESHARE

 12. [p 106]
 DFS (Dynamic frequency selection) 802.11h is not supported.



 NEW MESH COMMANDS
 ------------------
  - host_CMD_802_11_HOSTSLEEP_ACTIVE (code 0x0045) added as part of
 enhanced host
    sleep. Host gets a confirmation from the firmware

  - {set,get}_rreq_costs "cost54 cost36 cost11 cost1"
        Specify the link cost at each rate. Setting a specific cost to
        0 will disable transmitting a RREQ at that rate.

  - mesh_{set,get}bcast_r <n>
        Sets the rate for mesh broadcast data frames. Index <n> is the rate
        index (same as for rateadapt command, see driver README). Without
        arguments, shows the current rate.

  - {set,get}_rreq_delay <ms>
        Sets the delay in ms between the moment an RREQ is
        received and the moment it is forwarded or answered. Without
        arguments, it shows the current delay.

  - {set,get}_route_expiration <s>
        Sets the route expiration times, in seconds. When expired,
        a route will be refreshed.

   --- monitor mode operation
   echo mode > /sys/class/net/{ethX,mshX}/device/libertas_rtap

    where mode is the hex mask that specifies which frames to sniff (in
 short, 0x1 for data, 0x2 for all management but beacons, 0x4 for beacons).
 Any non zero mode will activate the monitor mode, inhibiting transmission
 in ethX and mshX interfaces and routing all the traffic to a new rtapX
 interface that will output the packets in 802.11+radiotap headers format.
    CMD_802_11_SNIFFER_MODE

   --- Support for 32 anycast addresses for MPP operation.
 Support for up to 32 anycast addresses substituting former MPP_ANYCAST
 address. The anycast address range is C0:27:C0:27:C0:XX where XX goes from
 00 to 1F (or 0 to 31 in dec). The value to write on anycast_mask will
 specify which addresses the device listens to. Bits in a 32 bit int are
 numbered from 0 (least significant bit) to 31. A specific address ending
 in YY will be listened to if bit YY in the value is set to one. Examples:

 0x00000000 : do not listen to any anycast address 0xFFFFFFFF : listen to
 every anycast address from :00 to :1F
 0x00000013 : listen to anycast addresses :00, :01 and :04


 Mesh autostart control: Allows to enable or disable the mesh autostart
 feature. It can be configured with  # echo Z >
 /sys/class/net/mshX/autostart_enabled

 where Z is zero to disable the autostart and non-zero to enable it.
 It is enabled by default. To support this, two new mesh_access
 subcommands, mesh_{set,get}_autostart_enabled (0x14 and 0x15).


 -- - Mesh TTL
 firmware side integrated (based on previous Sailendra Govardhan work)

 Support for per-packet mesh TTL in firmware. The patch was based on
 Sailendra's work but was modified to work better with Javier driver patch.
 It will only look for the mesh TTL on the frame coming from the host if
 the TxPacketOffset indicates that the mesh header part of the wcb_t
 structure was filled at the driver. Otherwise it will use the default mesh
 TTL. This is important as offers complete backwards compatibility with
 previous drivers.

 --- New SET_BOOT2_VER commands (for OLPC ticket #1694)


 NEW EVENTS
 -----------

 1. MESH_AUTO_STARTED (23)


 OTHER CHANGES
 -------------
 1. [page 25]
 TxControl in TxPD does not define control bit for mesh interface.

 2. [p22]
  RxControl In RxPD does not define control bit for mesh frames
 }}}

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