RE: Subject: [VOTE] Apache NuttX 11.0.0 (incubating) RC2 release

2022-09-19 Thread alin.jerpe...@sony.com
Please test this release
We need some more votes to be able to create the release 

Best regards
Alin Jerpelea


-Original Message-
From: Xiang Xiao  
Sent: den 14 september 2022 19:53
To: dev@nuttx.apache.org
Subject: Re: Subject: [VOTE] Apache NuttX 11.0.0 (incubating) RC2 release

+1 with tools/checkelease.sh:
./tools/checkrelease.sh --release 11.0.0-RC2 Downloading release files from 
https://urldefense.com/v3/__https://dist.apache.org/repos/dist/dev/incubator/nuttx/11.0.0-RC2/__;!!JmoZiZGBv3RvKRSx!_AM2wqhyvJXbdzPcQZFOXYpkBNNnZwGoKQnKS8BvvYvbskS3DKRb8iVUnDSCivUymvfOiZxGdtm_vcSa2jG3KyhsDOg$
gpg: directory '/tmp/nuttx-checkrelease/.gnupg' created
gpg: keybox '/tmp/nuttx-checkrelease/.gnupg/pubring.kbx' created
gpg: /tmp/nuttx-checkrelease/.gnupg/trustdb.gpg: trustdb created
gpg: key E1B6E30DB05D6280: public key "Brennan Ashton "
imported
gpg: key 2B8C7F0EAB22000E: public key "Abdelatif Guettouche (CODE SIGNING
KEY) " imported
gpg: key 4137A71698C5E4DB: public key "Alin Jerpelea "
imported
gpg: key 9E711BAD3264C061: public key "Alin Jerpelea "
imported
gpg: key A57CE1279F1E7328: public key "Alin Jerpelea (CODE SIGNING KEY) < 
jerpe...@apache.org>" imported
gpg: key 6E72660F995FBC42: public key "Brennan Ashton < 
bash...@brennanashton.com>" imported
gpg: Total number processed: 6
gpg:   imported: 6
 OK: 
https://urldefense.com/v3/__https://dist.apache.org/repos/dist/dev/incubator/nuttx/KEYS__;!!JmoZiZGBv3RvKRSx!_AM2wqhyvJXbdzPcQZFOXYpkBNNnZwGoKQnKS8BvvYvbskS3DKRb8iVUnDSCivUymvfOiZxGdtm_vcSa2jG3QOvIo50$
   is
imported.
Checking apache-nuttx-11.0.0-incubating.tar.gz sha512...
 OK: apache-nuttx-11.0.0-incubating.tar.gz sha512 hash matches.

Checking apache-nuttx-11.0.0-incubating.tar.gz GPG signature:
gpg: Signature made Fri Sep  9 19:17:06 2022 CST
gpg:using RSA key 9208D2E4B800D66F749AD4E94137A71698C5E4DB
gpg: Good signature from "Alin Jerpelea " [unknown]
gpg: WARNING: This key is not certified with a trusted signature!
gpg:  There is no indication that the signature belongs to the
owner.
Primary key fingerprint: 9208 D2E4 B800 D66F 749A  D4E9 4137 A716 98C5 E4DB
 OK: apache-nuttx-11.0.0-incubating.tar.gz gpg signature matches.

Checking apache-nuttx-11.0.0-incubating.tar.gz for required files:
 OK: all required files exist in nuttx.

Checking apache-nuttx-apps-11.0.0-incubating.tar.gz sha512...
 OK: apache-nuttx-apps-11.0.0-incubating.tar.gz sha512 hash matches.

Checking apache-nuttx-apps-11.0.0-incubating.tar.gz GPG signature:
gpg: Signature made Fri Sep  9 19:17:11 2022 CST
gpg:using RSA key 9208D2E4B800D66F749AD4E94137A71698C5E4DB
gpg: Good signature from "Alin Jerpelea " [unknown]
gpg: WARNING: This key is not certified with a trusted signature!
gpg:  There is no indication that the signature belongs to the
owner.
Primary key fingerprint: 9208 D2E4 B800 D66F 749A  D4E9 4137 A716 98C5 E4DB
 OK: apache-nuttx-apps-11.0.0-incubating.tar.gz gpg signature matches.

