The sndbufs field was moved to socket_conn_s as s_sndbufs in the
new NuttX version. Line 955 was missed during rebase while line 718
was already correctly updated.
Fix: conn->sndbufs -> conn->sconn.s_sndbufs
This reverts commit 8f96e59aee9cd0c5bbb82e01044d109f8588fec2.
The implementation of __dso_handle is independent of the HOST OS but dependent on the specific compiler.
Therefore, this patch will cause compilation failures for other cross-compilers on the Windows platform, such as arm-none-eabi-gcc and aarch64-none-elf-gcc.
Constraints should be applied to compiler target rather than compiler host.
Signed-off-by: Shanmin Zhang <zhangshanmin@xiaomi.com>
When enable both `DEV_GPIO` and `GPIO_LOWER_HALF` for a GPIO pin device for an I/O expander pin.
See esp32s3_gpio.c for more details.
Log
xtensa-esp32s3-elf-ld: /workspace/nuttx/staging/libboard.a(esp32s3_bringup.o):(.literal.esp32s3_bringup+0x14): undefined reference to `esp32s3_gpio_init'
xtensa-esp32s3-elf-ld: /workspace/nuttx/staging/libboard.a(esp32s3_bringup.o): in function `esp32s3_bringup':
/workspace/nuttx/boards/xtensa/esp32s3/common/board/esp32s3_bringup.c:409: undefined reference to `esp32s3_gpio_init'
Signed-off-by: wangjianyu3 <wangjianyu3@xiaomi.com>
modlib_read: Read 64 bytes from offset 192665
modlib_symvalue: ERROR: SHN_UNDEF: Exported symbol "__gnu_Unwind_Find_exidx" not found
modlib_relocate: ERROR: Section 2 reloc 12: Failed to get value of symbol[246]: -2
elf_loadbinary: Failed to bind symbols program binary: -2
builtin_loadbinary: Loading file: /mnt/sotest
Signed-off-by: anjiahao <anjiahao@xiaomi.com>
1. revert 4946904, This patch is to solve the crash problem caused by reboot operation. The phenomenon is: when reboot operation is executed, the system will call binder_flush, which will cause the use after free to be called when proc is destroyed.
2. Now, we can rename BIOC_FLUSH to BINDER_FLUSH to avoid system call binder_flush.
3. why revert 4946904, because when we set looper_need_return in advance, it will cause the child thread of the binder thread pool to be unable to exit when it really wants to exit.
Signed-off-by: cuiziwei <cuiziwei@xiaomi.com>
The large max command line length may cause stack overflow.
Test
./tools/configure.sh lm3s6965-ek:qemu-flat
make -j16
qemu-system-arm -semihosting \
-M lm3s6965evb \
-device loader,file=nuttx.bin,addr=0x00000000 \
-netdev user,id=user0 \
-serial mon:stdio -nographic
Link: https://github.com/apache/nuttx-apps/pull/2850
Signed-off-by: wangjianyu3 <wangjianyu3@xiaomi.com>
Notes:
1. This commit do the same thing as TCP did: https://github.com/apache/nuttx/pull/10627
2. UDP uses `iob_navail(false)` but TCP uses `iob_navail(true)`, this is because of a problem related to TCP recv window (https://github.com/apache/nuttx/pull/4142), so we don't need to change UDP now.
Signed-off-by: Zhe Weng <wengzhe@xiaomi.com>
Add lvgl and fb examples for qemu-intel64.
NOTE: multiboot framebufer doesn't work with -kernel argument in QEMU,
NuttX image must be loaded with -cdrom argument.
QEMU command to run examples:
qemu-system-x86_64 -m 2G -cpu host -enable-kvm -cdrom disk.iso -serial mon:stdio
Signed-off-by: p-szafonimateusz <p-szafonimateusz@xiaomi.com>
Summary:
There are differences in different server implementations, so it is necessary to check whether the returned nwqid satisfies the requested number.
Signed-off-by: chenrun1 <chenrun1@xiaomi.com>
Most tools used for compliance and SBOM generation use SPDX identifiers
This change brings us a step closer to an easy SBOM generation.
Signed-off-by: Alin Jerpelea <alin.jerpelea@sony.com>
The if(CONFIG_BINFMT_ELF_RELOCATABLE) block and
nuttx_mod_compile_options_ifdef for CONFIG_LTO_FULL at lines 54-57
were exact duplicates of the block at lines 49-52. Remove the
redundant copy.
Signed-off-by: haopengxiang <haopengxiang@xiaomi.com>