On 8/28/06, R. Steve McKown <[EMAIL PROTECTED]> wrote:
On Monday 28 August 2006 16:53, David Gay wrote:
> On 8/28/06, R. Steve McKown <[EMAIL PROTECTED]> wrote:
> > So shouldn't then TEP 103 specify data integrity requirements? [snip]
>
> [snip]
> A reasonable compromise might be that read is guaranteed to return
> valid data.
I'd love to see the spec guarantee that read returns valid data. Are you
envisioning a read returns a len of 0 on bad data or end of log? This seems
to fit nicely with the implementation of at45db, where bad data on a page and
end of log conditions are generally synonymous.
I'm simply envisioning that it's guaranteed (well, within the bounds
provided by simple error detection codes) not to return invalid data.
It's actual behaviour on invalid data would be left unspecified (skip,
think it's end of log, whatever - we might want to guarantee that it
does return at least, though).
David
_______________________________________________
Tinyos-help mailing list
[email protected]
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
