Branch: refs/heads/main
Home: https://github.com/OpenAMP/open-amp
Commit: bb4459fe30c954ae9772d8600e7e86515ff7ffff
https://github.com/OpenAMP/open-amp/commit/bb4459fe30c954ae9772d8600e7e8651…
Author: Bowen Wang <wangbowen6(a)xiaomi.com>
Date: 2024-10-21 (Mon, 21 Oct 2024)
Changed paths:
M lib/rpmsg/rpmsg_virtio.c
Log Message:
-----------
rpmsg_virtio: fix rpmsg_virtio_get_tx_payload_buffer() error
If rpmsg_virtio_notify_wait() returns RPMSG_SUCCESS, we should not
directly return NULL, but call rpmsg_virtio_get_tx_buffer to get
the tx buffer again.
Signed-off-by: Yongrong Wang <wangyongrong(a)xiaomi.com>
Signed-off-by: Bowen Wang <wangbowen6(a)xiaomi.com>
To unsubscribe from these emails, change your notification settings at https://github.com/OpenAMP/open-amp/settings/notifications
Branch: refs/heads/main
Home: https://github.com/OpenAMP/open-amp
Commit: 47be1f3379db20dcff666d3508521e70ee34570c
https://github.com/OpenAMP/open-amp/commit/47be1f3379db20dcff666d3508521e70…
Author: Yongrong Wang <wangyongrong(a)xiaomi.com>
Date: 2024-10-21 (Mon, 21 Oct 2024)
Changed paths:
M lib/remoteproc/remoteproc_virtio.c
M lib/rpmsg/rpmsg_virtio.c
Log Message:
-----------
rpmsg_virtio.c: replace metal_cpu_yield to new libmetal API metal_yield
The CPU yield is not supported by all OSes/processors. If not supported,
this causes a busy loop that monopolizes the CPU. Replace it with the
new metal_yield, it would be managed at the OS level and dispatched to
metal_cpu_yield, metal_sleep_usec, or others.
Signed-off-by: Yongrong Wang <wangyongrong(a)xiaomi.com>
To unsubscribe from these emails, change your notification settings at https://github.com/OpenAMP/open-amp/settings/notifications
Branch: refs/heads/main
Home: https://github.com/OpenAMP/libmetal
Commit: 1ed90fd96772ec577e55cd9f5511ba7b32e070ca
https://github.com/OpenAMP/libmetal/commit/1ed90fd96772ec577e55cd9f5511ba7b…
Author: Arnaud Pouliquen <arnaud.pouliquen(a)foss.st.com>
Date: 2024-10-21 (Mon, 21 Oct 2024)
Changed paths:
M lib/system/generic/sys.h
Log Message:
-----------
lib: system: fix missing metal_yield API for generic systems.
The metal_yield API needs also to be declared for the baremetal systems.
This fix build issue in Open-amp for generic system:
/github/workspace/open-amp/lib/rpmsg/rpmsg_virtio.c:275:17:
error: implicit declaration of function 'metal_yield'
275 | metal_yield();
| ^~~~~~~~~~~
Signed-off-by: Arnaud Pouliquen <arnaud.pouliquen(a)foss.st.com>
To unsubscribe from these emails, change your notification settings at https://github.com/OpenAMP/libmetal/settings/notifications
Branch: refs/heads/main
Home: https://github.com/OpenAMP/libmetal
Commit: 142c40321e6116488ba929a2b79c7a907eb059fa
https://github.com/OpenAMP/libmetal/commit/142c40321e6116488ba929a2b79c7a90…
Author: Yongrong Wang <wangyongrong(a)xiaomi.com>
Date: 2024-10-21 (Mon, 21 Oct 2024)
Changed paths:
M lib/system/freertos/sys.h
M lib/system/freertos/template/sys.h
M lib/system/freertos/xlnx/sys.h
M lib/system/linux/sys.h
M lib/system/nuttx/sys.h
M lib/system/zephyr/sys.h
Log Message:
-----------
lib: system: create a new libmetal API metal_yield
Define metal_yield in sys.h files is more flexible to manage this
in libmetal, metal_yield would be managed at the OS level and
dispatched to metal_cpu_yield, metal_sleep_usec, or others.
Signed-off-by: Yongrong Wang <wangyongrong(a)xiaomi.com>
To unsubscribe from these emails, change your notification settings at https://github.com/OpenAMP/libmetal/settings/notifications
Branch: refs/heads/main
Home: https://github.com/OpenAMP/libmetal
Commit: d0cd9285b72ef1a3bcd6aae536f747ebc1091697
https://github.com/OpenAMP/libmetal/commit/d0cd9285b72ef1a3bcd6aae536f747eb…
Author: Yongrong Wang <wangyongrong(a)xiaomi.com>
Date: 2024-10-21 (Mon, 21 Oct 2024)
Changed paths:
M lib/system/freertos/sys.h
M lib/system/freertos/template/sys.h
M lib/system/freertos/xlnx/sys.h
M lib/system/linux/sys.h
M lib/system/nuttx/sys.h
M lib/system/zephyr/sys.h
Log Message:
-----------
lib/cpu.h: create a new libmetal API metal_yield
define metal_yield in sys.h files is more flexible to manage this
in libmetal, metal_yield would be managed at the OS level and
dispatched to metal_cpu_yield, metal_sleep_usec, or others
Signed-off-by: Yongrong Wang <wangyongrong(a)xiaomi.com>
To unsubscribe from these emails, change your notification settings at https://github.com/OpenAMP/libmetal/settings/notifications
Branch: refs/heads/main
Home: https://github.com/OpenAMP/open-amp
Commit: 6a5fdf1b1f7650b65115a64bbc23729e2e215b97
https://github.com/OpenAMP/open-amp/commit/6a5fdf1b1f7650b65115a64bbc23729e…
Author: Bill Mills <bill.mills(a)linaro.org>
Date: 2024-10-18 (Fri, 18 Oct 2024)
Changed paths:
M .github/actions/build_ci/entrypoint.sh
Log Message:
-----------
CI: reduce zephyr sdk install verbosity
Reduce the console output for the Zephyr sdk install.
This now matches the intent of libmetal but uses the documented wget
option.
Signed-off-by: Bill Mills <bill.mills(a)linaro.org>
Commit: 3541b5771bc7d0e0cd5259f6315639123be8fc05
https://github.com/OpenAMP/open-amp/commit/3541b5771bc7d0e0cd5259f631563912…
Author: Bill Mills <bill.mills(a)linaro.org>
Date: 2024-10-18 (Fri, 18 Oct 2024)
Changed paths:
M .github/actions/build_ci/entrypoint.sh
M .github/workflows/continuous-integration.yml
A .github/workflows/heathcheck.yml
Log Message:
-----------
CI: Do Zephyr build tests on known good and latest versions
Allow Zephyr testing to either use locked known good values
or the very latest versions.
This brings open-amp to parity with libmetal. Open-amp did not have the
SDK URL discovery code so that was added here as part of this.
The known good versions are best for PR checking as if the build fails
it is almost always the PR itself that broke it.
The latest version is good for periodically checking compatibility with
the very latest Zephyr changes.
For now we run both on pushes and PRs.
We also run main against the latest zephyr check weekly as a look ahead.
Signed-off-by: Bill Mills <bill.mills(a)linaro.org>
Compare: https://github.com/OpenAMP/open-amp/compare/c3132d0d631a...3541b5771bc7
To unsubscribe from these emails, change your notification settings at https://github.com/OpenAMP/open-amp/settings/notifications
Branch: refs/heads/main
Home: https://github.com/OpenAMP/open-amp
Commit: 9aa3ee53c7f781effa8d4fb17e37dbffb3f17a31
https://github.com/OpenAMP/open-amp/commit/9aa3ee53c7f781effa8d4fb17e37dbff…
Author: Arnaud Pouliquen <arnaud.pouliquen(a)foss.st.com>
Date: 2024-10-18 (Fri, 18 Oct 2024)
Changed paths:
M lib/CMakeLists.txt
A lib/include/internal/utilities.h
A lib/utils/CMakeLists.txt
A lib/utils/utilities.c
Log Message:
-----------
lib: utils: implement internal safe_strcpy function
The strlcpy() function has only recently become available in glibc.
While this function prevents destination buffer overflow, it seems
that it cannot guarantee read access only within the source buffer.
this is for instance the case if the source string is not terminated by
a'\0' character.
Implement a safe_strcpy to ensure that no access is done out of the
source and destination buffer ranges.
Signed-off-by: Arnaud Pouliquen <arnaud.pouliquen(a)foss.st.com>
Commit: 27bec14883019d0b1a526f7cbd17314360141c0a
https://github.com/OpenAMP/open-amp/commit/27bec14883019d0b1a526f7cbd173143…
Author: Arnaud Pouliquen <arnaud.pouliquen(a)foss.st.com>
Date: 2024-10-18 (Fri, 18 Oct 2024)
Changed paths:
M lib/rpmsg/rpmsg.c
Log Message:
-----------
lib: rpmsg: replace strncpy with internal safe_strcpy
The strncpy function does not ensure that the destination string is
null-terminated. To address this issue, replace strncpy with the
internal safe_strcpy() function, which guarantees null-termination of the
destination string but also access only in buffer memory ranges.
Note: (void)safe_strcpy(...) indicates that the return value is
intentionally ignored.
Signed-off-by: Arnaud Pouliquen <arnaud.pouliquen(a)foss.st.com>
Commit: c3132d0d631a4465bfc062b03274a67acf0039ab
https://github.com/OpenAMP/open-amp/commit/c3132d0d631a4465bfc062b03274a67a…
Author: Arnaud Pouliquen <arnaud.pouliquen(a)foss.st.com>
Date: 2024-10-18 (Fri, 18 Oct 2024)
Changed paths:
M lib/remoteproc/remoteproc.c
Log Message:
-----------
lib: remoteproc: replace strncpy with internal safe_strcpy
The strncpy function does not ensure that the destination string is
null-terminated. To address this issue, replace strncpy with the
internal safe_strcpy() function, which guarantees null-termination of the
destination string but also access only in buffer memory ranges.
Note: (void)safe_strcpy(...) indicates that the return value is
intentionally ignored.
Signed-off-by: Arnaud Pouliquen <arnaud.pouliquen(a)foss.st.com>
Compare: https://github.com/OpenAMP/open-amp/compare/a69881f13134...c3132d0d631a
To unsubscribe from these emails, change your notification settings at https://github.com/OpenAMP/open-amp/settings/notifications