Oopenvela-robotstm32ldiscovery/chrono: add CONFIG_SLCD
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
stm32ldiscovery/chrono: add CONFIG_SLCD This is to unblock CI check, https://github.com/apache/nuttx/actions/runs/12628628318/job/35185115826 following suggestion per: https://github.com/apache/nuttx/pull/15423#pullrequestreview-2530760373 Signed-off-by: Yanfeng Liu <p-liuyanfeng9@xiaomi.com> | 3 个月前 | |
boards/arm/stm32: migrate to SPDX identifier 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> | 3 个月前 | |
boards/arm/stm32: migrate to SPDX identifier 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> | 3 个月前 | |
boards/arm/stm32: migrate to SPDX identifier 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> | 3 个月前 | |
boards/arm/stm32: migrate to SPDX identifier 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> | 3 个月前 | |
driver/sensors: support custom type of sensor. For examples, the custom sensor could define: struct custem_event_s { uint64_t timestamp; int16_t adc[8]; }; struct sensor_lowerhalf_s g_lower = { .buffer_size = 1024, }; sensor_custom_register(lower, "/dev/sensor/custom0", sizeof(struct custem_event_s)); Signed-off-by: dongjiuzhu <dongjiuzhu1@xiaomi.com> | 3 个月前 |