| Commit message (Collapse) | Author | Files | Lines |
|
Do not use reserved interrupt IDs.
|
|
Make the GIC interrupt controller support a subgroup of the generic interrupt
controller support.
|
|
In addtion to 1023, the GICC_IAR register may return 1022 as a special value.
Simply check for a valid interrupt vector for the dispatching.
Check the GICC_IAR again after the dispatch to quickly process a next interrupt
without having to go through the interrupt prologue and epiloge.
|
|
This patch moves the bcm2835 system timer driver in the arm/raspberrypi directory to the shared directory and adjusts arm/raspberrypi BSP.
|
|
Make the clock driver parameters configurable. Use the maximum counter
frequency to get the best time resolution. Decouple the CPU counter from the
timecounter. Make the tick catch up handling more robust. Add a validation
test for the tick catch up.
|
|
Replace the BSP_CONSOLE_MINOR BSP option for the Xilinx Zynq BSPs with the new
BSP option ZYNQ_UART_KERNEL_IO_BASE_ADDR. Move the kernel I/O support to a
shared file.
|
|
This helps to provide a shared implementation of the kernel I/O support.
|
|
Make the initialization and polled functions independent of the Termios
context. This helps to implement the kernel I/O support without a dependency
on the Termios framework.
|
|
Move declarations of bsp_interrupt_get_affinity() and
bsp_interrupt_set_affinity() to <bsp/irq-generic.h>. Canonicalize the
<bsp/irq.h> includes.
Implement bsp_interrupt_get_affinity() and bsp_interrupt_set_affinity() only if
needed (usually RTEMS_SMP).
Provide stub implementations for i386 to fix build errors.
|
|
Pass the parameter of the clock interrupt handler to
Clock_driver_support_at_tick() and Clock_driver_timecounter_tick(). This makes
it possible to use the interrupt handler argument in clock drivers.
Use the interrupt handler provided by Clock_driver_support_install_isr() to
avoid local delarations of Clock_isr().
Update #4862.
|
|
The proper name is now CONFIGURE_MAXIMUM_FILE_DESCRIPTORS.
|
|
`tms570_sci_interrupt_handler()` is called when an RX interrupt fires. It checks
in the register `FLR`, the `RXRDY` bit (Receiver ready flag - indicate that the
SCIRD contains new data). If it is set, it calls
`tms570_sci_read_received_chars()`.
`tms570_sci_read_received_chars()` checks the register `RD` against 0. If it is
non zero, it returns 1 to indicate that one byte was read.
In the old behavior, if it is zero, the function returns 0 to indicate that no
data was read.
The new behavior is to not silently drop 0x00 bytes. Ignoring 0x00 bytes is fine
when working with printable text (which, I assume, is how this driver was
tested), but as soon as the UART is used in non canonical (raw) mode, with
potentially 0x00 bytes, these bytes will be silently dropped, causing issues in
the data/protocol layer above.
Update #4982.
|
|
This corrects an issue where caches can be dirty on warm boot.
|
|
This option replaces BSP_OSCILATOR_CLOCK. It may be used in PLL setup
calculatios.
Update #4982.
|
|
Update #4982.
|
|
Update #4982.
|
|
Update #4982.
|
|
Update #4982.
|
|
Update #4982.
|
|
Update #4982.
|
|
Reduce number of interrupt disable/enable actions.
Update #4982.
|
|
Update #4982.
|
|
There is no need to relocate the text and read-only data.
Update #4982.
|
|
Update #4982.
|
|
Update #4982.
|
|
Update #4982.
|
|
Update #4982.
|
|
Make sure that we do not use the stack for this function.
Update #4982.
|
|
Update #4982.
|
|
Do not clear SYSESR and let the application handle the reset source.
Update #4982.
|
|
Update #4982.
|
|
Update #4982.
|
|
Update #4982.
|
|
Update #4982.
|
|
Update #4982.
|
|
Update #4982.
|
|
Update #4982.
|
|
Do not set pins to the default function before the actual setting is
applied. If a pin setting needs to be done in a certain order, then
this should be done explicitly through multiple calls to
tms570_bsp_pinmmr_config().
Update #4982.
|
|
Update #4982.
|
|
Update #4982.
|
|
Bit 1 of the PACT is reserved (writes have no effect).
Update #4982.
|
|
Update #4982.
|
|
Remove obsolete tms570ls3137_hdk_with_loader BSP variant. With the new
memory origin/size build options this variant is no longer required.
Update #4982.
|
|
Reserve the space in a section. This makes it possible to use a common
memory region definition.
Update #4982.
|
|
Update #4982.
|
|
Update #4982.
|
|
Update #4982.
|
|
Update #4982.
|
|
Update #4982.
|
|
Update #4982.
|