8 files changed, 0 insertions, 913 deletions
diff --git a/docs/howto/BuildTFfromSource.md b/docs/howto/BuildTFfromSource.md
deleted file mode 100644
index 3880d5ab9..000000000
--- a/docs/howto/BuildTFfromSource.md
+++ /dev/null
@@ -1,66 +0,0 @@
-# Building TensorFlow and TOCO from source
-
-You can build TensorFlow and tools including `TOCO` from source.
-Please read
-[Installing TensorFlow from Sources](https://www.tensorflow.org/install/install_sources)
-for full description.
-
-## Install Bazel
-
-Follow [Installing Bazel](https://docs.bazel.build/versions/master/install.html)
-- For Ubuntu, follow [Installing Bazel on Ubuntu](https://docs.bazel.build/versions/master/install-ubuntu.html)
-
-These are the actual steps to install using apt package manager:
-```
-sudo apt-get install openjdk-8-jdk
-```
-```
-echo "deb [arch=amd64] http://storage.googleapis.com/bazel-apt stable jdk1.8" \
-| sudo tee /etc/apt/sources.list.d/bazel.list
-curl https://bazel.build/bazel-release.pub.gpg | sudo apt-key add -
-```
-```
-sudo apt-get update && sudo apt-get install bazel
-```
-```
-sudo apt-get upgrade bazel
-```
-
-## Install python packages
-
-```
-sudo apt-get install python-numpy python-dev python-pip python-wheel
-```
-
-## Configure
-
-```
-cd external/tensorflow
-./configure
-```
-
-Select options like this page: https://www.tensorflow.org/install/install_sources#ConfigureInstallation
-
-## Build with Bazel
-
-```
-bazel build --config=opt //tensorflow/tools/pip_package:build_pip_package
-bazel-bin/tensorflow/tools/pip_package/build_pip_package /tmp/tensorflow_pkg
-```
-
-If you have any problems while building, please fire an issue.
-
-## Uninstall if already installed
-
-You may skip this if you haven't installed
-```
-pip uninstall /tmp/tensorflow_pkg/tensorflow-1.6.0rc1-cp27-cp27mu-linux_x86_64.whl
-```
-
-## Install TensorFlow and tools
-
-```
-pip install /tmp/tensorflow_pkg/tensorflow-1.6.0rc1-cp27-cp27mu-linux_x86_64.whl --user
-```
-
-You should see installed `toco` at `~/.local/bin` folder.
diff --git a/docs/howto/CrossBuildForAarch64.md b/docs/howto/CrossBuildForAarch64.md
deleted file mode 100644
index f3dc55236..000000000
--- a/docs/howto/CrossBuildForAarch64.md
+++ /dev/null
@@ -1,81 +0,0 @@
-# Cross building for AARCH64
-
-In nnfw, we use both `ARM64` and `AARCH64` on build files such as Makefile, CMakeLists.txt and so on.
-- `ARM64`: only for Android
-- `AARCH64`: all except for Android
-
-However we use only one term `ARM64` in RootFS. Use `ARM64` if you need a RootFS for `AARCH64`.
-
-## Prepare Ubuntu RootFS
-
-Install required packages
-
-```
-sudo apt-get install qemu qemu-user-static binfmt-support debootstrap
-```
-
-Use `build_rootfs.sh` script to prepare Root File System. You should have `sudo`
-
-```
-sudo ./tools/cross/build_rootfs.sh arm64
-```
-- supports `arm`(default) and `arm64` architecutre for now
-- supports `xenial`(default) and `trusty` release
-
-To see the options,
-```
-./tools/cross/build_rootfs.sh -h
-```
-
-RootFS will be prepared at `tools/cross/rootfs/arm64` folder.
-
-### Prepare RootFS at alternative folder
-
-Use `ROOTFS_DIR` to a full path to prepare at alternative path.
-
-```
-ROOTFS_DIR=/home/user/rootfs/arm64-xenial sudo ./tools/cross/build_rootfs.sh arm64
-```
-
-### Using proxy
-
-If you need to use proxy server while building the rootfs, use `--setproxy` option.
-
-```
-# for example,
-sudo ./tools/cross/build_rootfs.sh arm64 --setproxy="1.2.3.4:8080"
-# or
-sudo ./tools/cross/build_rootfs.sh arm64 --setproxy="proxy.server.com:8888"
-```
-
-This will put `apt` proxy settings in `rootfs/etc/apt/apt.conf.d/90proxy` file
-for `http`, `https` and `ftp` protocol.
-
-## Cross build for AARCH64
-
-Install cross compilers
-```
-sudo apt-get install gcc-aarch64-linux-gnu g++-aarch64-linux-gnu
-```
-
-Build and install ARM Compute Library
-```
-CROSS_BUILD=1 TARGET_ARCH=aarch64 make acl
-```
-Mostly you only need once of ACL build. This will build and install to
-`Product/(target_arch-os)/out/bin` folder.
-- this is required for `AARCH64` on Ubuntu
-
-Give `TARGET_ARCH` variable to set the target architecture
-```
-CROSS_BUILD=1 TARGET_ARCH=aarch64 make
-CROSS_BUILD=1 TARGET_ARCH=aarch64 make install
-```
-- supports `armv7l` and `aarch64` for now
-
-If you used `ROOTFS_DIR` to prepare in alternative folder,
-you should also give this to makefile.
-```
-CROSS_BUILD=1 ROOTFS_DIR=/home/user/rootfs/arm64-xenial TARGET_ARCH=aarch64 make
-CROSS_BUILD=1 ROOTFS_DIR=/home/user/rootfs/arm64-xenial TARGET_ARCH=aarch64 make install
-```
diff --git a/docs/howto/CrossBuildForArm.md b/docs/howto/CrossBuildForArm.md
deleted file mode 100644
index e307596d0..000000000
--- a/docs/howto/CrossBuildForArm.md
+++ /dev/null
@@ -1,107 +0,0 @@
-# Cross building for ARM
-
-## Prepare Ubuntu RootFS
-
-Install required packages
-
-```
-sudo apt-get install qemu qemu-user-static binfmt-support debootstrap
-```
-
-Use `build_rootfs.sh` script to prepare Root File System. You should have `sudo`
-
-```
-sudo ./tools/cross/build_rootfs.sh arm
-```
-- supports `arm`(default) and `arm64` architecutre for now
-- supports `xenial`(default) and `trusty` release
-
-To see the options,
-```
-./tools/cross/build_rootfs.sh -h
-```
-
-RootFS will be prepared at `tools/cross/rootfs/arm` folder.
-
-## Prepare RootFS at alternative folder
-
-Use `ROOTFS_DIR` to a full path to prepare at alternative path.
-
-```
-ROOTFS_DIR=/home/user/rootfs/arm-xenial sudo ./tools/cross/build_rootfs.sh arm
-```
-
-## Using proxy
-
-If you need to use proxy server while building the rootfs, use `--setproxy` option.
-
-```
-# for example,
-sudo ./tools/cross/build_rootfs.sh arm --setproxy="1.2.3.4:8080"
-# or
-sudo ./tools/cross/build_rootfs.sh arm --setproxy="proxy.server.com:8888"
-```
-
-This will put `apt` proxy settings in `rootfs/etc/apt/apt.conf.d/90proxy` file
-for `http`, `https` and `ftp` protocol.
-
-## Install ARM Cross Toolchain
-
-We recommend you have g++ >= 6 installed on your system because NN generated tests require it.
-
-On Ubuntu 16.04 or older, follow the next steps:
-
-```
-cd ~/your/path
-wget https://releases.linaro.org/components/toolchain/binaries/7.2-2017.11/arm-linux-gnueabihf/gcc-linaro-7.2.1-2017.11-x86_64_arm-linux-gnueabihf.tar.xz
-tar xvf gcc-linaro-7.2.1-2017.11-x86_64_arm-linux-gnueabihf.tar.xz
-echo 'PATH=~/your/path/gcc-linaro-7.2.1-2017.11-x86_64_arm-linux-gnueabihf/bin:$PATH' >> ~/.bashrc
-```
-
-On Ubuntu 18.04 LTS, you can install using `apt-get`.
-Choose g++ version whatever you prefer: 6, 7 or 8.
-
-```
-sudo apt-get install g++-{6,7,8}-arm-linux-gnueabihf
-```
-
-Make sure you get `libstdc++.so` updated on your target with your new toolchain's corresponding one.
-
-For example, if you installed gcc-linaro-7.2.1-2017.11 above, do
-
-```
-wget https://releases.linaro.org/components/toolchain/binaries/7.2-2017.11/arm-linux-gnueabihf/runtime-gcc-linaro-7.2.1-2017.11-arm-linux-gnueabihf.tar.xz
-tar xvf runtime-gcc-linaro-7.2.1-2017.11-arm-linux-gnueabihf.tar.xz
-```
-
-Then, copy `libstdc++.so.6.0.24` into `/usr/lib/arm-linux-gnueabihf`, and update symbolic links on your device.
-
-## Build and install ARM Compute Library
-
-```
-CROSS_BUILD=1 TARGET_ARCH=armv7l make acl
-```
-Mostly you only need once of ACL build. This will build and install to `Product/(target_arch-os)/out/bin` folder.
-- this is required for ARM on Ubuntu
-
-## Build nnfw
-
-Give `TARGET_ARCH` variable to set the target architecture
-
-```
-CROSS_BUILD=1 TARGET_ARCH=armv7l make all install
-```
-- supports `armv7l` and `aarch64` for now
-
-If you used `ROOTFS_DIR` to prepare in alternative folder, you should also give this to makefile.
-
-```
-ROOTFS_DIR=ROOTFS_ARM=/path/to/your/rootfs/arm \
-CROSS_BUILD=1 TARGET_ARCH=armv7l make all install
-```
-
-## Run test
-
-```
- ./tests/scripts/test_driver.sh --artifactpath=.
-```
diff --git a/docs/howto/HowToAddUnittest.md b/docs/howto/HowToAddUnittest.md
deleted file mode 100644
index 5bb75b258..000000000
--- a/docs/howto/HowToAddUnittest.md
+++ /dev/null
@@ -1,31 +0,0 @@
-# How to Add Unittest using gtest(googletest)
-
-### 1. make own test code
-```
-#include "gtest/gtest.h"
-
-TEST(TFLite_test_case, simple_test)
-{
-    EXPECT_EQ(1, 1);
-}
-```
-
-### 2. Find and prepare package `googletest` to your test executable
-```
-find_nnfw_package(GTest QUITE)
-if(NOT GTest_FOUND)
-  ## Cannot find and prepare googletest package
-  return()
-endif(NOT GTest_FOUND)
-add_executable($YOURTEST_TARGET yourtest1.cc yourtest2.cc)
-```
-
-### 3. Link test executable against libgtest.a and libgtest_main.a (+ pthread)
-```
-target_link_libraries($YOURTEST_TARGET gtest gtest_main pthread)
-```
-
-### 4. Install test executable into Product/out/unittest
-```
-install(TARGETS $YOURTEST_TARGET DESTINATION unittest)
-```
diff --git a/docs/howto/HowToUseDockerImage.md b/docs/howto/HowToUseDockerImage.md
deleted file mode 100644
index a28502cf0..000000000
--- a/docs/howto/HowToUseDockerImage.md
+++ /dev/null
@@ -1,168 +0,0 @@
-# How to use docker image of nnfw
-
-We have a docker image to build `nnfw` repo.
-
-This docker image is built from https://github.sec.samsung.net/STAR/nnfw/blob/master/docker/Dockerfile and based on Ubuntu 16.04.
-And prebuilt docker image is available from Samsung private docker registry.
-
-This document describes how to use prebuilt docker image when developing `nnfw`.
-
-## How to install docker
-
-Follow [Installing Docker](https://docs.docker.com/)
-
-- For Ubuntu, follow [Installing Docker on Ubuntu](https://docs.docker.com/install/linux/docker-ce/ubuntu/)
-
-These are the actual steps to install using apt package manager:
-```
-$ sudo apt-get install \
-     apt-transport-https \
-     ca-certificates \
-     curl \
-     software-properties-common
-$ curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo apt-key add -
-$ sudo apt-key fingerprint 0EBFCD88
-```
-```
-$ sudo add-apt-repository \
-     "deb [arch=amd64] https://download.docker.com/linux/ubuntu \
-     $(lsb_release -cs) \
-	 stable"
-$ sudo apt-get update
-```
-```
-$ sudo apt-get install docker-ce
-```
-
-## Configure docker daemon
-
-1. Set HTTP/HTTPS proxy
-
-    * For Ubuntu, follow [Setting HTTP/HTTPS proxy environment variables](https://docs.docker.com/v17.09/engine/admin/systemd/#httphttps-proxy)
-
-If you are behind an HTTP or HTTPS proxy server, you will need to add this configuration in the Docker systemd service file.
-These are the actual steps to set an HTTP/HTTPS proxy environment variable:
-```
-$ sudo mkdir -p /etc/systemd/system/docker.service.d
-$ sudo vi etc/systemd/system/docker.service.d/http-proxy.conf
-```
-```
-[Service]
-Environment="HTTP_PROXY=http://10.112.1.184:8080/" "HTTPS_PROXY=https://10.112.1.184:8080/" "NO_PROXY=localhost,127.0.0.1"
-```
-```
-$ sudo systemctl daemon-reload
-$ sudo systemctl restart docker
-$ systemctl show --property=Environment docker
-```
-
-2. Edit configuration file of docker daemon
-
-First you have to add Samsung private docker reigstry to your docker daemon.
-Depending on your docker daemon installed, there are two ways of configuration.
-
-
-If there is a `/etc/default/docker`, please edit the file as below.
-```
-$ sudo vi /etc/default/docker
-
-DOCKER_OPTS="--insecure-registry docker.sec.samsung.net:5000"
-```
-
-If there is a `/etc/docker/daemon.json`, please edit the file as below.
-```
-{
-  ...,
-  "insecure-registries": [..., "docker.sec.samsung.net:5000"]
-}
-```
-
-3. Then restart docker daemon as below.
-
-```
-$ sudo service docker restart     // Ubuntu 14.04
-
-or
-
-$ sudo systemctl restart docker   // Ubuntu 16.04
-```
-
-## Install docker image of `nnfw`
-
-Let's pull docker image for `nnfw` repo and tag it to `nnfw_docker:latest`
-
-```
-$ docker pull docker.sec.samsung.net:5000/star/nnfw/nnfw_docker:1.5
-$ docker tag docker.sec.samsung.net:5000/star/nnfw/nnfw_docker:1.5 nnfw_docker:latest
-```
-
-If you would like to build `nnfw` tizen package using gbs, pull `nnfw_docker_tizen`.
-```
-$ docker pull docker.sec.samsung.net:5000/star/nnfw/nnfw_docker_tizen:1.2
-$ docker tag docker.sec.samsung.net:5000/star/nnfw/nnfw_docker_tizen:1.2 nnfw_docker_tizen:latest
-```
-
-## Build docker image instead of pull
-
-You can build docker image in your environment instead of pull docker image from server.
-
-```
-$ cd nnfw
-$ ./run build-docker
-```
-
-Default docker image name is `nnfw_docker`. If you want to change image name and/or tag, use `-t` or `--tag` option
-
-```
-$ cd nnfw
-$ ./run build-docker -t nnfw_docker_test
-```
-
-You can use options supported by `docker build` command (ex. `--network` option)
-
-```
-$ cd nnfw
-$ ./run build-docker --network=host --no-cache
-```
-
-If you want to build docker image for tizen build, use `--tizen` option
-
-```
-```
-$ cd nnfw
-$ ./run build-docker --tizen
-```
-```
-
-
-## Use docker image to build `nnfw`
-Three different targets for `nnfw` can be built using docker image.
-
-1. Build `nnfw` for `x86_64` target
-```
-$ cd nnfw
-$ docker run --rm -v $(pwd):/opt/nnfw -w /opt/nnfw nnfw_docker make install
-```
-or use `docker_run_test.sh` for convenience as below.
-```
-$ cd nnfw
-$ ./run docker_run_test.sh
-```
-You can find built artifacts at `nnfw/Product/x86_64-linux.debug`.
-
-2. Cross build `nnfw` for ARM on x86_64 host
-
-You should prepare RootFS, following [Cross Building for ARM](https://github.sec.samsung.net/STAR/nnfw/blob/master/docs/howto/CrossBuildForArm.md) except ACL build and cross build steps. Then execute below commands. If your RootFS directory is different with below directory, change it to correct path and ensure the path is absolute.
-```
-$ cd nnfw
-$ ROOTFS_DIR=$(pwd)/tools/cross/rootfs/arm \
-./run docker_build_cross_arm_ubuntu.sh
-```
-You can find built artifacts at `nnfw/Product/armv7l-linux.debug/`.
-
-3. Build `nnfw` for Tizen ARM package on x86_64 host
-```
-$ cd nnfw
-$ ./run docker_gbs_build.sh
-```
-You can find built artifacts at `Product/out/rpm`.
diff --git a/docs/howto/device/xu3_ubuntu.md b/docs/howto/device/xu3_ubuntu.md
deleted file mode 100644
index 38dbc69b0..000000000
--- a/docs/howto/device/xu3_ubuntu.md
+++ /dev/null
@@ -1,114 +0,0 @@
-## How to setup XU3 with Ubuntu 16.04
-
-Ref: https://wiki.odroid.com/old_product/odroid-xu3/odroid-xu3
-
-MicroSD card images
-- https://dn.odroid.com/5422/ODROID-XU3/Ubuntu/
-
-Latest image (as of writing this file)
-- https://dn.odroid.com/5422/ODROID-XU3/Ubuntu/ubuntu-16.04.3-4.14-minimal-odroid-xu4-20171213.img.xz
-- Flash with `WinFlashTool`
-
-MicroSD boot DIP settings
-- ![image](xu3-dip.png)
-
-SW1-1,2 | 1st Boot media
--- | --
-ON ON | eMMC
-OFF ON | MicroSD card
-
-Boot
-- login with serial console
-- password: `root`/`odroid`
-
-Set ethernet
-`/etc/network/interfaces`
-```
-# interfaces(5) file used by ifup(8) and ifdown(8)
-# Include files from /etc/network/interfaces.d:
-source-directory /etc/network/interfaces.d
-
-auto lo eth0
-iface lo inet loopback
-
-iface eth0 inet static
-	address 10.113.xxx.yyy
-	netmask 255.255.255.0
-	network 10.113.xxx.0
-	broadcast 10.113.xxx.255
-	gateway 10.113.xxx.1
-	dns-nameservers 10.32.192.11 10.32.193.11 8.8.8.8
-```
-Change `xxx.yyy` to your IP address.
-
-Reboot and login with SSH
-
-### Add proxy settings
-
-Add `/etc/apt/apt.conf.d/90proxies`
-```
-Acquire::http::proxy "http://10.112.1.184:8080/";
-Acquire::https::proxy "http://10.112.1.184:8080/";
-Acquire::ftp::proxy "ftp://10.112.1.184:8080/";
-```
-
-Add `/etc/profile.d/proxy.sh`
-```
-#!/bin/bash
-
-# Proxy
-export HTTP_PROXY=http://10.112.1.184:8080/
-export HTTPS_PROXY=https://10.112.1.184:8080/
-```
-
-### Update and install programs
-
-```
-sudo apt-get update
-sudo apt-get upgrade
-sudo apt-get install vim nfs-common
-```
-
-### For convenience
-
-Edit `~/.profile`
-```
-export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:.
-```
-
-### MALI GPU driver
-
-https://developer.arm.com/products/software/mali-drivers/user-space
-
-Download at `Odroid-XU3` section
-- https://developer.arm.com/-/media/Files/downloads/mali-drivers/user-space/odroid-xu3/malit62xr12p004rel0linux1fbdev.tar.gz?revision=b4f9b859-ac02-408e-9729-c1e50d3a9c6c
-
-Extract and copy to `/usr/lib/fbdev`
-
-File list
-```
-$ll /usr/lib/fbdev/
-
-total 22520
-drwxr-xr-x  2 root root     4096 Feb 21 02:35 ./
-drwxr-xr-x 57 root root     4096 Feb 21 08:33 ../
-lrwxrwxrwx  1 root root       11 Feb 21 02:35 libEGL.so -> libEGL.so.1*
-lrwxrwxrwx  1 root root       10 Feb 21 02:35 libEGL.so.1 -> libmali.so*
-lrwxrwxrwx  1 root root       17 Feb 21 02:35 libGLESv1_CM.so -> libGLESv1_CM.so.1*
-lrwxrwxrwx  1 root root       10 Feb 21 02:35 libGLESv1_CM.so.1 -> libmali.so*
-lrwxrwxrwx  1 root root       14 Feb 21 02:35 libGLESv2.so -> libGLESv2.so.2*
-lrwxrwxrwx  1 root root       10 Feb 21 02:35 libGLESv2.so.2 -> libmali.so*
-lrwxrwxrwx  1 root root       14 Feb 21 02:35 libOpenCL.so -> libOpenCL.so.1*
-lrwxrwxrwx  1 root root       10 Feb 21 02:35 libOpenCL.so.1 -> libmali.so*
--rwxr-xr-x  1 root root 21471208 Feb 21 02:35 libmali.so*
--rwxr-xr-x  1 root root  1580048 Feb 21 02:35 liboffline_compiler_api.so*
-```
-
-Add `/etc/ld.so.conf.d/malifbdev.conf`
-```
-# arm mali
-/usr/lib/fbdev
-```
-
-Rename `arm-linux-gnueabihf_EGL.conf` to `arm-linux-gnueabihf_EGL.conf.not`
-- This is to disable mesa (software emulator of EGL)
diff --git a/docs/howto/device/xu4_tizen.md b/docs/howto/device/xu4_tizen.md
deleted file mode 100644
index 3481be206..000000000
--- a/docs/howto/device/xu4_tizen.md
+++ /dev/null
@@ -1,247 +0,0 @@
-# About
-
-This will describe how to flash microSD with Tizen-4.0 for ODroid XU4.
-
-Host environment is Ubuntu 16.04
-
-# Download files
-
-## Images
-
-Boot
-- https://download.tizen.org/snapshots/tizen/unified/latest/images/standard/tv-boot-armv7l-odroidxu3/
-- download the biggest file
-
-Root FS
-- https://download.tizen.org/snapshots/tizen/unified/latest/images/standard/tv-wayland-armv7l-odroidu3/
-- download the biggest file
-
-U-Boot images
-```
-wget https://github.com/hardkernel/u-boot/raw/odroidxu3-v2012.07/sd_fuse/hardkernel_1mb_uboot/bl1.bin.hardkernel
-wget https://github.com/hardkernel/u-boot/raw/odroidxu3-v2012.07/sd_fuse/hardkernel_1mb_uboot/bl2.bin.hardkernel.1mb_uboot
-wget https://github.com/hardkernel/u-boot/raw/odroidxu3-v2012.07/sd_fuse/hardkernel_1mb_uboot/tzsw.bin.hardkernel
-```
-
-You also need `u-boot-mmc.bin` that is inside `tizen-unified_20180425.2_tv-boot-armv7l-odroidxu3.tar.gz` file.
-```
-tar xvf tizen-unified_20180425.2_tv-boot-armv7l-odroidxu3.tar.gz u-boot-mmc.bin
-```
-
-
-## Flashing script
-
-Download `sd_fusing_xu4-u1604.sh` from https://github.sec.samsung.net/RS7-RuntimeNTools/TizenTools/tree/master/sd_fusing_xu4
-
-This file is modified to work on Ubuntu 16.04.
-
-You can download original (What I got in the first place) file as `sd_fusing_xu4.sh`
-
-Make it executable
-```
-chmod u+x sd_fusing_xu4-u1604.sh
-```
-
-
-## Files
-
-You should see like this
-```
--rw-rw-r-- 1 maxwell maxwell     15616 Mar 23 17:11 bl1.bin.hardkernel
--rw-rw-r-- 1 maxwell maxwell     14592 Mar 23 17:10 bl2.bin.hardkernel.1mb_uboot
--rw-rw-r-- 1 maxwell maxwell   9290646 Apr 26 02:35 tizen-unified_20180425.2_tv-boot-armv7l-odroidxu3.tar.gz
--rw-rw-r-- 1 maxwell maxwell 346530499 Apr 26 02:59 tizen-unified_20180425.2_tv-wayland-armv7l-odroidu3.tar.gz
--rw-rw-r-- 1 maxwell maxwell    262144 Mar 23 17:11 tzsw.bin.hardkernel
--rwxr-xr-x 1 maxwell maxwell   1048576 Apr 26 02:35 u-boot-mmc.bin*
-```
-
-
-# Flash
-
-Host environment
-- Ubuntu 16.04
-- microSD connected through USB Reader as `/dev/sdd` file.
-
-## Flash boot files
-
-Give `--format` if it's a new flash memory.
-```
-sudo ./sd_fusing_xu4-u1604.sh --format \
--d /dev/sdd \
--b bl1.bin.hardkernel bl2.bin.hardkernel.1mb_uboot tzsw.bin.hardkernel u-boot-mmc.bin
-```
-Change `/dev/sdd` to your configuration.
-
-You will be asked to confirm format when used `--format`. Please type `y` to continue.
-```
-/dev/sdd will be formatted, Is it OK? [y/n]
-y
-```
-
-You can omit `--format` from the second time and followings.
-```
-sudo ./sd_fusing_xu4-u1604.sh \
--d /dev/sdd \
--b bl1.bin.hardkernel bl2.bin.hardkernel.1mb_uboot tzsw.bin.hardkernel u-boot-mmc.bin
-```
-`--format` option will, 1) delete current partition 2) create new partition table, 3) format each partitions.
-
-- If you meet `./sd_fusing_xu4-u1604.sh: line 147: pv: command not found` message and want to remove this message, install pv package by `sudo apt-get install pv`
-
-## Flash image files
-```
-sudo ./sd_fusing_xu4-u1604.sh -d /dev/sdd \
--b tizen-unified_20180425.2_tv-boot-armv7l-odroidxu3.tar.gz \
-tizen-unified_20180425.2_tv-wayland-armv7l-odroidu3.tar.gz
-```
-
-# Boot with Tizen 4.0
-
-Follow the steps
-
-Step 1.
-- Take out eMMC memory card if you have any
-
-Step 2. 
-- Plug-In microSD with Tizen 4.0
-
-Step 3. Set boot switch
-- Refer https://wiki.odroid.com/odroid-xu4/hardware/hardware
-- Set `Boot mode selector` switch on the bottom of the board to `uSD`
-
-Step 4. Connect Serial Console port with USB of Host computer
-- Install `minicom`
-```
-sudo apt-get install minicom
-```
-- Add yourself to the group `dialout`
-   - `sudo vi /etc/group`
-- Use serial terminal program like `minicom` (note that `/dev/ttyUSB1` might be different in your environment.)
-```
-minicom --baudrate 115200 --device /dev/ttyUSB1
-```
-- Use `CTRL-a z o` > `Serial port setup` to enter the dialog
-- Baud should be `115200-8N1`
-- Set configuration `Hardware Flow Control` to `No` to enable communication(keyboard typing..)
-- `Save setup as dfl` in configuration
-- If you are connecting from Windows or Mac my need to install the driver
-   - https://www.silabs.com/products/development-tools/software/usb-to-uart-bridge-vcp-drivers
-   - Use `PuTTY` for Windows.
-
-Step 5. Connect Power
-- You should see the boot logs...
-
-Step 6. Login root
-- login `root` pwd `tizen`
-
-# After boot
-
-## Slow down the fan speed
-
-If the fan noise is disturbing, you can slow down a little.
-
-```
-echo "100" > /sys/devices/platform/pwm-fan/hwmon/hwmon0/pwm1
-```
-This will slow down the speed to 100. Range is from 0 to 255. "0" to make it stop. "255" for maximum speed.
-
-This value resets after reboot so may have to set the value every time you reboot.
-
-## Expand root file system
-
-Default Root FS is 3G but the size shows about the size of the image file, about 700MB.
-
-There would be not enough space to install files. To overcome this do the following in Tizen root shell.
-
-```
-mount -o remount,rw /
-resize2fs /dev/mmcblk0p2
-sync
-```
-And reboot
-```
-reboot
-```
-
-`df` before and after
-```
-Filesystem           1K-blocks      Used Available Use% Mounted on
-/dev/root               754716    721228      8764  99% /
-```
-to
-```
-Filesystem           1K-blocks      Used Available Use% Mounted on
-/dev/root              3031952    724724   2282504  25% /
-```
-
-
-## Wide console
-
-```
-stty cols 200
-```
-
-## Setting IP Address of Target Device
-
-Use `connmanctl`
-
-**CAUTION** PLEASE DO THIS IN YOUR TARGET DEVICE. RUNNING THIS IN YOUR HOST MAY DAMAGE.
-
-Step 1. Get the service name
-- You first need to connect Ethernet cable.
-```
-connmanctl services
-```
-Will drop something like this
-```
-*AR Wired                ethernet_1a43230d5dfa_cable
-```
-
-Step 2. Use `config` to set the IP address
-```
-connmanctl config ethernet_1a43230d5dfa_cable --ipv4 manual 10.113.XXX.YYY 255.255.255.0 10.113.XXX.1
-connmanctl config ethernet_1a43230d5dfa_cable --nameservers 10.32.192.11 10.32.193.11
-```
-where `XXX.YYY` is your address for the target board.
-
-Setting for proxy can be done with connmanctl but don't know how to check.
-```
-connmanctl config ethernet_1a43230d5dfa_cable --proxy manual http://10.112.1.184:8080/
-```
-You can use environment variable but still don't know how to check.
-
-
-This information remains after reboot.
-
-# Connecting with SDB
-
-Default Tizen image has running SDBD in the device with default port (26101).
-
-In your Linux or Windows with `sdb` command,
-```
-sdb connect 10.113.XXX.YYY
-```
-Result will be something like
-```
-* Server is not running. Start it now on port 26099 *
-* Server has started successfully *
-connecting to 10.113.xxx.yyy:26101 ...
-connected to 10.113.xxx.yyy:26101
-```
-With `sdb devices`,
-```
-sdb devices
-List of devices attached 
-10.113.xxx.yyy:26101  	device    	xu3
-```
-It comes up with `xu3` as our `xu4` also uses same image `xu3` image.
-
-
-# Known issue
-- `ls -al` of root folder shows strange output.
-
-# Reference
-- https://wiki.tizen.org/Quick_guide_for_odroidxu4
-- and the mail got from "김석원님"
-- https://magazine.odroid.com/wp-content/uploads/odroid-xu4-user-manual.pdf
-   - https://magazine.odroid.com/odroid-xu4
diff --git a/docs/howto/device/xu4_ubuntu.md b/docs/howto/device/xu4_ubuntu.md
deleted file mode 100644
index 7b8a3aa2b..000000000
--- a/docs/howto/device/xu4_ubuntu.md
+++ /dev/null
@@ -1,99 +0,0 @@
-## How to use XU4 with Ubuntu 16.04
-
-Ref: https://wiki.odroid.com/odroid-xu4/odroid-xu4
-
-eMMC card pre-installed Ubuntu 16.04
-
-Preparation for IO via serial cable
-- Refer to `minicom` section in xu4_tizen.md
-- To find the name of serial device, plug your odroid into your host machine and power it on. Then, run the following on your host:
-	```
-	$ dmesg | grep tty
-	[    0.000000] console [tty0] enabled
-	[322282.017985] usb 2-1: cp210x converter now attached to ttyUSB0
-	```
-- Use `CTRL-a z o` > `Serial port setup` to enter the dialog
-- Set configuration `Serial Device` to `/dev/ttyUSB0` for the name of serial device
-- Baud should be `115200-8N1`
-- Set configuration `Hardware Flow Control` to `No` to enable communication(keyboard typing..)
-
-Connect
-- Connect eMMC to bottom of the board
-- Connect Serial Console to Host USB
-- Connect power and boot
-
-Login with serial console. you can login with `root` or default `odroid` account
-- `root` password: `odroid`
-- `odroid `password: `odroid`
-
-Set ethernet
-`/etc/network/interfaces`
-```
-# interfaces(5) file used by ifup(8) and ifdown(8)
-# Include files from /etc/network/interfaces.d:
-source-directory /etc/network/interfaces.d
-
-auto lo eth0
-iface lo inet loopback
-
-iface eth0 inet static
-	address 10.113.xxx.yyy
-	netmask 255.255.255.0
-	network 10.113.xxx.0
-	broadcast 10.113.xxx.255
-	gateway 10.113.xxx.1
-	dns-nameservers 10.32.192.11 10.32.193.11 8.8.8.8
-```
-Change `xxx.yyy` to your IP address.
-
-Reboot and login with SSH
-
-### Add proxy settings
-
-Add `/etc/apt/apt.conf.d/90proxies`
-```
-Acquire::http::proxy "http://10.112.1.184:8080/";
-Acquire::https::proxy "http://10.112.1.184:8080/";
-Acquire::ftp::proxy "ftp://10.112.1.184:8080/";
-```
-
-Add `/etc/profile.d/proxy.sh`
-```
-#!/bin/bash
-
-# Proxy
-export HTTP_PROXY=http://10.112.1.184:8080/
-export HTTPS_PROXY=https://10.112.1.184:8080/
-```
-
-### Update and install programs
-
-```
-sudo apt-get update
-sudo apt-get upgrade
-sudo apt-get install vim nfs-common
-```
-
-### MALI GPU driver
-
-Driver files are pre-installed in eMMC as follows
-```
-odroid@odroid:/usr/lib/arm-linux-gnueabihf/mali-egl$ ll
-total 20136
-drwxr-xr-x   2 root root     4096 Aug 20  2017 ./
-drwxr-xr-x 106 root root    90112 Mar 26 08:32 ../
--rw-r--r--   1 root root       38 Apr 30  2017 ld.so.conf
--rwxr-xr-x   1 root root     2752 Apr 30  2017 libEGL.so*
-lrwxrwxrwx   1 root root        9 Apr 30  2017 libEGL.so.1 -> libEGL.so*
-lrwxrwxrwx   1 root root        9 Apr 30  2017 libEGL.so.1.4 -> libEGL.so*
--rwxr-xr-x   1 root root     2752 Apr 30  2017 libGLESv1_CM.so*
-lrwxrwxrwx   1 root root       15 Apr 30  2017 libGLESv1_CM.so.1 -> libGLESv1_CM.so*
-lrwxrwxrwx   1 root root       15 Apr 30  2017 libGLESv1_CM.so.1.1 -> libGLESv1_CM.so*
--rwxr-xr-x   1 root root     2752 Apr 30  2017 libGLESv2.so*
-lrwxrwxrwx   1 root root       12 Apr 30  2017 libGLESv2.so.2 -> libGLESv2.so*
-lrwxrwxrwx   1 root root       12 Apr 30  2017 libGLESv2.so.2.0 -> libGLESv2.so*
--rwxr-xr-x   1 root root 20493444 May  8  2017 libmali.so*
--rwxr-xr-x   1 root root     2752 Apr 30  2017 libOpenCL.so*
-lrwxrwxrwx   1 root root       12 Apr 30  2017 libOpenCL.so.1 -> libOpenCL.so*
-lrwxrwxrwx   1 root root       12 Apr 30  2017 libOpenCL.so.1.1 -> libOpenCL.so*
-```