RE: CAN on STM32H7 platforms under NuttX

Roberto There is a DRAFT PR https://github.com/apache/incubator-nuttx/pull/2987 David -Original Message- From: Roberto Bucher [mailto:roberto.buc...@supsi.ch] Sent: Wednesday, April 14, 2021 6:18 AM To: dev@nuttx.apache.org Subject: CAN on STM32H7 platforms under NuttX Hi For a bachelor

RE: IMXRT1064 and 2 Ethernet interfaces

Hi Vadim , This sounds familiar.Please check if that code is a copy of the Kinetis driver. If so, see the changes that were done to it in https://github.com/apache/incubator-nuttx/pull/1273 David -Original Message- From: Вадим Ястребов [mailto:woody_haw...@mail.ru.INVALID] Sent: Frid

RE: [VOTE] Apache NuttX 10.1.0 (incubating) RC0 release

Yes! I just lit the label (backport/10.1) -Original Message- From: Gustavo Henrique Nihei [mailto:ghni...@gmail.com] Sent: Wednesday, April 28, 2021 5:58 AM To: dev@nuttx.apache.org Subject: Re: [VOTE] Apache NuttX 10.1.0 (incubating) RC0 release Hi folks, I believe we should consider ba

RE: NuttX (Online) Workshop 2021 (call for event team members)

Please count me in. -Original Message- From: alin.jerpe...@sony.com [mailto:alin.jerpe...@sony.com] Sent: Tuesday, May 18, 2021 1:54 AM To: dev@nuttx.apache.org Subject: NuttX (Online) Workshop 2021 (call for event team members) Hi all, Yesterday me and Alan were talking about the plans

RE: Nuttx FAT32 issues - corrupted files, wrongly stated free clusters by statfs

hi Reto, What SoC is this on? What type of card are you using? David -Original Message- From: Reto Gähwiler [mailto:gret.hexa...@gmail.com] Sent: Wednesday, May 19, 2021 3:22 AM To: dev@nuttx.apache.org Subject: Re: Nuttx FAT32 issues - corrupted files, wrongly stated free clusters by s

RE: RE: Nuttx FAT32 issues - corrupted files, wrongly stated free clusters by statfs

clusters by statfs Hi David, It is running on an STM32h743zi version V or Y. The SD-card in use is a SwissBit S-45u. Reto On 2021/05/19 11:11:22, David Sidrane wrote: > hi Reto, > > What SoC is this on? What type of card are you using? > > David > > -Original Message

RE: RE: RE: Nuttx FAT32 issues - corrupted files, wrongly stated free clusters by statfs

hanks, Reto On 2021/05/19 12:13:35, David Sidrane wrote: > Hi Reto, > > What is the clock rate to the card and is multiblock enabled? > > David > > -Original Message- > From: Reto Gähwiler [mailto:gret.hexa...@gmail.com] > Sent: Wednesday, May 19, 2021 5:08 AM >

RE: Ethernet cable (network interface availability) detection

ection? Polling the phy, or something > similar? As I recall, David Sidrane submitted a PR to do just this but it was not incoporated. I don't recall why. I recall having some concerns that polling the PHY in maintenance mode would interfere with normal operational mode, but I think David dem

RE: (Standard | Recommended) way to create NuttX applications

Yes you can, Just call the app. Create and app. Call it what you like. user_start etc. Set CONFIG_USERMAIN_STACKSIZE=1100 CONFIG_USER_ENTRYPOINT="user_start" Int user_start(int argc, char *argv[]) { return ...; } CONFIG_USERMAIN_STACKSIZE=1100 CONFIG_USER_ENTRYPOINT="pigs_can_fly " Int

RE: Port of project from NuttX 7.30 to 10.1 RC1: Unexpected IRQ

Hi Sebastien, Stack crashing into heap? Have you upped the stack sizes across the board? David -Original Message- From: Sebastien Lorquet [mailto:sebast...@lorquet.fr] Sent: Wednesday, May 26, 2021 9:22 AM To: dev@nuttx.apache.org Subject: Re: Port of project from NuttX 7.30 to 10.1 RC

RE: Memory locations

