<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>On 16/02/2020 00:36, Chris Johns wrote:<br>
</p>
<blockquote type="cite"
cite="mid:cfad10dc-5f5e-505a-e083-595d6cc7db34@rtems.org">On
2020-02-15 03:02, Sebastian Huber wrote:
<br>
<blockquote type="cite" style="color: #000000;">Move the idle
thread body configuration constant out of the
<br>
configuration table.
<br>
<br>
Provide a default definition of the idle thread body constant.
<br>
</blockquote>
<br>
May be I am missing something simple here. How would I provide an
custom IDLE task? Is it by providing something like ...
<br>
<br>
#include <rtems/score/threadidledata.h>
<br>
<br>
const Thread_Idle_body _Thread_Idle_body = My_Idle_body;
</blockquote>
<p>No, definitely not. An application designer should use the
documented API:</p>
<p><a class="moz-txt-link-freetext" href="https://docs.rtems.org/branches/master/c-user/configuring_a_system.html#configure-idle-task-body">https://docs.rtems.org/branches/master/c-user/configuring_a_system.html#configure-idle-task-body</a></p>
<p>The goal of this and follow up change sets is to split this 3k
LOC file (confdefs.h) in easier to review pieces.</p>
<p>The file contains also comments which should be in the Classic
API Guide, e.g. how to configure the filesystems:</p>
<p><a class="moz-txt-link-freetext" href="https://docs.rtems.org/branches/master/c-user/configuring_a_system.html#file-system-configuration-parameters">https://docs.rtems.org/branches/master/c-user/configuring_a_system.html#file-system-configuration-parameters</a></p>
<p>This is just an enumeration of the options. The user has no idea
how things are related after reading this section.<br>
</p>
</body>
</html>