In the Zephyr implementation, `sem_timedwait()` uses a potentially wildly different timebase for comparison via `k_uptime_get()` (uptime in ms). The standard specifies `CLOCK_REALTIME`. However, the real-time clock can be modified to an arbitrary value via clock_settime() and there is no guarantee that it will always reflect uptime. This change ensures that `sem_timedwait()` uses a more consistent timebase for comparison. Fixes #46807 Signed-off-by: Christopher Friedt <chrisfriedt@gmail.com>
17 lines
331 B
Plaintext
17 lines
331 B
Plaintext
# Provide some heap space
|
|
CONFIG_HEAP_MEM_POOL_SIZE=2048
|
|
|
|
# Networking config
|
|
CONFIG_NETWORKING=y
|
|
CONFIG_NET_SOCKETS=y
|
|
CONFIG_NET_SOCKETS_POSIX_NAMES=y
|
|
CONFIG_NET_SOCKETPAIR=y
|
|
|
|
# Network driver config
|
|
CONFIG_TEST_RANDOM_GENERATOR=y
|
|
|
|
# Use Portable threads
|
|
CONFIG_PTHREAD_IPC=y
|
|
CONFIG_POSIX_CLOCK=y
|
|
CONFIG_NET_SOCKETS_POSIX_NAMES=y
|