These changes eliminate the year 2100 as a limit for TOD. The new
limit is the year 4096. This limit is not due to any RTEMS limitation
but just before the year 4183 when the rounding error in the length
of the year adds up to an entire day. See
https://de.wikipedia.org/wiki/Schaltjahr for details.
There are still limits on Classic APIs which use the 32-bit rtems_interval
type. This corresponds to the Score Watchdog_Interval type. This impacts
delays, timeouts, and Classic API "after" timers.
Closes#5143
Co-authored-by: Joel Sherrill <joel@rtems.org>
Co-authored-by: Gedare Bloom <gedare@rtems.org>
The code seems to be broken for years.
Tested to work on real hardware (AMD Athlon) booted
over pxelinux in preparation for CAN stack test
with original Philips/NXP SJA1000 chips.
RTEMS configured with with
RTEMS_POSIX_API = True
BSP_ENABLE_COM1_COM4 = True
USE_COM1_AS_CONSOLE = False
USE_VBE_RM = False
USE_CIRRUS_GD5446 = False
Signed-off-by: Pavel Pisa <ppisa@pikron.com>
This adds a BSP-level function that returns the calculated PSCI
target_cpu parameter for a given cpu_index. BSPs can override this
function to use the correct affinity level for the calculation.
Also updates _CPU_SMP_Start_processor() to make use of this
function and remove code duplication.
This is initial mvp implementation for the Pi5 BSP. The
initial support has the following features:
- PL011 debug uart (full termios console driver)
- Arm Generic Timer (virtual interface)
- GIC-V2 interrupts
This will be extended in follow-up work.
Should Close rtems/programs/gsoc#85
The function cast from more parameters to fewer parameters is generally
unsafe as the additional parameters will be undefined values that happen
to be in the right registers if it is ever called. Instead of casting
the function pointer, provide a dummy function pointer when the original
function pointer is non-NULL since it is only ever used for a
NULL-check.
This warning occurs when comparing a signed variable to an unsigned one.
This addresses warnings that only occurred on 64-bit targets. For the
ones which only appeared on 64-bit targets, the cause was frequently
a mismatch when comparing a combination off_t, ssize_t, and int.
This warning occurs when comparing a signed variable to an unsigned one.
This addresses warnings that only occurred on 64-bit targets. For the
ones which only appeared on 64-bit targets, the cause was frequently
a mismatch when comparing a combination off_t, ssize_t, and int.
This warning occurs when comparing a signed variable to an unsigned one.
This addresses warnings that only occurred on 64-bit targets. For the
ones which only appeared on 64-bit targets, the cause was frequently
a mismatch when comparing a combination off_t, ssize_t, and int.
This warning occurs when comparing a signed variable to an unsigned one.
The cause is frequently a mismatch when comparing a combination off_t,
ssize_t, and int.
This warning occurs when comparing a signed variable to an unsigned one.
This addresses warnings that only occurred on 64-bit targets. For the
ones which only appeared on 64-bit targets, the cause was frequently
a mismatch when comparing a combination off_t, ssize_t, and int.
This warning occurs when comparing a signed variable to an unsigned one.
This addresses warnings that only occurred on 64-bit targets. For the
ones which only appeared on 64-bit targets, the cause was frequently
a mismatch when comparing a combination off_t, ssize_t, and int.
This warning occurs when comparing a signed variable to an unsigned one.
This addresses warnings that only occurred on 64-bit targets. For the
ones which only appeared on 64-bit targets, the cause was frequently
a mismatch when comparing a combination off_t, ssize_t, and int.
This warning occurs when comparing a signed variable to an unsigned one.
This addresses warnings that only occurred on 64-bit targets. For the
ones which only appeared on 64-bit targets, the cause was frequently
a mismatch when comparing a combination off_t, ssize_t, and int.
This warning occurs when comparing a signed variable to an unsigned one.
This addresses warnings that only occurred on 64-bit targets. For the
ones which only appeared on 64-bit targets, the cause was frequently
a mismatch when comparing a combination off_t, ssize_t, and int.
This warning occurs when comparing a signed variable to an unsigned one.
This addresses warnings that only occurred on 64-bit targets. For the
ones which only appeared on 64-bit targets, the cause was frequently
a mismatch when comparing a combination off_t, ssize_t, and int.
This warning occurs when comparing a signed variable to an unsigned one.
This addresses warnings that only occurred on 64-bit targets. For the
ones which only appeared on 64-bit targets, the cause was frequently
a mismatch when comparing a combination off_t, ssize_t, and int.
This started life as third party code but has been previously
modified without __rtems__ conditionals. The modifications fixed
some warnings (sign compare, memset writing past end of area,
and uninitialized structure field) but some were disabled as the
code was too complex to do otherwise without rigorous testing.
This adds a basic BSP for RockPro64, which includes a UART,
an ARM timer, and GICv3 support, and utilizes all available
memory as defined by the upstream U-Boot configuration.
Closes#5414
This warning occurs when comparing a signed variable to an unsigned one.
This is frequently an int or ssize_t variable compared to a uint32_t or
size_t. Sometimes the size_t is from a sizeof() use.
This warning occurs when comparing a signed variable to an unsigned one.
This is frequently an int or ssize_t variable compared to a uint32_t or
size_t. Sometimes the size_t is from a sizeof() use.
This warning occurs when comparing a signed variable to an unsigned one.
This is frequently an int or ssize_t variable compared to a uint32_t or
size_t. Sometimes the size_t is from a sizeof() use.
This warning occurs when comparing a signed variable to an unsigned one.
This is frequently an int or ssize_t variable compared to a uint32_t or
size_t. Sometimes the size_t is from a sizeof() use.
This removes the adapters that provide glue code directly from JFFS2 to
backend storage drivers since JFFS2, the NAND driver, and the QSPI NOR
driver all support the flashdev interface.
This changes the signature of the VMEBus DMA IRQ Callback type
(BSP_VMEDmaIRQCallback) to match that expected by BSP_installVME_isr()
when the callback is installed.
grlib has places where a function similar to memcpy() can be
provided by the driver. The signature does not match memcpy()
which led to function cast warnings when memcpy() was sufficient.
Provided a wrapper function to aligned the signatures.
A write to the sctlr_el1 register is a 'context-changing operation'
and thus requires a pipeline flush for the change to actually take
effect on subsequent instructions.
The isb instruction gurantees this, and ensures mmu is enabled
immediately.
Many files with Eric Valette as author only had his email address.
This led to them being missed in previous relicensing passes.
This effort relicensed where possible and made efforts to have the
file follow the RTEMS standard for top of files (SPDX, Doxygen,
and then copyright/license).
Closes#5418.