Here is a working example. https://github.com/apache/incubator-nuttx/blob/master/arch/arm/src/stm32h7/stm32_spi.c#L715-L716 https://github.com/apache/incubator-nuttx/blob/master/boards/arm/stm32h7/nucleo-h743zi/scripts/flash.ld#L179-L184 You can check it the arm-none-eabi-nm -C nuttx.elf | grep

RE: [Discuss] Migrate the build system to CMake

First, I would like to apologies to Matias for not being able to contribute to the effort. We are working on the PX4 release, and a nuttx upgrade and I just do not have the time to spare. Ironically time is one of the things this discussion is all about. PR with the current build system and CI t

RE: STM32F7/H7: DAC driver missing?

Hi If it is not all there then most likely you will have to port it. David -Original Message- From: Frank-Christian Kruegel [mailto:nu...@istda.com] Sent: Thursday, July 22, 2021 2:00 AM To: dev@nuttx.apache.org Subject: STM32F7/H7: DAC driver missing? Hi. I'm wondering where the drive

RE: Custom audio capabilities

Hi Tim, Emails are getting to the list. David -Original Message- From: Tim Sent: Monday, November 22, 2021 3:26 AM To: dev@nuttx.apache.org Subject: RE: Custom audio capabilities I appreciate no one may have any comments or suggestions but since I have had no replies to my last 2 or 3

RE: Kernel ticking and progmem writes

Is this a dual bank part? Is so you can avoid the bus lock by operating on the other bank. -Original Message- From: Nathan Hartman Sent: Tuesday, November 30, 2021 5:35 AM To: dev@nuttx.apache.org Subject: Re: Kernel ticking and progmem writes On Tue, Nov 30, 2021 at 8:05 AM Fotis Panagi

Re: STM32U5 support

Hi Michael, Of course you are much closer to the problem than I am. So here is just my opinion based on the stm32, stm32f7, stm32h7 lessons. Are the L5 and U5 the same with different marketing names or are there underlying IP differences? What is the delta? I would head the direction of splitti

RE: kconfig-frontends-win32-3.12.1 for windows failed to support some Kconfig syntax?

Yes. This has been discussed here: https://github.com/apache/incubator-nuttx/issues/2405 -Original Message- From: xyluo Sent: Friday, January 21, 2022 9:05 PM To: dev Subject: kconfig-frontends-win32-3.12.1 for windows failed to support some Kconfig syntax? Hello, Recently I need to bui

RE: arm/kinetis vs arm/kl

Hi Karel, It depends on the level of intrusion. You are closer to the problem then I am. So, I will share what I know and hopefully a clear path will emerge for you. I do not know the history of the KL. The Kinetis arch has a notion of IP versioning. See https://github.com/apache/incubator-nuttx/

[DISCUSS]: Self merge and Single company/organization merge gating

I am opening this discussion to widen the audience for feedback on the rules for merging. The original interexchange was in [1] 1 ) Given the geographical and time differences should we consider that once a review with approval* has been done the PR’s author can merge it? 2) Should we conside

[DISCUSS] Default state of NDEBUG

PR 5399 adds an Kconfig option for NDEBUG. The salient discussion begins at [2] there are mixed positions and reasoning. xiaoxiang781216 asked me to raise a discussion on this. The reasoning for the Default state of to be NDEBUG (n) hence undefined so that assert() enabled is the following: 1

RE: [DISCUSS]: Self merge and Single company/organization merge gating

On Self merge: As Nathan pointed out, it is more about time zones then merge velocity. However, using a backport only methodology requires an upstream merge before the work can be backported with least effort and adds a serial delay. It would be ideal to reduces the CI quantum delay this as much a

RE: Serial RX DMA polling

Hi Michal, > rather from board level section Yes Have a look at this example. https://github.com/PX4/PX4-Autopilot/blob/master/boards/px4/fmu-v5x/src/init.cpp#L243-L247 -Original Message- From: Michal Lenc Sent: Sunday, March 6, 2022 2:38 PM To: dev@nuttx.apache.org Subject: Serial RX

RE: STM32U585: Can't enable peripheral clock for IO port I (GPIOIEN in RCC_AHB2ENR1)

Hi Michael, Odd. Did you check the defines? How are you verifying it? Have you JTAG-ed it, could it be bad SVD? Have you just printed the value to be set and the result ? David -Original Message- From: Michael Jung Sent: Friday, March 25, 2022 9:07 AM To: dev Subject: STM32U585: Can't