Checking apache-nuttx-apps-11.0.0-incubating.tar.gz for required files:
 OK: all required files exist in apps.

Trying to build nuttx sim:asan...
 OK: we were able to build sim:asan.

Trying to run nuttx sim:asan...
==25236==WARNING: ASan is ignoring requested __asan_handle_no_return: stack
top: 0x7ffd0b573000; bottom 0x63123000; size: 0x1ced0b55
(31804422946816)
False positive error reports may follow
For details see 
https://urldefense.com/v3/__https://github.com/google/sanitizers/issues/189__;!!JmoZiZGBv3RvKRSx!_AM2wqhyvJXbdzPcQZFOXYpkBNNnZwGoKQnKS8BvvYvbskS3DKRb8iVUnDSCivUymvfOiZxGdtm_vcSa2jG3WBSDneE$
 OK: ostest with ASAN pass.

On Fri, Sep 9, 2022 at 7:28 PM Alin Jerpelea  wrote:

> Hello all,
> Apache NuttX (Incubating) 11.0.0 RC2 has been staged under [1] and 
> it's time to vote on accepting it for release. If approved we will 
> seek final release approval from the IPMC. Voting will be open for 72hr.
>
> A minimum of 3 binding +1 votes and more binding +1 than binding -1 
> are required to pass.
>
> The Apache requirements for approving a release can be found here [3] 
> "Before voting +1 [P]PMC members are required to download the signed 
> source code package, compile it as provided, and test the resulting 
> executable on their own platform, along with also verifying that the 
> package meets the requirements of the ASF policy on releases."
>
> A document to walk through some of this process has been published on 
> our project wiki and can be found here [4].
>
> [ ] +1 accept (indicate what you validated - e.g. performed the non-RM 
> items in [4]) [ ] -1 reject (explanation required)
>
> Thank you all,
> Alin Jerpelea
> SCM Information:
>   Release tag: nuttx-11.0.0-RC2
>   Hash for the release incubating-nuttx tag:
> d32555f3e0492b8f4caeb407db55de23322724ef
>   Hash for the release incubating-nuttx-apps tag:
> 8b43f9f9ca30f44c1cccae9a9078d5d45b776d35
>
> [1] 
> https://urldefense.com/v3/__https://dist.apache.org/repos/dist/dev/inc
> ubator/nuttx/11.0.0-RC

Re: Subject: [VOTE] Apache NuttX 11.0.0 (incubating) RC2 release

2022-09-19 Thread TimH
FYI I will start to get involved with release testing but I have too many 
in-progress new drivers, and fixes to 10.3 , for my board and arch for it to be 
viable at this time. 

And I’m on holiday 🙂

Regards,

Tim.

