#5461 NORM Never A: Strange command response from 5.110.20.p47 firmware

[Zarro Boogs per Child]

#5461: Strange command response from 5.110.20.p47 firmware
-----------------------+----------------------------------------------------
  Reporter:  dwmw2     |       Owner:  mbletsas      
      Type:  defect    |      Status:  new           
  Priority:  normal    |   Milestone:  Never Assigned
 Component:  wireless  |     Version:                
Resolution:            |    Keywords:                
  Verified:  0         |  
-----------------------+----------------------------------------------------

Comment(by ashish):

 This is may be due to mesh auto start enable command that starts ad-hoc
 network.
 Here is possible explanation.
 In the firmware we process one command at a time. During this time if a
 command is received from the driver, firmware ignores received command and
 notify driver by returning BUSY. Now when firmware receives mesh autostart
 enable command it sends back cmd response to the driver --to allow further
 command-- and then waits for ~5s after that fires up ad-hoc start
 internally. Lets say at this time firmware was processing scan command,
 which generally takes more time to finish, and it receives ad-hoc start
 (triggered by mesh auto start enable), it ignores this command and returns
 0x8002b.
 There are two solutions.
 1. Mesh is always on, so driver should not send mesh auto start enable.
 2. If driver is sending mesh auto start enable, firmware should take care
 of this problem describes above --need firmware fix.
 If we choose option 1 nothing to worry.

-- 
Ticket URL: <http://dev.laptop.org/ticket/5461#comment:4>
One Laptop Per Child <http://dev.laptop.org>
OLPC bug tracking system