Looks good, thanks!
Kinsey
On Tue, Apr 16, 2024 at 5:20 AM Ning Yang wrote:
> The clock from the ARM timer is derived from the system clock. This clock
> can
> change dynamically e.g. if the system goes into reduced power or in low
> power
> mode. Thus the clock speed adapts to the overall
The clock from the ARM timer is derived from the system clock. This clock can
change dynamically e.g. if the system goes into reduced power or in low power
mode. Thus the clock speed adapts to the overall system performance
capabilities. For accurate timing it is recommended to use the system
The clock from the ARM timer is derived from the system clock. This clock can
change dynamically e.g. if the system goes into reduced power or in low power
mode. Thus the clock speed adapts to the overall system performance
capabilities. For accurate timing it is recommended to use the system
On 13.04.24 12:13, Ning Yang wrote:
diff --git a/bsps/aarch64/raspberrypi/include/bsp/irq.h
b/bsps/aarch64/raspberrypi/include/bsp/irq.h
index 1ff6ae80de..f2dd2f6c14 100644
--- a/bsps/aarch64/raspberrypi/include/bsp/irq.h
+++ b/bsps/aarch64/raspberrypi/include/bsp/irq.h
@@ -9,6 +9,7 @@
/**
The clock from the ARM timer is derived from the system clock. This clock can
change dynamically e.g. if the system goes into reduced power or in low power
mode. Thus the clock speed adapts to the overall system performance
capabilities. For accurate timing it is recommended to use the system
A couple of comments inline below.
On Fri, Apr 12, 2024 at 9:33 AM Ning Yang wrote:
> The clock from the ARM timer is derived from the system clock. This clock
> can change dynamically e.g. if the system goes into reduced power or in low
> power mode. Thus the clock speed adapts to the overall
The clock from the ARM timer is derived from the system clock. This clock can
change dynamically e.g. if the system goes into reduced power or in low power
mode. Thus the clock speed adapts to the overall system performance
capabilities. For accurate timing it is recommended to use the system
Hi Mr. Kinsey Moore,
I will send the patch based on the current RTEMS master as soon as possible.
I am an applicant for GSOC2024 and will continue to improve RPi4 BSP the year.
I'm currently working on debugging UART interrupt mode. Please let me know if
there's anything I can do to help.
Ah, that makes sense. If your patch depends on Utkarsh's work, then we'll
need to work on getting that into upstream RTEMS as well. If your patch can
be rebased on to current RTEMS master, that would be ideal.
Regarding Utkarsh's work not being merged into RTEMS, patches sometimes
slip through
Hi Mr. Kinsey Moore:
I am using the RPi4 BSP (project of GSOC2023) written by Utkarsh Verma. For
some reason it wasn't merged.
https://lists.rtems.org/pipermail/devel/2023-August/076152.html
I got the code from his github: https://github.com/UtkarshVerma/rtems
Best regards,
Ning
> 2024年4月11日
I couldn't get this patch to apply. Are you sure it came from the right
branch and has no merge commits ahead of it?
Kinsey
On Wed, Apr 10, 2024 at 9:24 AM Ning Yang wrote:
> The clock from the ARM timer is derived from the system clock. This clock
> can change dynamically e.g. if the system
The clock from the ARM timer is derived from the system clock. This clock can
change dynamically e.g. if the system goes into reduced power or in low power
mode. Thus the clock speed adapts to the overall system performance
capabilities. For accurate timing it is recommended to use the system
12 matches
Mail list logo
