> But the msp430 used in the tmote sky is limited to 48KB, so there's > really really really little space left. Insufficent space for my > application as i have already an .text overflow of 500 bytes with much > features missing i do have to implement.
Yep. While we often peter to think in orders of magnitude, in this space there is a simple "does fit/doesn't fit" dichotomy. You can always optimize and shift the boundaries by a few dozens of percent, but given the pre-existing complexity of the protocols we are using, in the end the classes defined in the lwig guidance document *are* representing a useful step function of functionality. (The tmote is at the bottom end of class 1, that's why you hear the crunching sound.) Grüße, Carsten _______________________________________________ Lwip mailing list [email protected] https://www.ietf.org/mailman/listinfo/lwip
