[net2-wg] Deluge T2 snapshot

Razvan Musaloiu-E. razvanm at cs.jhu.edu
Thu May 17 01:13:26 PDT 2007


Hi!

I sent first a snapshot because I wanted some feedback before the commit 
phase. :P I put some things in slightly different places. The meeting 
notes says that everything should go to tos/lib/net/deluge but to me it 
doesn't really make sense to be like that. Here is a quick roadmap of the 
code from snapshot:
- tos/lib/net/deluge contains the dissemination code. ObjectTransferC is
   the frontend to that.
- tos/lib/deluge contains the DelugeC component. Also here is
   DelugeStorageC, a component that takes care of multiplexing the access
   to the flash volumes and SerialStarterC, a component we use to
   start the serial upon boot.
- tos/lib/deluge/TOSBoot contains the TOSBoot port from T1. Only the
   telosb part is included for now.
- tos/lib/deluge/VolumeManager is a component that we are using to
   read/write flash volumes over the serial port. I'm almost certain
   that David Moss has in contrib a replacement for this but we didn't have
   time try it.
- tos/lib/deluge/extra contains the code to access the internal flash
   and reboot the telosb. I think Prabal has the replacement code for this
   but it was not commited yet so that's why I put it in this directory.

Is this OK with everyone? :P

And a quick question: can I go ahead and add the bnp.extra? It's something 
that it's needed in order to keep the Makefiles simple for our examples. :-)

A nice evening to everyone!
Razvan ME

On Wed, 16 May 2007, Philip Levis wrote:

> On May 16, 2007, at 11:20 PM, Omprakash Gnawali wrote:
>
>> 
>> It will be great if you just put it in the CVS. You can refer to the
>> meeting notes from last week for destinations of various files.
>> 
>
> Sounds like a good idea to me.
>
> The best way to get people testing the code is to put it in CVS. Now that 
> TinyOS releases are reasonably frequent and stable, not that many users 
> operate directly from CVS. Since we can filter file lists when building a 
> release, there's no reason to not drop it in there.
>
> Phil


More information about the net2-wg mailing list