Meshing while suspended
dcbw at redhat.com
Wed May 9 10:57:39 EDT 2007
On Wed, 2007-05-09 at 10:16 -0400, Jim Gettys wrote:
> It will also require upgrading the Boot2 code in the wireless module to
> 3107, IIRC.
Probably not, actually; the Boot2 is pretty independent of the RAM-load
firmware. The Boot2 historically screwed us only with USB interactions
with the 5536, making it unable to accept firmware uploads at boot time
or to even enumerate on the USB bus. 3107 should fix most of those USB
things, and has a much safer Boot2 update implementation (ie, you can
actually tell when it's done writing the new bits to the SPI flash,
which you couldn't < 3107, you just had to wait 30s).
> Dan, is this right?
> - Jim
> On Wed, 2007-05-09 at 22:05 +1000, James Cameron wrote:
> > On Tue, May 08, 2007 at 01:20:27PM -0700, Javier Cardona wrote:
> > > The latest wireless firmware (5.220.11p4) implements mesh autonomous
> > > mode: the wireless interface will continue to participate in the mesh
> > > while the main CPU is suspended to RAM.
> > Excellent, my testing process can use this. What OS build is this
> > version in, or if not yet in a build, how can I obtain and use it?
> > I searched the Wiki. http://wiki.laptop.org/go/Wireless seems to list a
> > version, but it is quite old.
More information about the Devel