<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>On 16/02/2020 00:25, Chris Johns wrote:<br>
</p>
<blockquote type="cite"
cite="mid:4dc4a2fd-6c4d-7d27-80ff-b86913ca17c4@rtems.org">On
2020-02-15 03:02, Sebastian Huber wrote:
<br>
<blockquote type="cite" style="color: #000000;">Move the
microseconds per tick configuration constant out of the
<br>
configuration table.
<br>
</blockquote>
</blockquote>
This is necessary to split up the confdefs.h file in easier to
review pieces.<br>
<blockquote type="cite"
cite="mid:4dc4a2fd-6c4d-7d27-80ff-b86913ca17c4@rtems.org">
<blockquote type="cite" style="color: #000000;">
<br>
Add WATCHDOG_MICROSECONDS_PER_TICK_DEFAULT and use it to provide
a
<br>
default definition of the watchdog ticks constants.
<br>
</blockquote>
</blockquote>
The benefit is that the application configuration object file will
only include data structures which have a user-defined value. After
reading this again, I think this part of the patch makes no sense,
since most users define this to option to 1000.<br>
<blockquote type="cite"
cite="mid:4dc4a2fd-6c4d-7d27-80ff-b86913ca17c4@rtems.org">
<br>
What is the purpose and/or use for this change?
</blockquote>
</body>
</html>