Go to file
Guangyao Ma f67c4dae51 feat: add sync() to vfs
新增sync方法,该方法每次调用,会遍历系统内所有的mount点,调用各个文件系统注册
的sync方法,完成对所有已挂载文件系统的sync操作。

close #I480HV

Signed-off-by: Guangyao Ma <guangyao.ma@outlook.com>
Change-Id: I57ced9c3f7685a448defd17ae56c842796b5668f
2021-09-08 15:41:52 +08:00
.gitee add issue and pr template 2021-04-07 14:49:32 +08:00
apps feat: L0-L1 支持Trace 2021-08-31 20:29:45 +08:00
arch chore(build): optimize build scripts, make Kconfig in DEVICE_PATH mandatory 2021-09-01 18:45:44 +08:00
bsd chore(make): optimize build scripts 2021-08-30 17:18:21 +08:00
compat chore(musl): reduce the modifications of musl 2021-08-19 16:07:12 +08:00
drivers move trace device init from system_init.c to drivers/char/trace.c 2021-09-01 12:49:37 +08:00
figures update openharmony 1.0.1 2021-03-11 18:43:57 +08:00
fs feat: add sync() to vfs 2021-09-08 15:41:52 +08:00
kernel feat: L0-L1 支持Trace 2021-08-31 20:29:45 +08:00
lib chore(make): optimize build scripts 2021-08-30 17:18:21 +08:00
net chore: add default group automatly if needed 2021-08-06 12:05:56 +08:00
platform feat: L0-L1 支持Trace 2021-08-31 20:29:45 +08:00
security Merge branch 'master' of gitee.com:openharmony/kernel_liteos_a into misc 2021-07-27 01:40:59 +00:00
shell feat: add support for gn build system 2021-07-21 15:52:40 +08:00
syscall !570 fix ppoll & add 2 testcases 2021-08-30 02:06:24 +00:00
testsuites feat: L0-L1 支持Trace 2021-08-31 20:29:45 +08:00
tools !596 优化编译脚本,DEVICE_PATH下的drivers/Kconfig由可选改为必选 2021-09-01 11:07:20 +00:00
.gitignore chore(make): fix and optimize some build scripts 2021-08-23 20:47:18 +08:00
BUILD.gn feat(build): make liteos_config_file available as gn argument 2021-09-02 10:54:15 +08:00
Kconfig chore(build): optimize build scripts, make Kconfig in DEVICE_PATH mandatory 2021-09-01 18:45:44 +08:00
LICENSE update openharmony 1.0.1 2021-03-11 18:43:57 +08:00
Makefile chore: optimize build scripts and add lto config entry 2021-08-31 12:04:34 +08:00
OAT.xml chore(oat): 删除二进制文件,并且新增oat屏蔽 2021-08-06 01:41:09 +08:00
README.md fix: 修复文档链接失效问题 2021-08-12 14:21:35 +08:00
README_zh-HK.md fix: 修复文档链接失效问题 2021-08-12 14:21:35 +08:00
README_zh.md fix: 修复文档链接失效问题 2021-08-12 14:21:35 +08:00
build.sh chore(build): optimize build scripts, remove unused config files 2021-09-01 12:39:55 +08:00
config.mk chore(make): optimize build scripts 2021-08-30 17:18:21 +08:00
liteos.gni chore: optimize build scripts and add lto config entry 2021-08-31 12:04:34 +08:00

README.md

LiteOS Cortex-A

Introduction

The OpenHarmony LiteOS Cortex-A is a new-generation kernel developed based on the Huawei LiteOS kernel. Huawei LiteOS is a lightweight operating system OS built for the Internet of Things IoT field. With the rapid development of the IoT industry, OpenHarmony LiteOS Cortex-A brings small-sized, low-power, and high-performance experience and builds a unified and open ecosystem for developers. In addition, it provides rich kernel mechanisms, more comprehensive Portable Operating System Interface POSIX, and a unified driver framework, Hardware Driver Foundation HDF, which offers unified access for device developers and friendly development experience for application developers. Figure 1 shows the architecture of the OpenHarmony LiteOS Cortex-A kernel.

Figure 1 Architecture of the OpenHarmony LiteOS Cortex-A kernel

Directory Structure

/kernel/liteos_a
├── apps                   # User-space init and shell application programs
├── arch                   # System architecture, such as ARM
│   └── arm                # Code for ARM architecture
├── bsd                    # Code of the driver and adaptation layer module related to the FreeBSD, such as the USB module
├── compat                 # Kernel API compatibility
│   └── posix              # POSIX APIs
├── drivers                # Kernel drivers
│   └── char               # Character device
│       ├── mem            # Driver for accessing physical input/output (I/O) devices
│       ├── quickstart     # APIs for quick start of the system
│       ├── random         # Driver for random number generators
│       └── video          # Framework of the framebuffer driver
├── fs                     # File system module, which mainly derives from the NuttX open-source project
│   ├── fat                # FAT file system
│   ├── jffs2              # JFFS2 file system
│   ├── include            # Header files exposed externally
│   ├── nfs                # NFS file system
│   ├── proc               # proc file system
│   ├── ramfs              # RAMFS file system
│   └── vfs                # VFS layer
├── kernel                 # Kernel modules including the process, memory, and IPC modules
│   ├── base               # Basic kernel modules including the scheduling and memory modules
│   ├── common             # Common components used by the kernel
│   ├── extended           # Extended kernel modules including the dynamic loading, vDSO, and LiteIPC modules
│   ├── include            # Header files exposed externally
│   └── user               # Init process loading
├── lib                    # Kernel library
├── net                    # Network module, which mainly derives from the lwIP open-source project
├── platform               # Code for supporting different systems on a chip (SOCs), such as Hi3516D V300
│   ├── hw                 # Logic code related to clocks and interrupts
│   ├── include            # Header files exposed externally
│   └── uart               # Logic code related to the serial port
├── platform               # Code for supporting different systems on a chip (SOCs), such as Hi3516D V300
├── security               # Code related to security features, including process permission management and virtual ID mapping management
├── syscall                # System calling
└── tools                  # Building tools as well as related configuration and code

Constraints

  • Programming languages: C and C++
  • Applicable development boards: Hi3518E V300 and Hi3516D V300
  • Hi3518E V300 uses the JFFS2 file system by default, and Hi3516D V300 uses the FAT file system by default.

Usage

OpenHarmony LiteOS Cortex-A supports the Hi3518E V300 and Hi3516D V300. You can develop and run your applications based on both development boards.

Preparations

You need to set up the compilation environment on Linux.

Source Code Acquisition

Download and decompress a set of source code on a Linux server to acquire the source code.

Compilation and Building

For details about how to develop the first application, see:

Repositories Involved

Kernel subsystem

drivers_liteos

kernel_liteos_a