mirror of
https://github.com/apache/nuttx.git
synced 2026-06-04 23:03:27 +08:00
Fix nsh/apps bug
git-svn-id: svn://svn.code.sf.net/p/nuttx/code/trunk@3367 42af7a65-404d-4744-a932-0658087f49c3
This commit is contained in:
@@ -1535,3 +1535,10 @@
|
|||||||
* drivers/uart_16550.c and include/nuttx/uart_16550.h - Support for a generic
|
* drivers/uart_16550.c and include/nuttx/uart_16550.h - Support for a generic
|
||||||
16550 UART.
|
16550 UART.
|
||||||
* configure/qemu-i486/nsh - QEMU NSH example.
|
* configure/qemu-i486/nsh - QEMU NSH example.
|
||||||
|
* ../apps - The apps directory add-on was created by Uros Platise. It
|
||||||
|
supports a set of end-user applications than can be executed on top of
|
||||||
|
NSH. Think of it this way: In a buckled-up embedded application, your
|
||||||
|
end-user programs will probably have their own dedicated start-up logic.
|
||||||
|
But, during development, you might want to have you applications
|
||||||
|
available and executable from the NSH command line. This apps/ addon
|
||||||
|
(and NSH hooks) was contributed by Uros to accomplish just that.
|
||||||
|
|||||||
@@ -8,7 +8,7 @@
|
|||||||
<tr align="center" bgcolor="#e4e4e4">
|
<tr align="center" bgcolor="#e4e4e4">
|
||||||
<td>
|
<td>
|
||||||
<h1><big><font color="#3c34ec"><i>NuttX RTOS</i></font></big></h1>
|
<h1><big><font color="#3c34ec"><i>NuttX RTOS</i></font></big></h1>
|
||||||
<p>Last Updated: March 9, 2011</p>
|
<p>Last Updated: March 11, 2011</p>
|
||||||
</td>
|
</td>
|
||||||
</tr>
|
</tr>
|
||||||
</table>
|
</table>
|
||||||
@@ -2159,6 +2159,13 @@ nuttx-5.19 2011-xx-xx Gregory Nutt <spudmonkey@racsa.co.cr>
|
|||||||
* drivers/uart_16550.c and include/nuttx/uart_16550.h - Support for a generic
|
* drivers/uart_16550.c and include/nuttx/uart_16550.h - Support for a generic
|
||||||
16550 UART.
|
16550 UART.
|
||||||
* configure/qemu-i486/nsh - QEMU NSH example.
|
* configure/qemu-i486/nsh - QEMU NSH example.
|
||||||
|
* ../apps - The apps directory add-on was created by Uros Platise. It
|
||||||
|
supports a set of end-user applications than can be executed on top of
|
||||||
|
NSH. Think of it this way: In a buckled-up embedded application, your
|
||||||
|
end-user programs will probably have their own dedicated start-up logic.
|
||||||
|
But, during development, you might want to have you applications
|
||||||
|
available and executable from the NSH command line. This apps/ addon
|
||||||
|
(and NSH hooks) was contributed by Uros to accomplish just that.
|
||||||
|
|
||||||
pascal-2.1 2011-xx-xx Gregory Nutt <spudmonkey@racsa.co.cr>
|
pascal-2.1 2011-xx-xx Gregory Nutt <spudmonkey@racsa.co.cr>
|
||||||
|
|
||||||
|
|||||||
+11
-5
@@ -492,12 +492,18 @@ static int nsh_execute(FAR struct nsh_vtbl_s *vtbl, int argc, char *argv[])
|
|||||||
}
|
}
|
||||||
}
|
}
|
||||||
|
|
||||||
#ifdef CONFIG_EXAMPLES_NSH_BUILTIN_APPS
|
/* If the command was not found, then try to execute the command from
|
||||||
if (handler == cmd_unrecognized)
|
* a list of pre-built applications.
|
||||||
{
|
*/
|
||||||
/* Try to execute the command from a list of pre-built applications. */
|
|
||||||
|
|
||||||
return nsh_execapp(vtbl, cmd, argv);
|
#ifdef CONFIG_EXAMPLES_NSH_BUILTIN_APPS
|
||||||
|
if (handler == cmd_unrecognized && nsh_execapp(vtbl, cmd, argv) == OK)
|
||||||
|
{
|
||||||
|
/* The pre-built application was successfully started -- run OK.
|
||||||
|
* If not, then fall through to execute the cmd_nrecognized handler.
|
||||||
|
*/
|
||||||
|
|
||||||
|
return OK;
|
||||||
}
|
}
|
||||||
#endif
|
#endif
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user