RE: STM32U585: Can't enable peripheral clock for IO port I (GPIOIEN in RCC_AHB2ENR1)

er returns 0x802000ff. The stm32l5, which I based the stm32u5 code on, did not have an IO port I. I must have missed a piece of logic during porting I guess. Bye, Michael Am Fr., 25. März 2022 um 17:22 Uhr schrieb David Sidrane < david.sidr...@nscdg.com>: > Hi Michael, > > Odd. Did you c

RE: IMXRT1020-EVK hardfault on boot

Hi Nicolas, I have not tested a RT1020 lately. My board is pack becaue I am moving in a fey days. It will be a several weeks before I can l look at it. Possibly Dave Marples github @mubes can lend a hand. David -Original Message- From: nicolas.silv...@ludo.tech Sent: Monday, Augus

Re: STM32F103RET6 and HSI

HSI is not a good choice if there are external interfaces. It can vary too much part to part and over temperature to meet the 2% across the system boundary. They claim 1% @25c but that is 1/2 the budget to begin with, https://www.st.com/resource/en/application_note/dm00425536-how-to-optimize-stm32

Re: STM32H7 SPI status ?

Hi Sebastien, I think it is a stale artifact from before the DMA was fleshed out. We are using DMA on the H7 SPI in PX4. The only caveat is that the default drive strength may be too high and we reduced it with the macro: https://github.com/PX4/PX4-Autopilot/blob/main/boards/px4/fmu-v6x/nuttx-co

RE: [DISCUSS] Graduate NuttX as TLP

+1 - The time has come. David -Original Message- From: Xiang Xiao Sent: Wednesday, October 19, 2022 1:52 AM To: dev@nuttx.apache.org Subject: Re: [DISCUSS] Graduate NuttX as TLP +1. We are ready after two years of incubation! On Wed, Oct 19, 2022 at 1:07 PM Alin Jerpelea wrote: > +1

Re: [VOTE] Apache NuttX Community Graduation

+1: Apache NuttX is ready to graduate to TLP David On 2022/10/21 12:46:47 Nathan Hartman wrote: > Dear Apache NuttX Community, > > Following the [DISCUSS] thread which has gone 72 hours without any > further issues raised [1]: > > This is a call to VOTE on Graduation of Apache NuttX from the >

RE: PWM fast stop operation

Hi Petro, On the STM32 there are shadow registers that buffer the updated data to ensure that outputs are updated synchronously with the end of the period. There is a bit that can be set to force the update to the shadowed registers to be immediate, which will change the count of the current perio

RE: New names of repositories

> I vote for nuttx, nuttx-apps +1 David -Original Message- From: James Dougherty Sent: Friday, November 18, 2022 11:21 AM To: dev@nuttx.apache.org Subject: Re: New names of repositories That’s right! and underscores are difficult to see when the file name is displayed as an underlined

RE: SAM-E70 progmem - in system programming and RAMFUNCS

Is the NVIC_VTABLE repointed to the RAM vectors? -Original Message- From: James Dougherty Sent: Thursday, December 8, 2022 12:40 AM To: dev@nuttx.apache.org Subject: Re: SAM-E70 progmem - in system programming and RAMFUNCS RAMFUNCS certainly works for this funcs with __ramfuncs__ attribu

RE: SAM-E70 progmem - in system programming and RAMFUNCS

gain tomorrow, any ideas, please share! Thank you for your time and attention to this issue... -James On Thu, Dec 8, 2022 at 7:57 AM Gregory Nutt wrote: > On 12/8/2022 5:55 AM, David Sidrane wrote: > > Is the NVIC_VTABLE repointed to the RAM vectors? > > The RAM functions

RE: Intertask communication in NuttX

Have you looked at uOrb? -Original Message- From: Roberto Bucher Sent: Saturday, December 17, 2022 1:53 AM To: dev@nuttx.apache.org Subject: Intertask communication in NuttX Hi after successfully reached to recompile the microROS environment, I'd like to build an intertask communication

RE: Serial driver: No BREAK support?

