anchao commented on code in PR #13410:
URL: https://github.com/apache/nuttx/pull/13410#discussion_r1759684106
##########
boards/arm/stm32/olimex-stm32-p407/scripts/memory.ld:
##########
@@ -92,7 +92,7 @@ MEMORY
/* 112Kb of contiguous SRAM */
- ksram (rwx) : ORIGIN = 0x20000000, LENGTH = 8K
- usram (rwx) : ORIGIN = 0x20002000, LENGTH = 8K
- xsram (rwx) : ORIGIN = 0x20008000, LENGTH = 96K
+ ksram (rwx) : ORIGIN = 0x20000000, LENGTH = 16K
+ usram (rwx) : ORIGIN = 0x20004000, LENGTH = 16K
+ xsram (rwx) : ORIGIN = 0x20008000, LENGTH = 80K
Review Comment:
Yes, although `sigev_notify_thread_id` is Linux specific, which should all
be attributed by **SIGEV_THREAD**:
```
struct sigevent {
int sigev_notify; /* Notification method */
int sigev_signo; /* Notification signal */
union sigval sigev_value;
/* Data passed with notification */
void (*sigev_notify_function) (union sigval);
/* Function used for thread
notification (SIGEV_THREAD) */
void *sigev_notify_attributes;
/* Attributes for notification thread
(SIGEV_THREAD) */
pid_t sigev_notify_thread_id;
/* ID of thread to signal
(SIGEV_THREAD_ID); Linux-specific */
};
```
I think here may be no need to change the RAM configuration if use
`CONFIG_SIG_EVTHREAD` to control `sigev_notify_thread_id`.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
