It was an early decision of the Core WG that we will keep the chip directory flat until we have enough clutter there that would necessitate a hierarchical model like we have for the platforms (with the .family). So currently this should be handled in the same way as atm128/atm1281, i.e. with a new msp430X subdir in parallel to the msp430. A platform can then cherry pick chip abstractions and regulate the shadowing in its .platform file.
Vlado On Thu, Oct 15, 2009 at 23:31, Eric Decker <[email protected]> wrote: > > With the advent of the 26xx and 54xx series chips there are a number of > differences and not everything falls cleanly under the umbrella of the > msp430 structure. > > How should this get handled? > > Does the way it is done in the dexma code (contrib/dexma/tos/chips/msp430X) > take care of it? > > Basically they define pieces of the msp430 as chunks and each chunk shows > up. This forces > the developer to understand what pieces get pulled in by the platform. > > My concern though is how much of this propagates though the rest of the > system. The chip/processor > dependent stuff should all get invoked via the platform files. Not sure if > that is the case. > > thoughts? > > -- > Eric B. Decker > Senior (over 50 :-) Researcher > > >
_______________________________________________ Tinyos-help mailing list [email protected] https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