Hi Nathan, Have you seen https://github.com/apache/nuttx/blob/master/arch/arm/src/stm32f7/stm32_serial.c#L2657 ? David -Original Message- From: Nathan Hartman Sent: Monday, January 30, 2023 7:16 PM To: dev@nuttx.apache.org Subject: Serial driver: No BREAK support? Serial communications

RE: Serial driver: No BREAK support?

about TIOCSBRK. Nathan On Tue, Jan 31, 2023 at 2:27 AM David Sidrane wrote: > Hi Nathan, > > Have you seen > > https://github.com/apache/nuttx/blob/master/arch/arm/src/stm32f7/stm32 > _serial.c#L2657 > ? > > David > > -Original Message- > From: Nathan Hartm

Is there a current list of functions that can be called from interrupt context.

Hi, There has been a lot of good work and changes in system for mm, logging, synchronization, and networking. Do we have a current list of functions that can be called from interrupts? Should we consider a documentation pass to mark these? David

RE: DISCUSSION - Usage of mailing lists for apache projects

I would add that all pull request must have a statement explaining the reason or motivation for the change(s). Just stating the "What" was done is not enough. There must be a "Why" the change is needed. David -Original Message- From: alin.jerpe...@sony.com Sent: Thursday, March 9, 2023

RE: DISCUSSION - Usage of mailing lists for apache projects

reasons simply by typing "git log" if they are in the commit message What do you think ? Thanks Alin -Original Message----- From: David Sidrane Sent: den 9 mars 2023 10:00 To: dev@nuttx.apache.org Cc: Sebastien Lorquet Subject: RE: DISCUSSION - Usage of mailing lists for apache p

Hardcoded Pin mux, pad control and Drive Strength (AKA Slew-rate and Frequency) Settings #1570

Opening the discussion for this issue on the list. See https://github.com/apache/nuttx/issues/1570 I would like to get feedback on the approach see if we can move forward on this. While some solutions were discussed in - Revert "stm32h7 sdmmc: set SDMMC_CK pin to high speed (50 MHz) mod

RE: Hardcoded Pin mux, pad control and Drive Strength (AKA Slew-rate and Frequency) Settings #1570

We can do this with a message pragma, so as not to kill CI. Sebastien Le 07/04/2023 à 15:34, David Sidrane a écrit : > Opening the discussion for this issue on the list. See > https://github.com/apache/nuttx/issues/1570 > > > > I would like to get feedback on the approach see if

RE: Hardcoded Pin mux, pad control and Drive Strength (AKA Slew-rate and Frequency) Settings #1570

-Original Message- From: Frank-Christian Kruegel Sent: Monday, April 10, 2023 9:01 AM To: dev@nuttx.apache.org Subject: Re: Hardcoded Pin mux, pad control and Drive Strength (AKA Slew-rate and Frequency) Settings #1570 Am 10.04.2023 um 14:51 schrieb David Sidrane: > If I attempt

RE: Hardcoded Pin mux, pad control and Drive Strength (AKA Slew-rate and Frequency) Settings #1570

, if LEGACY_PINMAP is set in user config, maybe we can add a compile time warning in stm32h7/stm32_gpio.c that in the future, users are required to update their board.h and once done, disable LEGACY_PINMAP ? Sebastien Le 07/04/2023 à 15:34, David Sidrane a écrit : > Opening the discussion

RE: Hardcoded Pin mux, pad control and Drive Strength (AKA Slew-rate and Frequency) Settings #1570

@davids5, I saw the request on GitHub for help with the STM32G families but unfortunately something has come up and I won't be able to work on it this week. Hopefully someone else can volunteer, otherwise I'll try to help next week... Thanks, Nathan On Tue, Apr 11, 2023 at 7:58 AM Dav

RE: Hardcoded Pin mux, pad control and Drive Strength (AKA Slew-rate and Frequency) Settings #1570

-Original Message- From: David Sidrane Sent: Wednesday, April 12, 2023 2:49 AM To: 'dev@nuttx.apache.org' Subject: RE: Hardcoded Pin mux, pad control and Drive Strength (AKA Slew-rate and Frequency) Settings #1570 Nathan, no worries. I ended up doing the STM32G families yesterd

RE: How ro re-trigger CI workflow?

