| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
Update #2271.
|
| |
|
|
|
| |
This is necessary to use the CPU counter converter even in case no clock
driver is present, e.g. in tmcontext01.
|
| |
|
|
|
|
| |
The nanoseconds extension returned wrong values on secondary processors
since some of the global timer registeres are banked. Use global
variables instead.
|
| | |
|
| | |
|
| |
|
|
|
|
| |
Merge RTEMS_FATAL_SOURCE_BSP_GENERIC and RTEMS_FATAL_SOURCE_BSP_SPECIFIC
into new fatal source RTEMS_FATAL_SOURCE_BSP. This makes it easier to
figure out the code position given a fatal source and code.
|
| |
|
|
|
|
|
|
|
| |
Add a CPU counter interface to allow access to a free-running counter.
It is useful to measure short time intervals. This can be used for
example to enable profiling of critical low-level functions.
Add two busy wait functions rtems_counter_delay_ticks() and
rtems_counter_delay_nanoseconds() implemented via the CPU counter.
|
| | |
|
| |
|
|
|
|
| |
Use the Global Timer for the Cortex-A9 MPCore clock driver instead of
the Private Timer. This enables a consistent nanoseconds since last
context switch value across all processors.
|
| | |
|
| |
|
|
|
|
| |
This allows an application to provide a localised clock freq with
needing to go down the BSP opts path. This is important with the
Zynq where the Xilinx tools generate the frequency.
|
| | |
|
| |
|
