nuttx/nuttx-mirror
1
2
Fork 0
mirror of https://github.com/apache/nuttx.git synced 2025-01-13 10:58:49 +08:00
Code Issues Projects Releases Packages Wiki Activity Actions

binfmt_execmodule() calls to sched_releasttcb() was not updated to use the second, thread type parameter

Browse source 
git-svn-id: svn://svn.code.sf.net/p/nuttx/code/trunk@5779 42af7a65-404d-4744-a932-0658087f49c3
This commit is contained in:
patacongo 2013-03-23 19:06:40 +00:00
parent a1344d8a44
commit 82b86f9c4a
7 changed files with 17 additions and 10 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
ChangeLog
View file

@ -4434,4 +4434,10 @@
in the kernel build. The original implementation was C-based in the kernel build. The original implementation was C-based
and simpler. However, the C code intermixed with SVC calls was and simpler. However, the C code intermixed with SVC calls was
not properly preserving registers. The more complex, assembly not properly preserving registers. The more complex, assembly
language version does not suffer from these issues (2013-03-23). language version does not suffer from these issues. I believe
the the kernel build can not be called "feature complete"
(2013-03-23).
* binfmt/binfmt_execmodule.c: Here is a place where I forget
to update the call to sched_releasetcb() to pass the thread
type as the second parameter (2013-03-23).

4
binfmt/binfmt_execmodule.c
View file

@ -245,10 +245,10 @@ int exec_module(FAR const struct binary_s *binp)
errout_with_stack: errout_with_stack:
#ifndef CONFIG_CUSTOM_STACK #ifndef CONFIG_CUSTOM_STACK
tcb->cmn.stack_alloc_ptr = NULL; tcb->cmn.stack_alloc_ptr = NULL;
sched_releasetcb(&tcb->cmn); sched_releasetcb(&tcb->cmn, TCB_FLAG_TTYPE_TASK);
kufree(stack); kufree(stack);
#else #else
sched_releasetcb(&tcb->cmn); sched_releasetcb(&tcb->cmn, TCB_FLAG_TTYPE_TASK);
#endif #endif
goto errout; goto errout;

3
configs/open1788/knsh/defconfig
View file

@ -191,8 +191,7 @@ CONFIG_LPC17_GPDMA=y
# #
# SDIO Configuration # SDIO Configuration
# #
# CONFIG_SDIO_DMA=y # CONFIG_SDIO_DMA is not defined
CONFIG_SDIO_DMAPRIO=0x0
# CONFIG_SDIO_WIDTH_D1_ONLY is not set # CONFIG_SDIO_WIDTH_D1_ONLY is not set
# #

3
configs/open1788/nsh/defconfig
View file

@ -185,8 +185,7 @@ CONFIG_LPC17_GPDMA=y
# #
# SDIO Configuration # SDIO Configuration
# #
# CONFIG_SDIO_DMA=y # CONFIG_SDIO_DMA is not defined
CONFIG_SDIO_DMAPRIO=0x0
# CONFIG_SDIO_WIDTH_D1_ONLY is not set # CONFIG_SDIO_WIDTH_D1_ONLY is not set
# #

3
configs/open1788/scripts/memory.ld
View file

@ -57,7 +57,8 @@
* *
* For the same reasons, the maximum size of the SRAM mapping is limited to * For the same reasons, the maximum size of the SRAM mapping is limited to
* 4KB. Both of these alignment limitations could be reduced by using * 4KB. Both of these alignment limitations could be reduced by using
* multiple regions to map the FLASH/SDRAM range. * multiple regions to map the FLASH/SDRAM range or perhaps with some
* clever use of subregions.
* *
* A detailed memory map for the 64KB CPU SRAM region is as follows: * A detailed memory map for the 64KB CPU SRAM region is as follows:
* *

3
configs/sam3u-ek/scripts/memory.ld
View file

@ -58,7 +58,8 @@
* *
* For the same reasons, the maximum size of the SRAM mapping is limited to * For the same reasons, the maximum size of the SRAM mapping is limited to
* 4KB. Both of these alignment limitations could be reduced by using * 4KB. Both of these alignment limitations could be reduced by using
* multiple regions to map the FLASH/SDRAM range. * multiple regions to map the FLASH/SDRAM range or perhaps with some
* clever use of subregions.
* *
* A detailed memory map for the 16Kb SRAM region is as follows: * A detailed memory map for the 16Kb SRAM region is as follows:
* *

3
configs/stm32f4discovery/scripts/memory.ld
View file

@ -65,7 +65,8 @@
* *
* For the same reasons, the maximum size of the SRAM mapping is limited to * For the same reasons, the maximum size of the SRAM mapping is limited to
* 4KB. Both of these alignment limitations could be reduced by using * 4KB. Both of these alignment limitations could be reduced by using
* multiple regions to map the FLASH/SDRAM range. * multiple regions to map the FLASH/SDRAM range or perhaps with some
* clever use of subregions.
* *
* A detailed memory map for the 112KB SRAM region is as follows: * A detailed memory map for the 112KB SRAM region is as follows:
* *