Close and reopen PR or rebase on master and force push the branch. The latter is preferable if the CI fix was on master -Original Message- From: fft Sent: Saturday, April 22, 2023 4:25 AM To: dev Subject: How ro re-trigger CI workflow? Hello, Two weeks ago, i created a PR #8999 to fi

RE: SD and eMMC performance in Nuttx

Hi Radek Pesina, This may be way off base but, have you tried reverting https://github.com/apache/nuttx/commit/7312a553bbc40f3771c5d53ccded89bed7391f2a It release the CPU but traded that for potentially quantized large delays David -Original Message- From: Radek Pesina Sent: Wednesday,

RE: CAN TX fail handling

Tim, See https://github.com/apache/nuttx/issues/3927 David -Original Message- From: Alan C. Assis Sent: Wednesday, August 9, 2023 3:47 PM To: dev@nuttx.apache.org Cc: Pavel Pisa Subject: Re: CAN TX fail handling Hi Tim, Agree! This behavior could be implemented in the driver, for exa

RE: Addition of STM32H7 MCU's

The way to fix it is to fully name the files that are *different* by replacing the x with the part number’s digit E.G. stm32h7x3xx_irq.h -> stm32h723xx_irq.h The top level inclusion file will have the ifdef logic to include the correct part based on chip selection: See https://github.com/apach

RE: iMXRT usbdev endpoint allocation problem

Hi Marten , See https://github.com/apache/nuttx/pull/4784 Furthermore once all the caching was working, the USB driver had a bug that the bulk endpoints was getting confused with the interrupt endpoints and although sized to 512 where reporting a max size of 1024 causing more fun memory overwrite

RE: IMXRT: LPUART IDLE character Kconfig setting request

What about adding it per [LP]U[S]ART in the Kconfig here https://github.com/apache/nuttx/tree/master/drivers/serial Then any arch can use it. David -Original Message- From: Daniel Appiagyei Sent: Monday, October 9, 2023 12:51 AM To: dev@nuttx.apache.org Subject: IMXRT: LPUART IDLE chara

[Test] Joined

[Test] Joined Is it alive? David

[TEST] Joined

[TEST] Joined Hi Group, Is this thing live yet? *David Sidrane* *david.sidr...@gmail.com *

RE: State of Bitbucket Repsitories

The history will be intact no matter where it is. It will remain BSD until the license changes. The change should be on a branch than a single commit. Then it is a knife edge -Original Message- From: Gregory Nutt [mailto:spudan...@gmail.com] Sent: Tuesday, December 10, 2019 7:44 AM To: de

RE: Project Emails

How about sub modules? We atomically tag across both to keep the project in proper synchronization. David -Original Message- From: Nathan Hartman [mailto:hartman.nat...@gmail.com] Sent: Thursday, December 12, 2019 10:55 AM To: dev@nuttx.apache.org Subject: Re: Project Emails On Thu, Dec

Workflow and Release strategy Proposal (Was RE: Project Emails)

Precisely! We cut a branch as a Release Candidate. nuttx-MM.mm.rr-rcnn. During the release cycle it can have back ports from master if a new feature or bug fix is found it is added if deemed necessary to the release. Workflow Proposal I would ask that we adopt a workflow similar to PX4. [1] - see

Atomic git tagging (was RE: Project Emails)

Greg, I think the below steps will do a an atomic tag/branch (Branch protections may be needed as well) However, it exemplifies why Submodules are evil but useful. A much simpler approach is 2 folder is the same project - I am aware of ALL the arguments - I agree with most of them but there are

Point of order.

Point of order. Recognizing that using the ASF mailing list is all new to some of us. I would like to ask people to keep on topic in threads. Greg raised the issue that the PPMC is not getting things done. I think it is impossible to organize an effort without communication that is focused. Plea

RE: [nuttx] Wiki Backup

Brennan, Thank you for your efforts! Justin: Is there an issue with adding all the PPMC to have the ability to edit the content? I see some naming that looks like url id became the Page Title: For example: NuttX Initialization Sequence is listed under Initsequence https://cwiki.apache.org/con

Re: Contributions (PR or patches)

I would like to reboot this. I would question some of these statements that are conditioned by history: Greg repeatedly stated that he hated PR and prefers patches. So to work with NuttX people sent patches. This is a fresh start, and the value of it is to be able to ASK the group what their pre

