[Tinyos-host-mote-wg] [Tinyos-2.0wg] Re: atomic warnings

[David Gay]

On 6/21/05, Joe Polastre <joe.polastre at gmail.com> wrote:
> So should we be putting an atomic{} block around the init and start functions?

I'm tempted to say there should be one around init and hardwareInit,
as start may be called from elsewhere with interrupts enabled anyway
(so I'd also move the __nesc_enable_interrupt up to after init).

For 2.x, I think this means that there's an atomic up to just before
the booted event.

Comments?

For the 2.x folks: the question is:
- what parts of the boot sequence should be run with interrupts
disabled (currently it's init+start in 1.x, and just the scheduler in
2.x)
- making sure that nesC is aware of this (currently nesC assumes that
all the boot sequence runs with interrupts enabled, except in alpha10
where a bug makes it assume it all runs with interrupts disabled)

David

_______________________________________________
Tinyos-2.0wg mailing list
Tinyos-2.0wg at Mail.Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-2.0wg