fstest_main.c:340:47: note: expected ‘struct fstest_ctx_s *’ but argument is of type ‘fsblkcnt_t’ {aka ‘long long unsigned int’}
340 | static int fstest_gc(FAR struct fstest_ctx_s *ctx, size_t nbytes)
| ~~~~~~~~~~~~~~~~~~~~~^~~
fstest_main.c:1168:13: error: too few arguments to function ‘fstest_gc’
1168 | ret = fstest_gc(buf.f_bfree);
| ^~~~~~~~~
fstest_main.c:340:12: note: declared here
340 | static int fstest_gc(FAR struct fstest_ctx_s *ctx, size_t nbytes)
| ^~~
Signed-off-by: anjiahao <anjiahao@xiaomi.com>
(1)add dev_alt to manage /dev/crypto
(2)add sha_alt to alternate sha1 algorithm
(3)use new mbedtls_config.h to admin configs of mbedtls
Signed-off-by: makejian <makejian@xiaomi.com>
Made by:
commit 5659906fdfdac0a363aecb329c39c936324dcc55
Author: Gregory Nutt <gnutt@nuttx.org>
Date: Fri Mar 24 12:02:04 2023 -0600
Changes to apps needed by nutts PR 8885
needby:965551
ostest contains some logic that depends on internal implementation of signal sets and ostest must be updated to match those changes.
There is no particular impact from this PR. This PR is the result of impact from nuttx 8885.
Tested with nuttx 8885
Change-Id: I2550888ee29aadcfcf8a98bfe5690920ee2b17d1
Signed-off-by: Xiang Xiao <xiaoxiang@xiaomi.com>
CC: nxcamera.c nxcamera.c: In function 'show_image':
nxcamera.c:85:20: error: initialization of 'uint32_t *' {aka 'unsigned int *'} from incompatible pointer type 'uint8_t *' {aka 'unsigned char *'} [-Werror=incompatible-pointer-types]
85 | uint32_t *pbuf = pcam->bufs[buf->index];
| ^~~~
cc1: all warnings being treated as errors
Signed-off-by: yangsen5 <yangsen5@xiaomi.com>
wasm clang can't find math.h if using libm from toolchain.
It's OK to using math.h from NuttX since only declaration is needed for wasm build.
Signed-off-by: Huang Qi <huangqi3@xiaomi.com>
define a macro for split long variable and redefine variable in batch.
see details in `apps/Make.defs` `SPLITVARIABLE`.
replace the variable reference that caused the error.
Signed-off-by: xuxin19 <xuxin19@xiaomi.com>
A sensor of this type measures the force on it, and additionally
compares the force with one or more specified thresholds. The sensor
can output the force value directly. Moreover, it's usually applied
as a press key. In that case, when it detects a force greater than
some given threshold, a corresponding event is reported.
Signed-off-by: jinxudong <jinxudong@xiaomi.com>
bug: if user input obr_topic is sensor_gps_sate(wrong topic, which does not exist), the using of `strncmp` will assign idx=8 (as sesnor_gps) in the first.
However, there is no match in the `g_sensor_list`, hence idx=8 will give out value of `sensor_gps` as output(wrong).
Change: This update aims to match the whole value of sensor name in `g_sensor_list`, while keeping `sensor_name+number` match in this condition.
Signed-off-by: haopengxiang <haopengxiang@xiaomi.com>
Some vendor hardware precision cannot meet the requirements,
and the deviation needs to be input at this time.
Signed-off-by: yangguangcai <yangguangcai@xiaomi.com>
