Dear David,
I do not have the background on developing embedded systems; I started to
learn nesC half a year ago for research purpose.
Do you mean that some commands in avr library that manipulate memory-mapped
I/O will enable interrupts as a side effect? If so, could you give me some
concrete examples (I just learned that the "sei" macro in avr library can
enable interrupts)? Will these commands/macros be frequently used by
\textbf{application} developers in real applications?
Best regards,
Yours,
Zhifeng Lai
-----Original Message-----
From: David Gay [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 10, 2007 12:29 AM
To: Zhifeng Lai
Cc: tinyos help; Philip Levis; Zhifeng Lai
Subject: Re: [Tinyos-help] Some confusion on the classic nesC paper.
On 7/9/07, David Gay <[EMAIL PROTECTED]> wrote:
> On 7/6/07, Zhifeng Lai <[EMAIL PROTECTED]> wrote:
> > Dear David,
> >
> > Thanks for your reply!
> >
> > With regard to the second question, if we disallow programmers to use
> > assembly code and assume ncc can perform global and inter-procedural
alias
> > analysis, can we safely conclude my aforementioned claim (programmers
will
> > not raise data races if they obey the race-free invariant)?
>
> Yes (well, mostly - you could still run into weirdness with
> memory-mapped I/O, e.g., DMA - you'd want to prevent that in
> application-level code too, on some platforms at least...)
Another example: the status register with the interrupt-enable bit (in
fact, all registers) on the avr architecture is memory-mapped...
David Gay
_______________________________________________
Tinyos-help mailing list
[email protected]
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
