Go to file
Zhe Weng 17584eaa4f net/nat: Rename struct ipv*_nat_entry to ipv*_nat_entry_t
I found `struct ipv*_nat_entry` is missing `_s` suffix, but the name is too long in some cases, so maybe `ipv*_nat_entry_t` could be better.

Signed-off-by: Zhe Weng <wengzhe@xiaomi.com>
2024-04-12 14:39:01 +02:00
.github Minor improvement for tools/ci: Fixed cmake build of bloaty and installation in darwin.sh script. 2024-03-19 20:52:40 +08:00
arch arch/riscv: add T-HEAD CSR mapping 2024-04-11 22:20:39 +08:00
audio Documentation: remove all migrated READMEs 2023-10-29 21:03:54 -03:00
binfmt all: Fix accessing uninitialized local variables 2024-04-04 11:51:54 +08:00
boards video/vnc: add vnc_fb_register 2024-04-12 17:42:49 +08:00
cmake cmake:implement ALLSYMS feat of CMake version 2024-04-03 10:16:21 -03:00
crypto sched: explicitly select the cpuload clock source configuration 2023-11-01 09:27:56 +08:00
Documentation build(deps): bump idna from 3.4 to 3.7 in /Documentation 2024-04-12 10:05:14 +08:00
drivers video/vnc: add vnc_fb_register 2024-04-12 17:42:49 +08:00
dummy build: add initial cmake build system 2023-07-08 13:50:48 +08:00
fs fs/mmap: enable parameter checks always 2024-03-25 20:39:24 +08:00
graphics video/vnc: add vnc_fb_register 2024-04-12 17:42:49 +08:00
include video/vnc: add vnc_fb_register 2024-04-12 17:42:49 +08:00
libs fdcheck: update fdcheck impl 2024-04-11 10:45:44 +08:00
mm mm/map: minor reformating 2024-04-11 14:15:57 +08:00
net net/nat: Rename struct ipv*_nat_entry to ipv*_nat_entry_t 2024-04-12 14:39:01 +02:00
openamp openamp/libmetal.cmake: sync with libmetal.defs 2024-03-28 16:07:49 +08:00
pass1
sched irq: All irq_cpu_locked is called in the critical_section, and the parameter is the current cpu id. 2024-04-12 17:40:23 +08:00
syscall build/cmake: add initial KERNEL mode support 2024-03-15 16:21:23 +08:00
tools add drivertest test cases on sim for CI 2024-04-11 10:33:15 -03:00
video build: add initial cmake build system 2023-07-08 13:50:48 +08:00
wireless Remove the back slash from long literal string 2024-02-19 16:43:15 +01:00
.asf.yaml
.gitignore fs/vfat: Fix typo in the macro DIRSEC_BYTENDX 2024-02-03 12:46:08 -03:00
.yamllint
AUTHORS AUTHORS: add Tomek CEDRO to the list 2023-03-07 14:15:55 +01:00
CMakeLists.txt cmake:implement ALLSYMS feat of CMake version 2024-04-03 10:16:21 -03:00
CONTRIBUTING.md Remove the tail spaces from all files except Documentation 2023-02-26 13:24:24 -08:00
INVIOLABLES.md
Kconfig rpmsg/debug: add debug configs and macros 2024-02-15 19:53:55 -08:00
LICENSE RP2040: Implement board_uniqueid() 2024-03-17 10:00:25 -03:00
Makefile tools:fix some error use of shell command in Windows native build 2022-11-06 16:41:49 +08:00
NOTICE Remove the double blank line from source files 2022-02-20 20:10:14 +01:00
README.md Gathering community recommendations 2023-10-28 13:55:56 +08:00
ReleaseNotes Documentation: move ReleaseNotes 2023-09-26 20:41:00 +08:00

POSIX Badge License Issues Tracking Badge Contributors GitHub Build Badge Documentation Badge

Apache NuttX is a real-time operating system (RTOS) with an emphasis on standards compliance and small footprint. Scalable from 8-bit to 64-bit microcontroller environments, the primary governing standards in NuttX are POSIX and ANSI standards. Additional standard APIs from Unix and other common RTOSs (such as VxWorks) are adopted for functionality not available under these standards, or for functionality that is not appropriate for deeply-embedded environments (such as fork()).

For brevity, many parts of the documentation will refer to Apache NuttX as simply NuttX.

Getting Started

First time on NuttX? Read the Getting Started guide! If you don't have a board available, NuttX has its own simulator that you can run on terminal.

Documentation

You can find the current NuttX documentation on the Documentation Page.

Alternatively, you can build the documentation yourself by following the Documentation Build Instructions.

The old NuttX documentation is still available in the Apache wiki.

Supported Boards

NuttX supports a wide variety of platforms. See the full list on the Supported Platforms page.

Contributing

If you wish to contribute to the NuttX project, read the Contributing guidelines for information on Git usage, coding standard, workflow and the NuttX principles.

License

The code in this repository is under either the Apache 2 license, or a license compatible with the Apache 2 license. See the License Page for more information.