sergiotarxz/nuttx
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

LM: Don't initialize .data if running in SRAM. Global missing intialize type. SAMA5 NAND: Fix for read nand in smaller chunks

Browse Source
This commit is contained in:
Gregory Nutt 2013-12-05 10:37:55 -06:00
parent 053956b5f7
commit babb9b4308
3 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
Documentation/NXGraphicsSubsystem.html
View File

@ -356,7 +356,7 @@
<p>
<sup>1</sup><small>NXMU and NXSU are interchangeable other than (1) certain start-up
and intialization APIs (as described below), and (2) timing. With NXSU, NX APIs
and initializeation APIs (as described below), and (2) timing. With NXSU, NX APIs
execute immediately; with NXMU, NX APIs defer and serialize the operations and, hence,
introduce different timing and potential race conditions that you would not experience
with NXSU.</small>

8
Documentation/NuttxPortingGuide.html
View File

@ -2257,7 +2257,7 @@ else
<li><code>up_rtc_time()</code>.
Get the current time in seconds. This is similar to the standard <code>time()</code> function.
This interface is only required if the low-resolution RTC/counter hardware implementation selected.
It is only used by the RTOS during intialization to set up the system time when <code>CONFIG_RTC</code> is set
It is only used by the RTOS during initializeation to set up the system time when <code>CONFIG_RTC</code> is set
but neither <code>CONFIG_RTC_HIRES</code> nor <code>CONFIG_RTC_DATETIME</code> are set.
</li>
<li><code>up_rtc_gettime()</code>.
@ -3511,7 +3511,7 @@ extern void up_ledoff(int led);
<ol>
<li>
<p>
Each USB host class driver includes an intialization entry point that is called from the
Each USB host class driver includes an initializeation entry point that is called from the
application at initialization time.
This driver calls <code>usbhost_registerclass()</code> during this initialization in order to makes itself available in the event the device that it supports is connected.
</p>
@ -3599,7 +3599,7 @@ extern void up_ledoff(int led);
<ol>
<li>
<p>
Each USB device class driver includes an intialization entry point that is called from the
Each USB device class driver includes an initializeation entry point that is called from the
application at initialization time.
</p>
<p>
@ -4134,7 +4134,7 @@ void pm_initialize(void);
</pre></ul>
<p><b>Description:</b>
This function is called by MCU-specific one-time at power on reset in order to initialize the power management capabilities.
This function must be called <i>very</i> early in the intialization sequence <i>before</i> any other device drivers are initialize (since they may attempt to register with the power management subsystem).
This function must be called <i>very</i> early in the initializeation sequence <i>before</i> any other device drivers are initialize (since they may attempt to register with the power management subsystem).
</p>
<p><b>Input Parameters:</b>
None

2
Documentation/NuttxUserGuide.html
View File

@ -1000,7 +1000,7 @@ int posix_spawn_file_actions_destroy(FAR posix_spawn_file_actions_t *file_action
</pre></ul>
<p>
<b>Description:</b>
The <code>posix_spawn_file_actions_destroy()</code> function destroys the object referenced by <code>file_actions</code> which was previously intialized by <code>posix_spawn_file_actions_init()</code>, returning any resources obtained at the time of initialization to the system for subsequent reuse.
The <code>posix_spawn_file_actions_destroy()</code> function destroys the object referenced by <code>file_actions</code> which was previously initializeed by <code>posix_spawn_file_actions_init()</code>, returning any resources obtained at the time of initialization to the system for subsequent reuse.
A <code>posix_spawn_file_actions_t</code> may be reinitialized after having been destroyed, but must not be reused after destruction, unless it has been reinitialized.
</p>
<p>