Gregory Nutt 1b1daeb7ef Correct STM32 RTC EXTI bit definition. From Lazlo		2014-10-09 06:25:07 -06:00
..
a1x	Build support for platform-specific shared memory logic. Not logic yet in place	2014-09-24 07:38:11 -06:00
arm	Update everything under nuttx/arch to use the corrected syslog interfaces	2014-10-08 12:48:47 -06:00
armv6-m	Update everything under nuttx/arch to use the corrected syslog interfaces	2014-10-08 12:48:47 -06:00
armv7-a	Update everything under nuttx/arch to use the corrected syslog interfaces	2014-10-08 12:48:47 -06:00
armv7-m	Update everything under nuttx/arch to use the corrected syslog interfaces	2014-10-08 12:48:47 -06:00
c5471	There used to be two ways to pass parameters to new tasks, depending upon the configuration: Either (1) argv[] as created as an array with each string strdup'ed. Or (1) argv[] array and strings were created on the stack before the new task was started. Now, there is only one way, way (1). Way (2) might be slightly more compact, but this is not worth carry the complexity of two different ways of doing the same thing.	2014-09-01 15:39:34 -06:00
calypso	There used to be two ways to pass parameters to new tasks, depending upon the configuration: Either (1) argv[] as created as an array with each string strdup'ed. Or (1) argv[] array and strings were created on the stack before the new task was started. Now, there is only one way, way (1). Way (2) might be slightly more compact, but this is not worth carry the complexity of two different ways of doing the same thing.	2014-09-01 15:39:34 -06:00
common	Misc changes to get a clean build after all of the syslog changes. There are probably other things still broken	2014-10-08 16:23:48 -06:00
dm320	Update everything under nuttx/arch to use the corrected syslog interfaces	2014-10-08 12:48:47 -06:00
imx	Update everything under nuttx/arch to use the corrected syslog interfaces	2014-10-08 12:48:47 -06:00
kinetis	There used to be two ways to pass parameters to new tasks, depending upon the configuration: Either (1) argv[] as created as an array with each string strdup'ed. Or (1) argv[] array and strings were created on the stack before the new task was started. Now, there is only one way, way (1). Way (2) might be slightly more compact, but this is not worth carry the complexity of two different ways of doing the same thing.	2014-09-01 15:39:34 -06:00
kl	There used to be two ways to pass parameters to new tasks, depending upon the configuration: Either (1) argv[] as created as an array with each string strdup'ed. Or (1) argv[] array and strings were created on the stack before the new task was started. Now, there is only one way, way (1). Way (2) might be slightly more compact, but this is not worth carry the complexity of two different ways of doing the same thing.	2014-09-01 15:39:34 -06:00
lpc17xx	There used to be two ways to pass parameters to new tasks, depending upon the configuration: Either (1) argv[] as created as an array with each string strdup'ed. Or (1) argv[] array and strings were created on the stack before the new task was started. Now, there is only one way, way (1). Way (2) might be slightly more compact, but this is not worth carry the complexity of two different ways of doing the same thing.	2014-09-01 15:39:34 -06:00
lpc31xx	Update everything under nuttx/arch to use the corrected syslog interfaces	2014-10-08 12:48:47 -06:00
lpc43xx	There used to be two ways to pass parameters to new tasks, depending upon the configuration: Either (1) argv[] as created as an array with each string strdup'ed. Or (1) argv[] array and strings were created on the stack before the new task was started. Now, there is only one way, way (1). Way (2) might be slightly more compact, but this is not worth carry the complexity of two different ways of doing the same thing.	2014-09-01 15:39:34 -06:00
lpc214x	Update everything under nuttx/arch to use the corrected syslog interfaces	2014-10-08 12:48:47 -06:00
lpc2378	Update everything under nuttx/arch to use the corrected syslog interfaces	2014-10-08 12:48:47 -06:00
nuc1xx	There used to be two ways to pass parameters to new tasks, depending upon the configuration: Either (1) argv[] as created as an array with each string strdup'ed. Or (1) argv[] array and strings were created on the stack before the new task was started. Now, there is only one way, way (1). Way (2) might be slightly more compact, but this is not worth carry the complexity of two different ways of doing the same thing.	2014-09-01 15:39:34 -06:00
sam34	Only SAM4 family has RTTDIS bit in the MR register. SourceForge bug #33 from Fabien Comte	2014-09-17 07:42:12 -06:00
sama5	Build support for platform-specific shared memory logic. Not logic yet in place	2014-09-24 07:39:06 -06:00
samd	There used to be two ways to pass parameters to new tasks, depending upon the configuration: Either (1) argv[] as created as an array with each string strdup'ed. Or (1) argv[] array and strings were created on the stack before the new task was started. Now, there is only one way, way (1). Way (2) might be slightly more compact, but this is not worth carry the complexity of two different ways of doing the same thing.	2014-09-01 15:39:34 -06:00
stm32	Correct STM32 RTC EXTI bit definition. From Lazlo	2014-10-09 06:25:07 -06:00
str71x	Update everything under nuttx/arch to use the corrected syslog interfaces	2014-10-08 12:48:47 -06:00
tiva	There used to be two ways to pass parameters to new tasks, depending upon the configuration: Either (1) argv[] as created as an array with each string strdup'ed. Or (1) argv[] array and strings were created on the stack before the new task was started. Now, there is only one way, way (1). Way (2) might be slightly more compact, but this is not worth carry the complexity of two different ways of doing the same thing.	2014-09-01 15:39:34 -06:00
.gitignore	.dSYM only needs to be in the same .gitignore files as .exe	2013-05-30 15:02:04 -06:00
Makefile	The 'make export' target needs to bundle up the user C startup file (crt0), not the kernel head object	2014-09-04 13:31:34 -06:00