Re: Contributions (PR or patches)

> So, how will we keep track of approvals? I assume that GitHub has a built in mechanism for this purpose? Nathan, Yes it if built for this and from my perspective working on a 93 person team, with 67 repositories. It is highly efficient, collaborative, and effective. For example: Ignoring the

RE: [nuttx] Wiki Backup

Thank you Justin! I see. So for benefit of others: Do not follow the link in the email and try to log in. Log into the dashboard first then follow the link there. David -Original Message- From: Justin Mclean [mailto:jus...@classsoftware.com] Sent: Monday, December 16, 2019 3:49 AM To:

RE: [nuttx] Wiki Backup

getting updated, I did about 80% of them. I can finish that today, I just needed to go to sleep last night. Manually clicking through all the pages was grating on me. --Brennan On Mon, Dec 16, 2019, 3:21 AM David Sidrane wrote: > Brennan, > > Thank you for your efforts! > > Just

[REQUIREMENTS- NuttX Workflow]

[REQUIREMENTS- NuttX Workflow] I am creating this thread to gather ONLY REQUIREMENTS. See [DISCUSS - NuttX Workflow] After the requirements are gathered in one place we can discuss the merits and vote on them.

RE: [nuttx] Wiki Backup

space name. Thanks, Brennan <https://cwiki.apache.org/confluence/x/5pNSC> On Mon, Dec 16, 2019 at 12:12 PM David Sidrane wrote: > Brennan, > > I bet it was grueling. Thank you again Brennan! > > David > -Original Message- > From: Brennan Ashton [mailto:bash...@b

Re: [DISCUSS - NuttX Workflow]

Hi, Sharing my thoughts here for discussion. === Source code checking Prior to submission, the submission shall be checked by a source code beatify-er. REQ1: The submission shall not be possible without a local check passing. REQ2: A tool shall be used to check the NuttX coding standard

Re: [DISCUSS - NuttX Workflow]

That is precisely what submodules do:submodules aggregate on a single SHAL N repositories. The problem is: How to have atomic checkout of the correct configuration with out a temporal shift? Please describe how you would do this. Give detailed steps. On 2019/12/18 10:09:26, Alan Carvalho de As

Re: [DISCUSS - NuttX Workflow]

>I haven’t found proper github plugin to get PRs from multiple repos(especially >PRs dependency 1) How would you create a way to do this. Hows about we add a file to the repo with the 2 shals in it and hand edit it before every push? ["NuttX/nuttx"] path = NuttX/nuttx url = h

Re: [DISCUSS - NuttX Workflow]

> 5 issue one pull request from your fork nuttx/apps to apache nuttx/apps > master branch Are you suggesting we have one repo NuttX with 2 folders apps and nuttx? That will simplify everything! - but I suspect we will receive STRONG arguments against it. So you say "one pull request" Where

RE: patch for ntpclient: merge xmit and recv buffer into one to save the stack

+1 -Original Message- From: Gregory Nutt [mailto:spudan...@gmail.com] Sent: Tuesday, December 17, 2019 8:07 PM To: dev@nuttx.apache.org Subject: Re: patch for ntpclient: merge xmit and recv buffer into one to save the stack > Should we enable the attachment before the new workflow settle?

RE: [DISCUSS - NuttX Workflow]

s, that will be annoying with submodules. This will still require separate pull requests for apps and nuttx. I have NEVER seen any contribution that really required an exactly atomic update to both repos. People often send patches for nuttx, and sometimes for apps. Why change that? Sebastien

Re: [DISCUSS - NuttX Workflow]

8 12:50:17, Nathan Hartman wrote: > On Wed, Dec 18, 2019 at 5:46 AM David Sidrane wrote: > > > > 5 issue one pull request from your fork nuttx/apps to apache nuttx/apps > > master branch > > > > Are you suggesting we have one repo NuttX with 2 folders apps and n

RE: [DISCUSS - NuttX Workflow]

odule method bring? Even with a hat repository that contains two submodules (apps and nuttx), you will have to send separate pull requests for each submodule, right? Sebastien Le 18/12/2019 à 14:40, Gregory Nutt a écrit : > On 12/18/2019 4:23 AM, David Sidrane wrote: >> That is precisely

