nuttx/arch/sh/src/m16c
2015-02-27 17:19:38 -06:00
..
chip.h Extend stack debug logic to include IDLE and interrupt stacks. Also color the heap as well. Based on suggestions from David Sidrane 2013-11-01 11:16:51 -06:00
Kconfig Change how UARTs are enabled for i.MX, M16C, and ez80 to make them compatible with other chips 2012-11-20 19:59:40 +00:00
m16c_copystate.c Remove os_internal.h it has been replace by several new header files under sched/. There have been some sneak inclusion paths via os_internal.h, so expect a few compilation errors for some architectures 2014-08-08 18:39:28 -06:00
m16c_dumpstate.c Update everything under nuttx/arch to use the corrected syslog interfaces 2014-10-08 12:48:47 -06:00
m16c_head.S More trailing whilespace removal 2014-04-13 16:22:22 -06:00
m16c_initialstate.c Rename _TCB to struct tcb_s 2013-02-04 18:46:28 +00:00
m16c_irq.c More trailing whilespace removal 2014-04-13 16:22:22 -06:00
m16c_lowputc.c configs/skp16c26/ostest: Configuration converted to use the kconfig-frontends tools 2014-03-06 08:28:49 -06:00
m16c_schedulesigaction.c Replace os_internal.h with sched/sched.h in files that actually reference something in sched.h 2014-08-08 17:53:55 -06:00
m16c_serial.c Remove os_internal.h it has been replace by several new header files under sched/. There have been some sneak inclusion paths via os_internal.h, so expect a few compilation errors for some architectures 2014-08-08 18:39:28 -06:00
m16c_sigdeliver.c arch/: board function prototypes are now in include/nuttx/board.h. Remove from architecture header file; Add inclusion of nuttx/board.h to all files referencing board functions 2015-02-27 17:19:38 -06:00
m16c_timer.h Email address change in nuttx/ 2012-09-13 18:32:24 +00:00
m16c_timerisr.c Move clock functions from sched/ to sched/clock 2014-08-08 14:43:02 -06:00
m16c_uart.h Email address change in nuttx/ 2012-09-13 18:32:24 +00:00
m16c_vectors.S More trailing whilespace removal 2014-04-13 16:22:22 -06:00
Make.defs 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