Agreed!
The dev list is the only official way to communicate with all users of
NuttX. I would think ALL important discussions need to occur there.
Github is for developers; dev is for everyone.
On 3/7/2023 11:43 AM, Nathan Hartman wrote:
On Tue, Mar 7, 2023 at 12:27 PM Alan C. Assis wrote:
On Tue, Mar 7, 2023 at 12:27 PM Alan C. Assis wrote:
> Some important things to keep in mind to avoid these kind of frustration:
>
> 1) NuttX development is on GitHub, although this mailing list has dev@ in
> its name, the development is not here. In the past Greg used to accept
> patches over ma
Some important things to keep in mind to avoid these kind of frustration:
1) NuttX development is on GitHub, although this mailing list has dev@ in
its name, the development is not here. In the past Greg used to accept
patches over mailing list. But now NuttX is an Apache project TLP;
2) You cann
I imagine that this is occurring because readline also echos the input:
https://github.com/apache/nuttx-apps/blob/master/system/readline/readline_common.c#L644
The low-level serial driver should not echo just because /isconsole /is
true. Console echo is always handled by the application. I wo
Hi,
I am connecting to my board using
python3 -m serial --raw --eol cr /dev/ttyUSB0 115200
This has ALWAYS worked.
Today it does not work anymore.
Every character I send to NSH is echoed TWICE, see below just typing help:
--
seb@lap:~$ python3 -m serial --raw
Greg,
Thanks. The commit link is there:
https://github.com/apache/nuttx/commit/e6227e19433c4999d500437d0a8a5c05f476ceb1
Here is the pull request
https://github.com/apache/nuttx/pull/8623
This pull request was written and reviewed by xiaomi (again) and only
ONE independent review (thanks for
Hi,
I agree with Nathan. The "V=0" -- seems to be an explicit option for "no
verbose" compilation (in other worlds should suppress all the outputs
except errors I hope).
Best regards,
Petro
вт, 7 бер. 2023 р. о 15:59 Nathan Hartman пише:
> On Tue, Mar 7, 2023 at 8:12 AM Sebastien Lorquet
> wr
On Tue, Mar 7, 2023 at 8:12 AM Sebastien Lorquet
wrote:
> Hi,
>
> Do your realize how counter-intuitive this is?
>
> I would have NEVER imagined that V=0 is not the exact contrary of V=1!
I agree. I think it should be:
* No V argument: Make behaves as originally
* V=0: Make's current behavior
It is likely that the issue with the SIGNAL number was introduced by
commit e6227e19433c4999d500437d0a8a5c05f476ceb1
Author: chenrun1
Date: Wed Feb 1 17:17:43 2023 +0800
include/signal.h:Expanding SIGNAL to be consistent with Linux
There is nothing inherently wrong with the
I have been frustrated at times by changes to master and it’s a conundrum:
- If you're developing code and base it on a stable release there's a good
chance that by the time your own code is "done" it will be incompatible with
latest and/or the current release.
- if you develop based on current,
*yet again* it is the proof that multiplying the channels of
communication just dilutes them.
Anything considered a breaking change requiring the use of explicit doc
in the next release SHOULD be discussed here openly.
The commit was approved by David, OK, and, again, xiaomi.
This is not exa
Hi Sebastien,
The commit 03b164f59ce40a3f5677b0588af2aee8d9697bf6 tools/makefile: silent all
compile output
It has been reviewed and approved by several members
https://github.com/apache/nuttx/pull/8378
Best regards
Alin
-Original Message-
From: Sebastien Lorquet
Sent: den 7 mars
Hi,
Do your realize how counter-intuitive this is?
I would have NEVER imagined that V=0 is not the exact contrary of V=1!
Can this silent mode be made optional in a config setting please? It is
really a non-feature. it's just a fantasy to please some committer, and
should have never been acce
On Tue, Mar 7, 2023 at 7:23 AM Tomek CEDRO wrote:
> On Tue, Mar 7, 2023 at 9:24 AM Sebastien Lorquet wrote:
> > No
> > V=1 is an entirely different thing.
> > I dont want to see the output mangled with tons of arm-none-eabi-gcc
> > command lines.
> > This stuff is another breakage
> > Sebastien
On Tue, Mar 7, 2023 at 9:24 AM Sebastien Lorquet wrote:
> No
> V=1 is an entirely different thing.
> I dont want to see the output mangled with tons of arm-none-eabi-gcc
> command lines.
> This stuff is another breakage
> Sebastien
Well if the build is silent and you do not know what happens then
FWIW, I saw this yesterday on a new branch from Master. Bizarrely not with my
first distclean and make but with a subsequent rebuild. Then it disappeared
again: I tracked it down to a duplicate signal value with a random table having
appeared in Kconfig. That branch was short lived so I’m not ha
>Sent: 06 March 2023 21:35
>To: dev@nuttx.apache.org
>
>Put a breakpoint on up_assert.
>
>You can also then set the PC and SP to the saved value to see the context
>of the assertion.
>
>On 3/6/2023 1:01 PM, Tim Hardisty wrote:
>>
>> I would really like it to stop the debug session at the point of t
the problem is that the new SIGWORK is defined by CONFIG_SIG_WORK to 17
without condition
but SIGCHLD is configured by CONFIG_SIG_CHLD , but this var depends on
SCHED_HAVE_PARENT, this var is not defined in my build and SIGCHLD
defaults to 17 in code.
So something is wrong, SIGCHLD shoud not
Hello
So how do you explain this? I did not touch them either and my last
update is not so old, maybe a few weeks.
make menuconfig and saving again did not help.
make -j1 does not help either, in fact I am never using parallel make.
also omg this silent make is awful, seriously how do you r
Alan,
I am a bit tired of NuttX these last months.
Make is not clean. It is someone's preference that was DISCRETELY pushed
without any community discussion, as always.
All the error output is buffered in memory and kept for the last moment.
What is the way to restore the previous behaviour
Hi Sebastien,
I checked the logs and the lib_strsignal.c is untouched for a long time
I would start debugging with make -j1
Best regards
Alin
-Original Message-
From: Sebastien Lorquet
Sent: den 7 mars 2023 09:26
To: dev@nuttx.apache.org
Subject: NuttX is broken
What is this?
NuttX
Hi Sebastien,
Please read:
https://community.apache.org/contributors/etiquette
BTW, the new building system is strange, but more clean.
I think it should at least give some users feedback, like a text
progress bar, etc.
For course it needs improvement, but you don't need to do this way.
BR,
What is this?
NuttX is broken.
I ran make distclean, used the same defconfig, and I get this:
CC: string/lib_strsignal.c string/lib_strsignal.c: In function 'strsignal':
string/lib_strsignal.c:169:7: error: duplicate case value
169 | case SIGWORK:
| ^~~~
string/lib_strsign
No
V=1 is an entirely different thing.
I dont want to see the output mangled with tons of arm-none-eabi-gcc
command lines.
This stuff is another breakage
Sebastien
On 3/7/23 09:22, Marco Casaroli wrote:
Try
make V=1
On Tue, 7 Mar 2023 at 09:18, Sebastien Lorquet wrote:
Hi,
This morn
Try
make V=1
On Tue, 7 Mar 2023 at 09:18, Sebastien Lorquet wrote:
> Hi,
>
> This morning I updated my working copy, ran git pull origin master and
> rebuilt my OS
>
> Now when I run make I get no output. But the cpu fan works.
>
> Only the last line of the console shows text, there is no log m
Hi,
This morning I updated my working copy, ran git pull origin master and
rebuilt my OS
Now when I run make I get no output. But the cpu fan works.
Only the last line of the console shows text, there is no log makefile
anymore.
This is AWFUL!
What happened?
Was make updated by linux min
26 matches
Mail list logo
