Agreed, but what do you propose as an alternative then? The only one I see is potentially exporting a new interface that a user can wire to that lets them decide what should be done in the case of a failure. Or maybe run in the loop a fixed number of times before giving up and passing through as if it had suceeded (possibly also signaling an event of some sort taht something went terribly wrong).
Kevin On Thu, May 1, 2008 at 12:59 PM, Philip Levis <[EMAIL PROTECTED]> wrote: > > On May 1, 2008, at 12:03 PM, Kevin Klues wrote: > > > As the code currently is, you're right, if start or stop ever fails, > > then there is a chance for lock up. Doing a task repost after > > checking return conditions shuld fix this problem. As you say though, > > if FAIL is returned indefinitely, then the task will be reposted > > forever, but then again you've got other problems if FAIL is > > perpetually being returned when trying to start or stop a device..... > > I'll check in the fix. > > > > I don't think a spinning task loop is a good fix; it means that if a driver > ever fails, the MCU will not enter a low power state. > > Phil > -- ~Kevin _______________________________________________ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