RE: [DISCUSS - NuttX Workflow]

ject: Re: [DISCUSS - NuttX Workflow] On 12/18/2019 4:23 AM, David Sidrane wrote: > That is precisely what submodules do:submodules aggregate on a single SHAL > N repositories. > > The problem is: How to have atomic checkout of the correct configuration > with out a temporal shift? >

RE: [DISCUSS - NuttX Workflow]

The 2 and 3 is to contrast HARD against EASY. This is so ALL of us can realize we are not suggesting doing what is expedient*, What is being suggested is doing what is right. I am having a really hard time to get you to see this is not about EASY. It is subtle. >I don't know if my understanding of

RE: [DISCUSS - NuttX Workflow]

GOOD and BAD does not say why. It just says how one feel about something. I get that the system architecture has a clear separate from OS to apps. No question there. I also see the value in NOT having them in 1 repo. But please bear with me, and let me tease out some "Why" answers on this thread.

RE: [DISCUSS - NuttX Workflow]

Greg, Where do you see any reference to github (In a url as an example?) This is all pure git. Are we going to continue using git? David -Original Message- From: Gregory Nutt [mailto:spudan...@gmail.com] Sent: Wednesday, December 18, 2019 8:07 AM To: dev@nuttx.apache.org Subject: Re: [

RE: [DISCUSS - NuttX Workflow]

Hi Nathan, Great list! I can +1 on most of them, but isn't correct that the PPMC will need to all agree on these? > When they wish to contribute, they can do so: > * Via a pull request > * Via a patch transmitted to us by some method Is this an ASF edict? > Regardless of the method, we would c

RE: [DISCUSS - NuttX Workflow]

Agreed! Gosh I am hoping I am not talking down to people. I just remember my learning curve with git. If we are continuing to use git and I assume we are: My comments are meant to help people that do not understand how to use git for the process and evaluate what they will have to do if we choose

[Degrees of freedom under ASF ]

I would like to get some clarification on the projects degrees of freedom under ASF from our mentors. Since we are all (except a few) new to the “Apache way” I think we need some enlightenment. I feel it is important that we, as a group, understand what are guidelines, rules and absolutes. I do

Re: [Degrees of freedom under ASF ]

Thank you Justin for the quick answers! 1 more below On 2019/12/19 14:00:36, Justin Mclean wrote: > Hi, > > > I would like to get some clarification on the projects degrees of freedom > > under ASF from our mentors. > > As long as you follow the Apache Way you are free to do what you want. W

RE: Workflow and Release strategy Proposal (Was RE: Project Emails)

By who? Where is the vote? -Original Message- From: Gregory Nutt [mailto:spudan...@gmail.com] Sent: Thursday, December 19, 2019 5:45 AM To: dev@nuttx.apache.org Subject: Re: Workflow and Release strategy Proposal (Was RE: Project Emails) > Why would you want to shut down your slack space

RE: [Degrees of freedom under ASF ]

19, 2019 at 10:11 AM David Sidrane wrote: > On 2019/12/19 14:00:36, Justin Mclean wrote: > > It’s preferable yes. But if they can be archived and searchable that’s > > fine. Often a solution is automatically sending that conversion to a > > mailing list or bringing back

RE: [DISCUSS - NuttX Workflow]

Greg, please read the first post again.

RE: Contributions (PR or patches)

as long as they apply > > clean and someone will spend the time to test them manually. > > > > Regards > > Alin > > > > > > On Mon, Dec 16, 2019 at 12:56 PM David Sidrane > wrote: > > > >>> So, how will we keep track of approvals

RE: [DISCUSS - NuttX Workflow]

This reads like a past slack discussion that ignored HW. Is that really what an embedded system OS should do? > Changes to code in MCU architectural support, board support, or features > in the periphery of the OS should be at the discretion of the > committer. Committers should use their best jud

Re: [DISCUSS - NuttX Workflow]

Hi Nathan, You Rock! On 2019/12/20 05:31:37, Nathan Hartman wrote: > On Thu, Dec 19, 2019 at 4:40 PM David Sidrane wrote: > > > Changes to code in MCU architectural support, board support, or features > > > in the periphery of the OS should be at the discretion o

Re: [DISCUSS - NuttX Workflow]

Hi Nathan, On 2019/12/20 02:51:56, Nathan Hartman wrote: > On Thu, Dec 19, 2019 at 6:24 PM Gregory Nutt wrote: > > >> ] A bad build system change can cause serious problems for a lot of > people around the world. A bad change in the core OS can destroy the good > reputation of the OS. > > > Wh