> On 19 Sep 2022, at 10:53, alin.jerpe...@sony.com wrote:
> 
> Please test this release
> We need some more votes to be able to create the release 
> 
> Best regards
> Alin Jerpelea
> 
> 
> -Original Message-
> From: Xiang Xiao  
> Sent: den 14 september 2022 19:53
> To: dev@nuttx.apache.org
> Subject: Re: Subject: [VOTE] Apache NuttX 11.0.0 (incubating) RC2 release
> 
> +1 with tools/checkelease.sh:
> ./tools/checkrelease.sh --release 11.0.0-RC2 Downloading release files from 
> https://urldefense.com/v3/__https://dist.apache.org/repos/dist/dev/incubator/nuttx/11.0.0-RC2/__;!!JmoZiZGBv3RvKRSx!_AM2wqhyvJXbdzPcQZFOXYpkBNNnZwGoKQnKS8BvvYvbskS3DKRb8iVUnDSCivUymvfOiZxGdtm_vcSa2jG3KyhsDOg$
> gpg: directory '/tmp/nuttx-checkrelease/.gnupg' created
> gpg: keybox '/tmp/nuttx-checkrelease/.gnupg/pubring.kbx' created
> gpg: /tmp/nuttx-checkrelease/.gnupg/trustdb.gpg: trustdb created
> gpg: key E1B6E30DB05D6280: public key "Brennan Ashton "
> imported
> gpg: key 2B8C7F0EAB22000E: public key "Abdelatif Guettouche (CODE SIGNING
> KEY) " imported
> gpg: key 4137A71698C5E4DB: public key "Alin Jerpelea "
> imported
> gpg: key 9E711BAD3264C061: public key "Alin Jerpelea "
> imported
> gpg: key A57CE1279F1E7328: public key "Alin Jerpelea (CODE SIGNING KEY) < 
> jerpe...@apache.org>" imported
> gpg: key 6E72660F995FBC42: public key "Brennan Ashton < 
> bash...@brennanashton.com>" imported
> gpg: Total number processed: 6
> gpg:   imported: 6
> OK: 
> https://urldefense.com/v3/__https://dist.apache.org/repos/dist/dev/incubator/nuttx/KEYS__;!!JmoZiZGBv3RvKRSx!_AM2wqhyvJXbdzPcQZFOXYpkBNNnZwGoKQnKS8BvvYvbskS3DKRb8iVUnDSCivUymvfOiZxGdtm_vcSa2jG3QOvIo50$
>is
> imported.
> Checking apache-nuttx-11.0.0-incubating.tar.gz sha512...
> OK: apache-nuttx-11.0.0-incubating.tar.gz sha512 hash matches.
> 
> Checking apache-nuttx-11.0.0-incubating.tar.gz GPG signature:
> gpg: Signature made Fri Sep  9 19:17:06 2022 CST
> gpg:using RSA key 9208D2E4B800D66F749AD4E94137A71698C5E4DB
> gpg: Good signature from "Alin Jerpelea " [unknown]
> gpg: WARNING: This key is not certified with a trusted signature!
> gpg:  There is no indication that the signature belongs to the
> owner.
> Primary key fingerprint: 9208 D2E4 B800 D66F 749A  D4E9 4137 A716 98C5 E4DB
> OK: apache-nuttx-11.0.0-incubating.tar.gz gpg signature matches.
> 
> Checking apache-nuttx-11.0.0-incubating.tar.gz for required files:
> OK: all required files exist in nuttx.
> 
> Checking apache-nuttx-apps-11.0.0-incubating.tar.gz sha512...
> OK: apache-nuttx-apps-11.0.0-incubating.tar.gz sha512 hash matches.
> 
> Checking apache-nuttx-apps-11.0.0-incubating.tar.gz GPG signature:
> gpg: Signature made Fri Sep  9 19:17:11 2022 CST
> gpg:using RSA key 9208D2E4B800D66F749AD4E94137A71698C5E4DB
> gpg: Good signature from "Alin Jerpelea " [unknown]
> gpg: WARNING: This key is not certified with a trusted signature!
> gpg:  There is no indication that the signature belongs to the
> owner.
> Primary key fingerprint: 9208 D2E4 B800 D66F 749A  D4E9 4137 A716 98C5 E4DB
> OK: apache-nuttx-apps-11.0.0-incubating.tar.gz gpg signature matches.
> 
> Checking apache-nuttx-apps-11.0.0-incubating.tar.gz for required files:
> OK: all required files exist in apps.
> 
> Trying to build nuttx sim:asan...
> OK: we were able to build sim:asan.
> 
> Trying to run nuttx sim:asan...
> ==25236==WARNING: ASan is ignoring requested __asan_handle_no_return: stack
> top: 0x7ffd0b573000; bottom 0x63123000; size: 0x1ced0b55
> (31804422946816)
> False positive error reports may follow
> For details see 
> https://urldefense.com/v3/__https://github.com/google/sanitizers/issues/189__;!!JmoZiZGBv3RvKRSx!_AM2wqhyvJXbdzPcQZFOXYpkBNNnZwGoKQnKS8BvvYvbskS3DKRb8iVUnDSCivUymvfOiZxGdtm_vcSa2jG3WBSDneE$
> OK: ostest with ASAN pass.
> 
>> On Fri, Sep 9, 2022 at 7:28 PM Alin Jerpelea  wrote:
>> 
>> Hello all,
>> Apache NuttX (Incubating) 11.0.0 RC2 has been staged under [1] and 
>> it's time to vote on accepting it for release. If approved we will 
>> seek final release approval from the IPMC. Voting will be open for 72hr.
>> 
>> A minimum of 3 binding +1 votes and more binding +1 than binding -1 
>> are required to pass.
>> 
>> The Apache requirements for approving a release can be found here [3] 
>> "Before voting +1 [P]PMC members are required to download the signed 
>> source code package, compile it as provided, and test the resulting 
>> executable on their own platform, along with also verifying that the 
>> package meets the requirements of the ASF policy on releases."
>> 
>> A document to walk through some of this process has been published on 
>> our project wiki and can be found here [4].
>> 
>> [ ] +1 accept (indicate what you validated -

Re: Cache

2022-09-19 Thread NXWorld Lee
Hi Tim,
Please find the following code in arch/arm/src/armv7-a/arm_head.S.
The ICache and DCache will be enabled by default.
#undef CPU_DCACHE_DISABLE
#undef CPU_ICACHE_DISABLE

#if !defined(CPU_DCACHE_DISABLE) && !defined(CONFIG_SMP)
/* Dcache enable
*
*   SCTLR_CBit 2:  DCache enable
*/

orr r0, r0, #(SCTLR_C)
#endif

#ifndef CPU_ICACHE_DISABLE
/* Icache enable
*
*   SCTLR_IBit 12: ICache enable
*/

orr r0, r0, #(SCTLR_I)
#endif

Best Rds

On Tue, Sep 13, 2022 at 10:05 PM TimH  wrote:

> I found that the up_enable_dcache function is there, with a call to
> cp15_enable_dcache, yes; and that function is in my system.map.  But
> nothing calls it that I can find?
>
> >-Original Message-
> >From: Alan Carvalho de Assis 
> >Sent: 13 September 2022 15:01
> >
> >I don't know about sama5, but probably it is done here:
> arch/arm/src/armv7-
> >a/
> >
> >On 9/13/22, TimH  wrote:
> >> I will probably hit send then find it.but, right now, I can't see if
> >> there's anything I need to do to enable DCACHE?
> >>
> >>
> >>
> >> My .config has CONFIG_ARCH_DCACHE set, and that seems to "enable" all
> >> the various cache functions, including up_enable_dcache, but I can't
> >> find any calls to that function in sama5 related code.
> >>
> >>
> >>
> >> Any clues appreciated!!
> >>
> >>
> >>
> >>
>
>


Re: SAMA5D3 and D4 DMA

2022-09-19 Thread NXWorld Lee
Hi Tim,
SAMA5D2 has 2 XDMA controllers and the definition of peripherals channel is
also different with SAMA5D3 and SAMA5D4.
I will raise a pull request of adding SAMA5D2 XDMA definition to NuttX.
But I didn't test the XDMA driver on any SAMA5Dx platform.

I run NuttX on SAMA5D3 and SAMA5D2, the maxtouch driver and LCD driver were
OK.
Here is a blog introducing running NuttX graphics on SAMA5D3 Xplained with
LCD display driver.
https://blog.csdn.net/oldman147/article/details/73410473?spm=1001.2014.3001.5502


Best Rds

On Mon, Sep 12, 2022 at 10:45 PM TimH  wrote:

> Thanks Greg - I'm sure someone would have tripped over all of this if
> they'd tried to get DMA working. I will at the very least get it tested as
> best as I can on SAMA5D2 - which it definitely seems I am the only actual
> user of with NuttX! Lucky me lol.
>
> >-Original Message-
> >From: Gregory Nutt 
> >
> > I did the D3 and D4 ports years ago and I am not aware of any other use
> of
> >those boards.  DMA was partially functional then, but was not well tested
> and
> >was still buggy.  There were problems documented in
> >https://github.com/apache/incubator-
> >nuttx/blob/master/boards/arm/sama5/sama5d4-ek/README.txt
> >which look like the same issues with the SAMA5D3x-EK in
> >https://github.com/apache/incubator-
> >nuttx/blob/master/boards/arm/sama5/sama5d3x-ek/README.txt
> >
> >The D2 was more an effort of several people and was based initially on the
> >D4 (which was based on the D3).
> >
> >On Mon, Sep 12, 2022 at 8:30 AM TimH  wrote:
> >
> >> Aargh...too quick to retract. I think definitions for ATSAMA5D3 and
> >> ATSAMA5D4 are swapped and there *may* be inconsistencies, based on a
> >> comparison to datasheets. I don't think anyone has used it as I am 99%
> >> sure it wouldn't have worked as best as I can tell. File with issues is:
> >>
> >> arch/arm/src/sama5/sam_dmac.h
> >>
> >> It was the right file I was looking at, got confused by the presence
> >> of sam_xdmac.h as well as sam_dmac.h.
> >>
> >> I will had "# warning" for ATSAMA5D3 and ATSAMA5D4, and add a new
> >> section for SAMA5D2 which at least I hope to be able to check and
> >> confirm as working.
> >>
> >> >-Original Message-
> >> >From: TimH 
> >> >Sent: 12 September 2022 14:54
> >> >To: dev@nuttx.apache.org
> >> >Subject: RE: SAMA5D3 and D4 DMA
> >> >
> >> >Scrap that for now - was looking in the dma not xdma files
> >> >
> >> >>-Original Message-
> >> >>From: TimH 
> >> >>Sent: 12 September 2022 14:14
> >> >>To: dev@nuttx.apache.org
> >> >>Subject: SAMA5D3 and D4 DMA
> >> >>
> >> >>I am reworking DMA to get it working for the SAMA5D2. It seems to me
> >> >>that there are also errors and inconsistencies in the DMA code for
> >> >>the
> >> >>SAMA5D3 and D4 family.
> >> >>
> >> >>
> >> >>
> >> >>For now I have added "# warning" pre-processor statements. I have no
> >> >>means to check ATSAMA3 or ATSAMA4 devices - so unless someone can
> >> >>confirm that DMA does actually work for those 3 families and I've
> >> >>misunderstood something I will suggest that the warnings remain in
> >> >>place when I
> >> >eventually
> >> >>submit a PR for my work.
> >> >
> >>
> >>
> >>
>
>


Re: SAMA5D3 and D4 DMA

2022-09-19 Thread TimH
I have reworked the DMA for ATSAMA5D2 but not tested it yet. I will compare to 
yours and hopefully spot any differences or errors, thank you!

Regards,

Tim.

> On 19 Sep 2022, at 17:18, NXWorld Lee  wrote:
> 
> Hi Tim,
> SAMA5D2 has 2 XDMA controllers and the definition of peripherals channel is
> also different with SAMA5D3 and SAMA5D4.
> I will raise a pull request of adding SAMA5D2 XDMA definition to NuttX.
> But I didn't test the XDMA driver on any SAMA5Dx platform.
> 
> I run NuttX on SAMA5D3 and SAMA5D2, the maxtouch driver and LCD driver were
> OK.
> Here is a blog introducing running NuttX graphics on SAMA5D3 Xplained with
> LCD display driver.
> https://blog.csdn.net/oldman147/article/details/73410473?spm=1001.2014.3001.5502
> 
> 
> Best Rds
> 
>> On Mon, Sep 12, 2022 at 10:45 PM TimH  wrote:
>> 
>> Thanks Greg - I'm sure someone would have tripped over all of this if
>> they'd tried to get DMA working. I will at the very least get it tested as
>> best as I can on SAMA5D2 - which it definitely seems I am the only actual
>> user of with NuttX! Lucky me lol.
>> 
>>> -Original Message-
>>> From: Gregory Nutt 
>>> 
>>> I did the D3 and D4 ports years ago and I am not aware of any other use
>> of
>>> those boards.  DMA was partially functional then, but was not well tested
>> and
>>> was still buggy.  There were problems documented in
>>> https://github.com/apache/incubator-
>>> nuttx/blob/master/boards/arm/sama5/sama5d4-ek/README.txt
>>> which look like the same issues with the SAMA5D3x-EK in
>>> https://github.com/apache/incubator-
>>> nuttx/blob/master/boards/arm/sama5/sama5d3x-ek/README.txt
>>> 
>>> The D2 was more an effort of several people and was based initially on the
>>> D4 (which was based on the D3).
>>> 
 On Mon, Sep 12, 2022 at 8:30 AM TimH  wrote:
>>> 
 Aargh...too quick to retract. I think definitions for ATSAMA5D3 and
 ATSAMA5D4 are swapped and there *may* be inconsistencies, based on a
 comparison to datasheets. I don't think anyone has used it as I am 99%
 sure it wouldn't have worked as best as I can tell. File with issues is:
 
 arch/arm/src/sama5/sam_dmac.h
 
 It was the right file I was looking at, got confused by the presence
 of sam_xdmac.h as well as sam_dmac.h.
 
 I will had "# warning" for ATSAMA5D3 and ATSAMA5D4, and add a new
 section for SAMA5D2 which at least I hope to be able to check and
 confirm as working.
 
> -Original Message-
> From: TimH 
> Sent: 12 September 2022 14:54
> To: dev@nuttx.apache.org
> Subject: RE: SAMA5D3 and D4 DMA
> 
> Scrap that for now - was looking in the dma not xdma files
> 
>> -Original Message-
>> From: TimH 
>> Sent: 12 September 2022 14:14
>> To: dev@nuttx.apache.org
>> Subject: SAMA5D3 and D4 DMA
>> 
>> I am reworking DMA to get it working for the SAMA5D2. It seems to me
>> that there are also errors and inconsistencies in the DMA code for
>> the
>> SAMA5D3 and D4 family.
>> 
>> 
>> 
>> For now I have added "# warning" pre-processor statements. I have no
>> means to check ATSAMA3 or ATSAMA4 devices - so unless someone can
>> confirm that DMA does actually work for those 3 families and I've
>> misunderstood something I will suggest that the warnings remain in
>> place when I
> eventually
>> submit a PR for my work.
> 
 
 
 
>> 
>> 



Re: Subject: [VOTE] Apache NuttX 11.0.0 (incubating) RC2 release

2022-09-19 Thread Alan Carvalho de Assis
Guys, please help!!!

The idea is to have the NuttX 11.0.0 available before this weekend (guess why?)

https://nuttx.events/2022/09/19/list-of-presentation-of-the-nuttx-international-2022/

BR,

Alan

On 9/19/22, alin.jerpe...@sony.com  wrote:
> Please test this release
> We need some more votes to be able to create the release
>
> Best regards
> Alin Jerpelea
>
>
> -Original Message-
> From: Xiang Xiao 
> Sent: den 14 september 2022 19:53
> To: dev@nuttx.apache.org
> Subject: Re: Subject: [VOTE] Apache NuttX 11.0.0 (incubating) RC2 release
>
> +1 with tools/checkelease.sh:
> ./tools/checkrelease.sh --release 11.0.0-RC2 Downloading release files from
> https://urldefense.com/v3/__https://dist.apache.org/repos/dist/dev/incubator/nuttx/11.0.0-RC2/__;!!JmoZiZGBv3RvKRSx!_AM2wqhyvJXbdzPcQZFOXYpkBNNnZwGoKQnKS8BvvYvbskS3DKRb8iVUnDSCivUymvfOiZxGdtm_vcSa2jG3KyhsDOg$
> gpg: directory '/tmp/nuttx-checkrelease/.gnupg' created
> gpg: keybox '/tmp/nuttx-checkrelease/.gnupg/pubring.kbx' created
> gpg: /tmp/nuttx-checkrelease/.gnupg/trustdb.gpg: trustdb created
> gpg: key E1B6E30DB05D6280: public key "Brennan Ashton
> "
> imported
> gpg: key 2B8C7F0EAB22000E: public key "Abdelatif Guettouche (CODE SIGNING
> KEY) " imported
> gpg: key 4137A71698C5E4DB: public key "Alin Jerpelea "
> imported
> gpg: key 9E711BAD3264C061: public key "Alin Jerpelea
> "
> imported
> gpg: key A57CE1279F1E7328: public key "Alin Jerpelea (CODE SIGNING KEY) <
> jerpe...@apache.org>" imported
> gpg: key 6E72660F995FBC42: public key "Brennan Ashton <
> bash...@brennanashton.com>" imported
> gpg: Total number processed: 6
> gpg:   imported: 6
>  OK:
> https://urldefense.com/v3/__https://dist.apache.org/repos/dist/dev/incubator/nuttx/KEYS__;!!JmoZiZGBv3RvKRSx!_AM2wqhyvJXbdzPcQZFOXYpkBNNnZwGoKQnKS8BvvYvbskS3DKRb8iVUnDSCivUymvfOiZxGdtm_vcSa2jG3QOvIo50$
>   is
> imported.
> Checking apache-nuttx-11.0.0-incubating.tar.gz sha512...
>  OK: apache-nuttx-11.0.0-incubating.tar.gz sha512 hash matches.
>
> Checking apache-nuttx-11.0.0-incubating.tar.gz GPG signature:
> gpg: Signature made Fri Sep  9 19:17:06 2022 CST
> gpg:using RSA key 9208D2E4B800D66F749AD4E94137A71698C5E4DB
> gpg: Good signature from "Alin Jerpelea " [unknown]
> gpg: WARNING: This key is not certified with a trusted signature!
> gpg:  There is no indication that the signature belongs to the
> owner.
> Primary key fingerprint: 9208 D2E4 B800 D66F 749A  D4E9 4137 A716 98C5 E4DB
>  OK: apache-nuttx-11.0.0-incubating.tar.gz gpg signature matches.
>
> Checking apache-nuttx-11.0.0-incubating.tar.gz for required files:
>  OK: all required files exist in nuttx.
>
> Checking apache-nuttx-apps-11.0.0-incubating.tar.gz sha512...
>  OK: apache-nuttx-apps-11.0.0-incubating.tar.gz sha512 hash matches.
>
> Checking apache-nuttx-apps-11.0.0-incubating.tar.gz GPG signature:
> gpg: Signature made Fri Sep  9 19:17:11 2022 CST
> gpg:using RSA key 9208D2E4B800D66F749AD4E94137A71698C5E4DB
> gpg: Good signature from "Alin Jerpelea " [unknown]
> gpg: WARNING: This key is not certified with a trusted signature!
> gpg:  There is no indication that the signature belongs to the
> owner.
> Primary key fingerprint: 9208 D2E4 B800 D66F 749A  D4E9 4137 A716 98C5 E4DB
>  OK: apache-nuttx-apps-11.0.0-incubating.tar.gz gpg signature matches.
>
> Checking apache-nuttx-apps-11.0.0-incubating.tar.gz for required files:
>  OK: all required files exist in apps.
>
> Trying to build nuttx sim:asan...
>  OK: we were able to build sim:asan.
>
> Trying to run nuttx sim:asan...
> ==25236==WARNING: ASan is ignoring requested __asan_handle_no_return: stack
> top: 0x7ffd0b573000; bottom 0x63123000; size: 0x1ced0b55
> (31804422946816)
> False positive error reports may follow
> For details see
> https://urldefense.com/v3/__https://github.com/google/sanitizers/issues/189__;!!JmoZiZGBv3RvKRSx!_AM2wqhyvJXbdzPcQZFOXYpkBNNnZwGoKQnKS8BvvYvbskS3DKRb8iVUnDSCivUymvfOiZxGdtm_vcSa2jG3WBSDneE$
>  OK: ostest with ASAN pass.
>
> On Fri, Sep 9, 2022 at 7:28 PM Alin Jerpelea  wrote:
>
>> Hello all,
>> Apache NuttX (Incubating) 11.0.0 RC2 has been staged under [1] and
>> it's time to vote on accepting it for release. If approved we will
>> seek final release approval from the IPMC. Voting will be open for 72hr.
>>
>> A minimum of 3 binding +1 votes and more binding +1 than binding -1
>> are required to pass.
>>
>> The Apache requirements for approving a release can be found here [3]
>> "Before voting +1 [P]PMC members are required to download the signed
>> source code package, compile it as provided, and test the resulting
>> executable on their own platform, along with also verifying that the
>> package meets the requirements of the ASF policy on releases."
>>
>> A document to walk through some of this process has been published on
>> our project wiki and can be found here [4].
>>
>> [ ] +1 accept (indicate what you validated - e.g. performed the non-RM
>> items in [4]) [ ] -1 reject