| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
Add and use _Objects_Put_without_thread_dispatch(). These two functions
pair with the _Objects_Get() function. This helps to introduce object
specific SMP locks to avoid lock contention.
|
|
|
|
|
|
| |
This field is unused except for special case simulator clock drivers.
In these places use an alternative. Add and use
_Thread_Set_global_exit_status() and _Thread_Get_global_exit_status().
|
|
|
|
|
| |
Do not assume that the scheduler selects the main processor for the
initialization thread.
|
|
|
|
|
|
| |
Call _SMP_Handler_initialize() later and move bsp_smp_initialize() into
_SMP_Handler_initialize(). Change bsp_smp_initialize() prototype to
match integer types of calling context.
|
|
|
|
|
|
|
| |
Delete rtems_configuration_get_smp_maximum_processors(). Delete
rtems_configuration_smp_maximum_processors variable. Add
maximum_processors field to rtems_configuration_table if RTEMS_SMP is
defined. Add rtems_configuration_get_maximum_processors().
|
|
|
|
|
|
|
| |
Add and use rtems_libio_exit_helper. Add rtems_libio_exit().
The fclose(stdin) etc. makes no sense during exit. This would use the
_REENT structure of the thread calling _exit().
|
|
|
|
|
| |
Rename open_dev_console() to rtems_libio_post_driver(). Rename
rtems_libio_supp_helper to rtems_libio_post_driver_helper.
|
|
|
|
|
| |
Add and use rtems_libio_helper function type. Add and use
rtems_libio_helper_null() instead of NULL pointer.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Only one of the following can be defined.
+ CONFIGURE_APPLICATION_NEEDS_CLOCK_DRIVER
+ CONFIGURE_APPLICATION_DOES_NOT_NEED_CLOCK_DRIVER
+ CONFIGURE_APPLICATION_NEEDS_TIMER_DRIVER
Otherwise it is a configuration error which can be detected at
compilation time.
|
|
|
|
|
| |
This was not used by any BSP and obsolete now that unified memory
is an option for all BSPs.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
This is the result of a sed script which converts all uses
of @{ into a consistent form.
|
|
|
|
|
|
|
| |
The output of the modules.html is much improved. Most
filesystem and POSIX API related groups are properly nested.
Some formatting issues were addressed as were multiple
inconsistencies.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
http://www.google-melange.com/gci/task/view/google/gci2012/8032207
|
|
|
|
| |
http://www.google-melange.com/gci/task/view/google/gci2012/8006220
|
| |
|
| |
|
|
|
|
| |
http://www.google-melange.com/gci/task/view/google/gci2012/8011204
|
|
|
|
|
|
|
|
|
| |
Do not return from rtems_initialize_start_multitasking() and call
rtems_fatal() instead with a fatal source of RTEMS_FATAL_SOURCE_EXIT and
a fatal code with the exit status.
Remove all bsp_cleanup() functions. The boot_card() is now a no return
function.
|
|
|
|
|
| |
This file contains the parts of <rtems/posix/psignal.h> that are only
necessary for the POSIX API implementation.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add CPU port type CPU_Exception_frame and function
_CPU_Exception_frame_print().
The CPU ports of avr, bfin, h8300, lm32, m32c, m32r, m68k, nios2, sh,
sparc64, and v850 use an empty default implementation of
_CPU_Exception_frame_print().
Add rtems_exception_frame and rtems_exception_frame_print().
Add RTEMS_FATAL_SOURCE_EXCEPTION for CPU exceptions. Use rtems_fatal()
with source RTEMS_FATAL_SOURCE_EXCEPTION in CPU ports of i386, powerpc,
and sparc for unexpected exceptions.
Add third parameter to RTEMS_BSP_CLEANUP_OPTIONS() which controls the
BSP_PRINT_EXCEPTION_CONTEXT define used in the default
bsp_fatal_extension().
Add test sptests/spfatal26.
|
|
|
|
|
| |
This file contains the parts of <rtems/score/userext.h> that are only
necessary for the RTEMS implementation.
|
| |
|
|
|
|
|
| |
Use INTERNAL_ERROR_CPU_ISR_INSTALL_VECTOR on PowerPC for
_CPU_ISR_install_vector().
|
| |
|
| |
|
|
|
|
|
|
| |
A BSP can supply an initial extension via the new optional
BSP_INITIAL_EXTENSION define. It will be the last in the initial
extension table.
|
|
|
|
|
|
|
|
|
| |
The initial extensions remain now in a read-only table and will not be
copied to work space memory. The extension chains are statically
initialized. This makes it possible to call _User_extensions_Iterate()
independent of the system state. It is now guaranteed that the fatal
callout of the initial extensions will be called provided the stack
pointer, the read-only data, and code memory are valid.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
The comment in confdefs.h shows how to do it:
An application can define its own scheduling policy by defining
CONFIGURE_SCHEDULER_USER and the following:
- CONFIGURE_SCHEDULER_ENTRY_POINTS
- CONFIGURE_MEMORY_FOR_SCHEDULER - base memory
- CONFIGURE_MEMORY_PER_TASK_FOR_SCHEDULER - per task memory
|
|
|
|
|
| |
The Configuration is now read-only and must be statically initialized
via confdefs.h or similar.
|
| |
|
|
|
|
|
|
|
| |
Delete rtems_configuration_get_table(),
rtems_configuration_set_stack_space_size(),
rtems_configuration_set_work_space_size(), and
rtems_configuration_set_microseconds_per_tick().
|
| |
|
| |
|
| |
|