The Apache NuttX project team is proud to announce Apache NuttX 12.1.0 released.
The release artifacts and Release Notes can be found
at:https://nuttx.apache.org/download/https://nuttx.apache.org/releases/12.1.0/
Thanks,
Alin Jerpelea
on behalf of Apache NuttX PPMC
On 4/18/2023 6:58 AM, Nathan Hartman wrote:
On Tue, Apr 18, 2023 at 8:52 AM spudaneco wrote:
Perhaps you could use accessor functions to read/write 8, 16 32, 64 bit
values. Each scalar value will be properly aligned and, hence, will lie
within a page.
And those accessor functions could be
On Tue, Apr 18, 2023 at 8:52 AM spudaneco wrote:
> Perhaps you could use accessor functions to read/write 8, 16 32, 64 bit
> values. Each scalar value will be properly aligned and, hence, will lie
> within a page.
And those accessor functions could be macros in FLAT builds where functions
are
Perhaps you could use accessor functions to read/write 8, 16 32, 64 bit values.
Each scalar value will be properly aligned and, hence, will lie within a
page.Sent from my Galaxy
Original message From: Ville Juven
Date: 4/18/23 3:48 AM (GMT-06:00) To: dev@nuttx.apache.org Sub
Hi,
Sorry for the spamfest. Forget what I said about the alignment being a
solution. It is not. Any object allocated from heap that contains a sem_t
structure cannot guarantee that the alignment of sem_t is correct.
So I was just being dumb..
Br,
Ville Juven
On Tue, Apr 18, 2023 at 11:39 AM Juk
Hi,
I like the alignment idea, thanks for bringing it up!
I think forcing the alignment for the semaphore, and accessing it
directly via page pool from the kernel is the simplest and most trivial
thing. It implements what also Greg suggested + fixes the issue of
semaphore being on the page bo
Hi all,
As Tomek said, whatever you choose to do, please make sure everything of
this is absolutely kept optional, at least during the merge and
community validation phase.
I dont think connecting these proposals to CONFIG_BUILD_KERNEL is
granular enough.
Thanks,
Sebastien
Le 18/04/2023
Hi all,
Sorry, this is going a bit off topic.
One wild solution specifically to solve my/our problem
(CONFIG_BUILD_KERNEL) might be to force a "next power-of-two alignment" for
the semaphore. This would ensure that the semaphore ALWAYS fits within a
single page and remove the need for cross page
