Follow-up Comment #6, bug #30363 (project avr-libc):
Bill Perry's patch doesn't define the following cases:
1. The maximum delay that can be provided in _ms.
With the new implementation, the values change. If delay_ms() is considered,
maximum delay that can be provided is:
_ms = (2^32-1)*(10^-3) /F_CPU in MHz
= 4294967.295
(Note that the maximum value that can be given to
__builtin_avr_delay_cycles() is 0xFFFF FFFF )
If the requested delay is greater than the above value in milli seconds, can
the approach be similar to earlier one where the resolution is decreased to
1/10 ms?
2. Similarly maximum delay that can be provided in _us. (Resolution is not
decreased in this case, but delay_ms will be called for values greater than
(2^32-1)/F_CPU)
Comments... ?
_______________________________________________________
Reply to this item at:
<http://savannah.nongnu.org/bugs/?30363>
_______________________________________________
Message sent via/by Savannah
http://savannah.nongnu.org/
_______________________________________________
AVR-libc-dev mailing list
AVR-libc-dev@nongnu.org
http://lists.nongnu.org/mailman/listinfo/avr-libc-dev
