<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>On 31/03/2020 10:14, Chris Johns wrote:<br>
</p>
<blockquote type="cite"
cite="mid:e8ae8c91-9f35-0e97-8adc-82c3483a83a6@rtems.org">On
2020-03-31 00:51, Joel Sherrill wrote:
<br>
<blockquote type="cite" style="color: #000000;">On Mon, Mar 30,
2020 at 8:39 AM Sebastian Huber <<a
class="moz-txt-link-abbreviated"
href="mailto:sebastian.huber@embedded-brains.de"
moz-do-not-send="true">sebastian.huber@embedded-brains.de</a>
<a class="moz-txt-link-rfc2396E"
href="mailto:sebastian.huber@embedded-brains.de"
moz-do-not-send="true"><mailto:sebastian.huber@embedded-brains.de></a>>
wrote:
<br>
<br>
On 30/03/2020 15:35, Joel Sherrill wrote:
<br>
<br>
<blockquote type="cite" style="color: #000000;"> What
about the
<br>
<br>
CONFIGURE_FILESYSTEM_ENTRY_DEVFS
<br>
CONFIGURE_FILESYSTEM_ENTRY_DOSFS
<br>
CONFIGURE_FILESYSTEM_ENTRY_FTPFS
<br>
CONFIGURE_FILESYSTEM_ENTRY_IMFS
<br>
CONFIGURE_FILESYSTEM_ENTRY_JFFS2
<br>
CONFIGURE_FILESYSTEM_ENTRY_NFS
<br>
CONFIGURE_FILESYSTEM_ENTRY_RFS
<br>
CONFIGURE_FILESYSTEM_ENTRY_TFTPFS
<br>
<br>
configuration options? Is this really something a user
should
<br>
be able to
<br>
define?
<br>
<br>
<br>
Chris will likely chime in later but I believe these are
needed so
<br>
that
<br>
filesystem type is listed in the set of mountable
filesystems. The mount
<br>
command depends on those settings.
<br>
</blockquote>
<br>
Yes, it depends on the settings, but the
<br>
CONFIGURE_FILESYSTEM_ENTRY_* options give you an extra level
of
<br>
control. For example, you can enable the RFS with:
<br>
<br>
#define CONFIGURE_FILESYSTEM_ENTRY_RFS
<br>
<br>
Optionally, you can fine tune the entry:
<br>
<br>
#if defined(CONFIGURE_FILESYSTEM_RFS) \
<br>
&& !defined(CONFIGURE_FILESYSTEM_ENTRY_RFS)
<br>
#define CONFIGURE_FILESYSTEM_ENTRY_RFS \
<br>
{ RTEMS_FILESYSTEM_TYPE_RFS, rtems_rfs_rtems_initialise
}
<br>
#endif
<br>
<br>
I am not sure if this fine tuning is really necessary.
<br>
<br>
<br>
Me either. Looks like a way for someone to provide their own
<br>
version of the definition which seems in the class of defining
your
<br>
own Configuration Table structures. And we removed those.
<br>
<br>
Let's wait for Chris. :)
<br>
</blockquote>
<br>
This dates back to 2010 [1] and I suspect I was attempting to
follow the way confdefs tables were defined then. Anything that
makes things simpler is good.
</blockquote>
<p>Ok, good. Here is a patch which removes these configuration
options:</p>
<p><a class="moz-txt-link-freetext" href="https://lists.rtems.org/pipermail/devel/2020-March/058782.html">https://lists.rtems.org/pipermail/devel/2020-March/058782.html</a></p>
<p>I will now start to document the following options:</p>
<p>CONFIGURE_APPLICATION_NEEDS_ATA_DRIVER
<br>
CONFIGURE_APPLICATION_NEEDS_IDE_DRIVER
<br>
CONFIGURE_ATA_DRIVER_TASK_PRIORITY
<br>
CONFIGURE_CBS_MAXIMUM_SERVERS
<br>
CONFIGURE_DISABLE_NEWLIB_REENTRANCY
<br>
CONFIGURE_EXECUTIVE_RAM_SIZE
<br>
CONFIGURE_EXTRA_MPCI_RECEIVE_SERVER_STACK
<br>
CONFIGURE_FILESYSTEM_ALL
<br>
CONFIGURE_FILESYSTEM_DEVFS
<br>
CONFIGURE_FILESYSTEM_DOSFS
<br>
CONFIGURE_FILESYSTEM_FTPFS
<br>
CONFIGURE_FILESYSTEM_IMFS
<br>
CONFIGURE_FILESYSTEM_JFFS2
<br>
CONFIGURE_FILESYSTEM_NFS
<br>
CONFIGURE_FILESYSTEM_RFS
<br>
CONFIGURE_FILESYSTEM_TFTPFS
<br>
CONFIGURE_IMFS_DISABLE_MKNOD_DEVICE
<br>
CONFIGURE_MALLOC_DIRTY
<br>
CONFIGURE_MAXIMUM_POSIX_SHMS
<br>
CONFIGURE_SCHEDULER_ASSIGNMENTS
<br>
CONFIGURE_SCHEDULER_STRONG_APA
<br>
CONFIGURE_TASK_STACK_ALLOCATOR_AVOIDS_WORK_SPACE
<br>
CONFIGURE_TASK_STACK_FROM_ALLOCATOR
</p>
</body>
</html>