[Tinyos Core WG] Boot Order

[Philip Levis]

On May 22, 2008, at 7:04 AM, David Moss wrote:
> I understand the TEP, but if a driver is implemented with  
> interrupts, it
> would require modification to the driver or a custom driver to make  
> it work
> before the interrupts are enabled.
>
> It would be easier not to think about it by having the option to  
> access
> higher or lower priority Boot interfaces.
>
> It also sounds like other people have experienced this limitation  
> and fixed
> it with custom solutions.

I don't understand; most drivers will of course be implemented with  
interrupts. The point is that driver initialization (Init.init()) is  
the one place in TinyOS where you can block. Trying to handle  
interrupts in Booted() isn't possible, unless you manually string the  
continuations along. Or is the issue that drivers have already been  
implemented in this way and changing them is a pain? I'm leery of  
changing the boot sequence to support something which the boot  
sequence can already achieve.

Phil