diff --git a/adr/0002-use-yocto-bitbake-for-building-ohos.md b/adr/0002-use-yocto-bitbake-for-building-ohos.md
new file mode 100644
index 0000000000000000000000000000000000000000..d7eea24cce3c41e010738fe05ec0e63f7e3a4b60
--- /dev/null
+++ b/adr/0002-use-yocto-bitbake-for-building-ohos.md
@@ -0,0 +1,32 @@
+# 2. Use Yocto / bitbake for building OHOS
+
+Date: 2020-12-01
+
+## Status
+
+Accepted
+
+## Context
+
+OHOS as a distributed operating system is designed to be hosted on 
+top of OS kernel. Currently Liteos-a (targeting ARM Cortex-A based devices) 
+and Liteos-m (targeting ARM Cortex-M based devices) kernels are supported.
+
+OHOS Liteos-A has BSP for only two ip cameras devices, whereas Liteos-M
+has BSP for only one wifi iot device. Qemu support is missing.
+
+## Decision
+
+To leverage existing BSPs OHOS will be made compatible with Yocto.
+We will start with Linux Poky distribution for ARM Cortex-A based devices
+and Zephyr for the Cortex-M based devices.
+
+## Consequences
+
+meta-ohos layer (when done properly) will enable nearly effortless porting 
+of OHOS to new kernels / distros.
+
+Decoupling of existing OHOS services from Liteos-A/M kernels has to be done.
+
+HQ modification to the OHOS stack between releases can require repeating
+decoupling works with each and every release if we're not aligned and in sync.
diff --git a/adr/adr-list.md b/adr/adr-list.md
index babe641e8e6388023ed58693673486d9f7677f16..dfa4d941792bb5833ecd215785ae7522078e5b41 100644
--- a/adr/adr-list.md
+++ b/adr/adr-list.md
@@ -1,3 +1,4 @@
 # Architecture Decision Records
 
 * [1. Record architecture decisions](0001-record-architecture-decisions.md)
+* [2. Use Yocto / bitbake for building OHOS](0002-use-yocto-bitbake-for-building-ohos.md)