[Sugar-devel] Wanting to know a bit of (NetworkManager) workflow upon resume-from-suspend

[Paul Fox]

sascha wrote:
 > 
 > > i've cherry-picked 65a5f2b3 onto olpc-2.6.35, and the autobuilder
 > > did the rest.  this implements a new "libertas_disablemesh" module
 > > parameter which should keep mesh from being enabled.  please test:
 > >
 > >     http://rpmdropbox.laptop.org/f14-xo1/kernel-2.6.35.13_xo1-20120502.1603.olpc.bde819f.i586.rpm
 > 
 > Thanks! Just to be sure: as it's been merged into olpc-2.6.35, all
 > future official 2.6.35 based OLPC kernel builds will include this patch?

hi sascha -- 

yes.  i think we hope there won't actually be any more of those, but
if there are, that patch will be there.  current and future releases
get the patch for free, since it's upstream.  (thank you)

paul

p.s.  somehow the git hash i pasted above is incorrect.  the correct
cherry-pick was this one:
---------
 commit 6bdbdbf4a151a3a1333818cd17a7d7795e936041
 Author: Sascha Silbe <silbe at activitycentral.com>
 Date:   Wed May 11 14:52:34 2011 +0200

    libertas: Add libertas_disablemesh module parameter to disable mesh 
interface
    
    This allows individual users and deployments to disable mesh support at
    runtime, i.e. without having to build and maintain a custom kernel.
    
    Based on a patch by Paul Fox <pgf at laptop.org>.
    Signed-off-by: Sascha Silbe <silbe at activitycentral.com>
    Signed-off-by: John W. Linville <linville at tuxdriver.com>
---------


 > 
 > The reason we've not gone the module parameter route so far (in
 > Dextrose 3) is that we didn't want to divert from upstream (OLPC in this
 > case) on the kernel level. If it's included now, that concern is
 > addressed and we can go this route, which IMO is technically the best
 > option. It avoids all possible race conditions and only needs a single
 > configuration file to be set up.
 > 
 > Sascha
 > 
 > -- 
 > http://sascha.silbe.org/
 > http://www.infra-silbe.de/

=---------------------
 paul fox, pgf at laptop.org