mirror of
https://gitee.com/mirrors_PX4/PX4-Autopilot.git
synced 2026-10-20 23:13:34 +08:00
Move file-system header files to include/nuttx/fs
git-svn-id: https://nuttx.svn.sourceforge.net/svnroot/nuttx/trunk@4499 7fd9a85b-ad96-42d3-883c-3090e2eb8679
This commit is contained in:
@@ -2307,7 +2307,7 @@ extern void up_ledoff(int led);
|
||||
<ul>
|
||||
<li>
|
||||
<p>
|
||||
<b><code>include/nuttx/fs.h</code></b>.
|
||||
<b><code>include/nuttx/fs/fs.h</code></b>.
|
||||
All structures and APIs needed to work with character drivers are provided in this header file.
|
||||
</p>
|
||||
</li>
|
||||
@@ -2359,7 +2359,7 @@ extern void up_ledoff(int led);
|
||||
<ul>
|
||||
<li>
|
||||
<p>
|
||||
<b><code>include/nuttx/fs.h</code></b>.
|
||||
<b><code>include/nuttx/fs/fs.h</code></b>.
|
||||
All structures and APIs needed to work with block drivers are provided in this header file.
|
||||
</p>
|
||||
</li>
|
||||
@@ -2797,7 +2797,7 @@ extern void up_ledoff(int led);
|
||||
<li><code>MTDIOC_BULKERASE</code>: Erase the entire device</li>
|
||||
</ul>
|
||||
<p>
|
||||
is provided via a sinble <code>ioctl</code> method (see <code>include/nuttx/ioctl.h</code>):
|
||||
is provided via a sinble <code>ioctl</code> method (see <code>include/nuttx/fs/ioctl.h</code>):
|
||||
</p>
|
||||
<ul>
|
||||
<p><code>int (*ioctl)(FAR struct mtd_dev_s *dev, int cmd, unsigned long arg);</code></p>
|
||||
@@ -3827,12 +3827,12 @@ build
|
||||
</li>
|
||||
<li>
|
||||
<code>CONFIG_NUTTX_KERNEL</code>:
|
||||
With most MCUs, NuttX is built as a flat, single executable image
|
||||
With most MCUs, NuttX is built as a flat, single executable image
|
||||
containing the NuttX RTOS along with all application code.
|
||||
The RTOS code and the application run in the same address space and at the same kernel-mode privileges.
|
||||
If this option is selected, NuttX will be built separately as a monolithic, kernel-mode module and the applications
|
||||
If this option is selected, NuttX will be built separately as a monolithic, kernel-mode module and the applications
|
||||
can be added as a separately built, user-mode module.
|
||||
In this a system call layer will be built to support the user- to kernel-mode interface to the RTOS.
|
||||
In this a system call layer will be built to support the user- to kernel-mode interface to the RTOS.
|
||||
</li>
|
||||
<li>
|
||||
<code>CONFIG_MM_REGIONS</code>: If the architecture includes multiple
|
||||
|
||||
Reference in New Issue
Block a user