Re: [DISCUSS - NuttX Workflow]

group decision. Also Pleases do fill us in on where we can see the SW CI & HW CI you mentioned. Do you have links maybe be we can use it now? Again Sorry! David On 2019/12/20 11:44:23, Alan Carvalho de Assis wrote: > Hi David, > > On 12/20/19, David Sidrane wrote: > > Hi

RE: [DISCUSS - NuttX Workflow]

uration you want to test and it is done. > > BR, > > Alan > >> On 12/20/19, David Sidrane wrote: >> Hi Alan, >> >> Sorry if my intent was misunderstood. I am merely stating facts on were >> we >> are and how got there.I am not assigning blame. I am

RE: [DISCUSS - NuttX Workflow]

On 20 Dec 2019, at 13:09, David Sidrane wrote: > > Hi Fabio, > > What are the capabilities? > > It this 1 RPi/BBB per board nuttx board? > > David > > -Original Message- > From: Fabio Balzano [mailto:fa...@elfarolab.com] > Sent: Friday, December 20,

Attachment test Photo

Got it! How about this. Never got your GitHub invitation? Visit github.com/apache to see if you have an invitation pending. Apache Account:Authed Welcome back, David! *Not David? Log out then!* GitHub Account:Authed You are currently a

Images did not make it - I bet it is in [need auth]

Hi Alan, I Sent with an image. I do not see the post here.It must be stuck in the approval queue. We need to to request access to the moderation page. David

Re: [PATCH] This is a test! Please DON'T commit!

https://lists.apache.org/list.html?dev@nuttx.apache.org LOL - the list does list nor archive attachments. On 2019/12/20 17:56:42, Alan Carvalho de Assis wrote: > Testing attachments. > > Greg, please confirm you can receive attachments. > > BR, > > Alan >

Are you failure with the HAM Story?

All, This is one of my favorite Lessons that I learned... reposted from Private Are you failure with the HAM Story? A husband and his wife were in their kitchen. The husband was sitting at the kitchen table reading the newspaper while his wife was preparing a ham for dinner. The husband watched

RE: Test Repository

+1 -Original Message- From: Gregory Nutt [mailto:spudan...@gmail.com] Sent: Friday, December 20, 2019 4:29 PM To: dev@nuttx.apache.org Subject: Test Repository Looking at https://gitbox.apache.org/repos/, I see several projects, perhaps most projects, that have a special repository just t

RE: Test Repository

Greg, -Original Message- From: Gregory Nutt [mailto:spudan...@gmail.com] Sent: Friday, December 20, 2019 4:32 PM To: dev@nuttx.apache.org Subject: Re: Test Repository > Looking at https://gitbox.apache.org/repos/, I see several projects, > perhaps most projects, that have a special reposi

Re: Test Repository

Hi Justin, Great points. See below On 2019/12/21 00:42:58, Justin Mclean wrote: > Hi, > > You may need to think how this fits into releases. some things to consider: > - Do you want the release to contain test information or not? A lot of Apache > project do include that but some don’t - it m

RE: Away for two weeks

Enjoy! -Original Message- From: Justin Mclean [mailto:jus...@classsoftware.com] Sent: Friday, December 20, 2019 5:07 PM To: dev@nuttx.apache.org Subject: Away for two weeks H, I’m off on a two week break, while I’ll have some time to answer questions, where I'm going for the first week h

RE: Transferring Repositoies (Was Re: Masayuki Ishikawa added to NuttX committers)

+1 -Original Message- From: Brennan Ashton [mailto:bash...@brennanashton.com] Sent: Friday, December 20, 2019 8:47 PM To: dev@nuttx.apache.org Subject: Re: Transferring Repositoies (Was Re: Masayuki Ishikawa added to NuttX committers) On Fri, Dec 20, 2019, 8:31 PM 张铎(Duo Zhang) wrote: >

  1   2   3   4   >