#4616 NORM Update.: Mesh doesn't resume from suspend on reciept of multicast packets

[Zarro Boogs per Child]

#4616: Mesh doesn't resume from suspend on reciept of multicast packets
----------------------------------+-----------------------------------------
  Reporter:  gnu                  |       Owner:  cjb                              
      Type:  defect               |      Status:  new                              
  Priority:  normal               |   Milestone:  Update.1                         
 Component:  power manager (OHM)  |     Version:  Development build as of this date
Resolution:                       |    Keywords:                                   
  Verified:  0                    |  
----------------------------------+-----------------------------------------

Comment(by gnu):

 Why is "the wakeup behavior" any different from "standard 802.x
 functions"?  The chip should not do a CPU wakeup unless it has an
 interrupt to present to the host.  So, normal interrupt masking should be
 all the CPU needs to set up in advance, to determine which possible events
 will cause a wakeup.  And there should already be ways for the CPU to tell
 the chip "don't interrupt me about multicasts, except ones addressed to
 these addresses".

 This seems like a no-brainer to me, why is it so hard to get across?

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