<br><font size=2 face="sans-serif">Dan,</font>
<br>
<br><font size=2 face="sans-serif">Marvell and Cozybit "give"
us firmware by posting it in the internal Wiki.</font>
<br>
<br><font size=2 face="sans-serif">M.</font>
<br>
<br>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>Dan Williams <dcbw@redhat.com></b>
</font>
<p><font size=1 face="sans-serif">07/02/2007 07:06 AM</font>
<td width=59%>
<table width=100%>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td><font size=1 face="sans-serif">Ronak Chokshi <rchokshi@marvell.com></font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td><font size=1 face="sans-serif">Michail Bletsas <mbletsas@laptop.org>,
testing@laptop.org, Kim Quirk <kim.quirk@gmail.com>, "OLPC Developer's
List" <devel@laptop.org>, testing-bounces@lists.laptop.org</font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td><font size=1 face="sans-serif">RE: [Testing] Build 472 - testing</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><tt><font size=2>On Sun, 2007-07-01 at 10:15 -0700, Ronak Chokshi wrote:<br>
> True. Please treat our suggestions of builds only as recommendations.<br>
> The final decision of which build should be used for the major<br>
> milestones should come from within OLPC based on the accomplishments<br>
> planned for that milestone. This is the model we usually follow with<br>
> most of our other customers/projects as well.<br>
<br>
Ok, I was under the impression that we had to get sign-off for any<br>
CozyBit built firmware before CozyBit could give it to us, before we<br>
could put it in builds. Is that invalid, or has that changed?<br>
<br>
Dan<br>
<br>
> <br>
> <br>
> Thanks<br>
> <br>
> Ronak<br>
> <br>
> <br>
>
<br>
> ______________________________________________________________________<br>
> From:testing-bounces@lists.laptop.org<br>
> [mailto:testing-bounces@lists.laptop.org] On Behalf Of Michail Bletsas<br>
> Sent: Sunday, July 01, 2007 6:11 AM<br>
> To: Dan Williams<br>
> Cc: testing@laptop.org; Kim Quirk; OLPC Developer's List;<br>
> testing-bounces@lists.laptop.org<br>
> Subject: Re: [Testing] Build 472 - testing<br>
> <br>
> <br>
> <br>
> <br>
> <br>
> No we don't.... <br>
> <br>
> M. <br>
> <br>
> <br>
> <br>
> <br>
> <br>
> Dan Williams <dcbw@redhat.com> <br>
> Sent by:<br>
> testing-bounces@lists.laptop.org <br>
> <br>
> 06/30/2007 11:37 PM <br>
> <br>
> <br>
> To<br>
> <br>
> <br>
> Kim Quirk<br>
> <kim.quirk@gmail.com> <br>
> <br>
> <br>
> cc<br>
> <br>
> <br>
> testing@laptop.org, "OLPC Developer's List" <devel@laptop.org>
<br>
> <br>
> <br>
> Subject<br>
> <br>
> <br>
> Re: [Testing]<br>
> Build 472 -<br>
> testing<br>
> <br>
> <br>
> <br>
> <br>
> <br>
> <br>
> <br>
> <br>
> <br>
> <br>
> <br>
> <br>
> <br>
> <br>
> <br>
> <br>
> On Sat, 2007-06-30 at 08:10 -0400, Kim Quirk wrote:<br>
> > It looks like we may need/want to get the latest Marvell firmware<br>
> and<br>
> > all known flag day updates into the build on Monday (if possible).<br>
> At<br>
> > some point we just have to take the hit and ask everyone to upgrade,<br>
> > laptops and servers. <br>
> > <br>
> > As you mention, Dan, we need to do this in Cambridge first...
so<br>
> maybe<br>
> > this should be in Monday's build. I know we have the Marvell<br>
> firmware<br>
> > (or can get it). Is there anything outstanding that we are still<br>
> > waiting on to have this flag day? <br>
> <br>
> We need to get Ronak's sign-off on any firmware that we plan to put
in<br>
> public builds. That can take a few days, though sometimes it's
quick.<br>
> <br>
> Dan<br>
> <br>
> <br>
> > Is there a reason NOT to do this as soon as possible?<br>
> > <br>
> > Thanks,<br>
> > Kim<br>
> > <br>
> > On 6/30/07, Dan Williams <dcbw@redhat.com> wrote:<br>
> > On Fri, 2007-06-29 at 21:37 -0400,
John (J5) Palmieri wrote:<br>
> > > On Fri, 2007-06-29 at 11:23
-0400, Kim Quirk wrote: <br>
> > > > Test Groups,<br>
> > > > Build 472 is available,
but the biggest problem is that<br>
> it<br>
> > doesn't get<br>
> > > > on the mesh or infrastructure
AP. Some activities are<br>
> > working and<br>
> > > > there is more to see in
the Journal than the previous<br>
> > build. <br>
> > > ><br>
> > > > I'm hoping that we can
get another build today with the<br>
> > network<br>
> > > > problem fixed since that
would be important for our<br>
> > 'Release Candidate<br>
> > > > 1'. Today's milestone is
to get to RC1 which has most of<br>
> > the basic <br>
> > > > functionality that was
available in 406 builds. If we<br>
> can<br>
> > get the mesh<br>
> > > > connecting again, that
would be great!<br>
> > > ><br>
> > > > Test release notes:<br>
> > http://wiki.laptop.org/go/Test_Group_Release_Notes<br>
> > > > (Anyone can add notes about
this release page -- please<br>
> > do)<br>
> > ><br>
> > > I couldn't fix the mesh issues
with the current<br>
> > NetworkManager so I have<br>
> > > backtracked to an earlier working
version in build478.<br>
> This<br>
> > one gets on<br>
> > > the mesh and also on AP points.<br>
> > ><br>
> > ><br>
> ><br>
> http://olpc.download.redhat.com/olpc/streams/development/build478/<br>
> > <br>
> > So thinking about it again, we don't
expect the new svn2621<br>
> NM<br>
> > bits to<br>
> > work with any existing mesh networks
because the server<br>
> > software and<br>
> > hardware needs to change.<br>
> > <br>
> > We have to have a flag day in Cambridge
too before we can<br>
> get<br>
> > the new NM <br>
> > automeshing bits, because the new
bits aren't compatible<br>
> with<br>
> > the old<br>
> > bits on the server side.<br>
> > <br>
> > Dan<br>
> > <br>
> > <br>
> > <br>
> <br>
> _______________________________________________<br>
> Testing mailing list<br>
> Testing@lists.laptop.org<br>
> http://lists.laptop.org/listinfo/testing<br>
> <br>
> <br>
> <br>
> <br>
<br>
</font></tt>
<br>