#5144 HIGH 8.2.0 (: [firmware] Marvell firmware should default to mesh off, and have controls for turning mesh on and off

[Zarro Boogs per Child]

#5144: [firmware] Marvell firmware should default to mesh off, and have controls
for turning mesh on and off
-------------------------+--------------------------------------------------
   Reporter:  jg         |       Owner:  rchokshi            
       Type:  defect     |      Status:  new                 
   Priority:  high       |   Milestone:  8.2.0 (was Update.2)
  Component:  wireless   |     Version:                      
 Resolution:             |    Keywords:  blocks?:8.2.0       
Next_action:  never set  |    Verified:  0                   
  Blockedby:             |    Blocking:  7879                
-------------------------+--------------------------------------------------

Comment(by dsaxena):

 Replying to [comment:17 mbletsas]:
 > Deepak,
 >
 > By design, the mesh forwarding engine always runs, regardless of the
 status of the kernel networking device. So when you issue an "ifconfig
 msh0 down" command, all that you are doing is telling the host to stop
 using the mesh interface and not to turn off the mesh forwarding engine in
 the firmware.
 >
 > In general, this seems to confuse the hell out of linux people
 conceptually, since they believe that ifconfig should really turn things
 on and off. In our case msh0 is only the means by which the host
 communicates with the communications processor on the wireless subsystem
 and the linux kernel interface semantics are just not enough for the host
 processor to exercise control over its partner.

 Thanks for the clarification. Makes much more sense now.

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