easygraphics

SystemD issue

Onionfra — Wed, 30 Oct 2019 08:53:23 +0900

systemd는 /etc/systemd 아래에 설정파일을 두고 있다

시스템에 미리 정의 된 Service, Target 파일을 통해서 시스템을 컨트롤

/etc/systemd에서 설정하면서 심볼릭 링크를 통해서 사용

바이너리 실행파일은 아래 경로에서 확인 가능하며

$ ls /lib/systemd/

기본적인 시스템의 Service, Target은 아래에 위치하고 있다

$ ls /lib/systemd/system

ls -al /etc/systemd/system/multi-user.target.wants

remote-fs.target -> /lib/systemd/system/remote-fs.target

Run Level 변경

Troubleshooting of systemd and fsck on boot

https://gist.github.com/ebautistabar/82811d492231700ab2471dd9048502b7

https://salsa.debian.org/systemd-team/systemd/commit/8dc6998c2e9d49d0b08567b40b03b170313a8187

ARM core category

Onionfra — Tue, 20 Jun 2017 22:53:39 +0900

Cortex-A(ARMv8, ARMv7), Cortex-M, Coretex-R, Classic, SecureCore

Cortex-A

Cortex-M

Cortex-R

Classic

Secure

Linux container overview

Onionfra — Tue, 20 Jun 2017 21:56:32 +0900

LXC

•어플리케이션의 고립 환경을 지원하기 위해 리눅스 커널의 cgroup과 namespace 기능을 조합하여 만든 framework

•Cgroup: 리소스(CPU, memory, disk, I/O, network, etc) 사용에 대한 제한, 점유, 고립을 지원

üResource control

üFilesystem access

üGeneral device access

üMemory resources

üNetwork device resources

üCPU bandwidth

üBlock device IO bandwidth

üVarious other aspects of a control group's view of the system

•

•Namespace: 리소스들을 서로 다른 네임스페이스 그룹으로 나눠서, 다른 네임스페이스에서 볼 수 없도록 함

üpid, mnt, net, uts, ipc, user

Characteristic

•어플리케이션 관점에서의 분리(동작환경, 프로세스 트리, 네트워크, 사용자 id)

•

•어플리케이션과 OS와의 분리 실현

•

•퍼포먼스 저하 없는 실행시간 제공(Virtual machine대비)

•Emulate 단계가 없어 낮은 오버헤드 제공

•

•Virtual machine을 위한 부팅시간 불필요

•KVM, Xen, Vmware가상화 대비 빠른 시작/종료

•

•어플리케이션 컨테이너 지원(<->시스템 컨테이너)

•init및 각종 데몬을 실행할 필요 없이 목적에 맞는 프로세스만 존재하는 환경 구현 가능

•

•프로세스 단위 리소스(cpu, ram, devices) 분리 및 분배

•CPU

•RAM

•Devices

•Display

•GPU

•Serial(tty, i2c…)

•block device(hdd, emmc…)

•input device

•.

•단독 컨테이너가(프로세스) 대량의 리소스를 점유하는것을 방지(외부 공격 방지)

•SELinux 와 함께 컨테이너의 안전한 분리 실현(Guest 내의 root가 다른 HOST를 제어하지 못하게 함)

Disadvantages

•Host OS에 종속적

•Linux kernel만 가능

•컨테이너별 커널 구성 불가능(드라이버단의 공유 이슈 있음)

응용 예(Application container)

Security side

•SE linux와 결합한 보안 환경

•프로세스, 파일에 유형을 표시하여 이들의 분리, 상호작용하는 방식을 정의

•세분화된 액세스 제어(사용자, 역할, 유형, 레벨…)

•시스템 전체의 정책 관리(사용자 재량에 의한 설정 불가능)

•공격자는 정책의 변경 추가 없이 사용자 홈 디렉토리의 파일을 읽을 수 없음

•신뢰할 수 없는 입력으로부터 프로세스를 보호 하며 데이터의 기밀성과 무결성을 강화하는데 사용될

수 있음

linux multi core operation(AMP booting)

Onionfra — Tue, 20 Jun 2017 14:44:37 +0900

Asymmetric Multi-processing (AMP) = 비대칭 core

Symmetric Multi-processing (SMP) = 대칭 core

ARM & Linux change to AMP mode (ARM cp15 register,)
Define Cache initialize scheme
Define GIC initialize & distribute to core
Core Communication rule(IPI, SharedM, scretch register)
......

AMP & SMP of Multicore processor
reference: http://www.embedded.com/design/mcus-processors-and-socs/4429496/Multicore-basics

Linux booting sequence of AMP system

AMP-Linux&Android Linux(Asymmetric Multi-processing)

Interrupts, NAND, DRAM sharing of AMP system(Asymmetric Multi-processing)

•u-boot on multi core

•U-boot must have a MP driver(multi processor driver)

•TI have no MP driver now

•Reference link : http://gitorious.ti.com/ti-u-boot/ti-u-boot/blobs/30837e5b21d5a742983581ab9ee3fac085311d19/doc/README.mpc8572ds

•u-boot on single core

Action item

•Memory map(Dram) design for muti os(define address)

•Flash map design for muti os(define address)

•u-boot change for multi image load

•u-boot change for multi os booting(boot logic)

•Port MP driver or Fix kernel jump code

•Kernel0/Kernel1 change for AMP

•Kernel0/Kernel1 change for multi boot image

•Kernel0/Kernel1 change for cache enable scheme

•Kernel0/Kernel1 change for GIC

•Kernel0/Kernel1 change for Serial

•Device driver allocate to each kernel

Code tracing

Package build using Wayland-build-tool

Onionfra — Tue, 20 Jun 2017 13:14:58 +0900

Status: Build & weston is success, but weston-simple-egl is not working

Building Weston on Rasberrypi(raspbian)

# flashing latest raspbian image in host linux

https://www.raspberrypi.org/downloads/raspbian/

https://www.raspberrypi.org/documentation/installation/installing-images/linux.md

# update & upgrade rasbian

sudo apt-get update

sudo apt-get dist-upgrade

# wayland-build-tools clone (Made by Bryce Harrington)

git clone https://github.com/bryceharrington/wayland-build-tools.git

# Set build environment

cp wl_defines.sh ~/bin/

mkdir ~/build

mkdir ~/build/Wayland

# Install wayland build dependencies

./wl_install_deps

# Fail case: I got build error in mesa package in "wl_build" script so I did like below
config.txt
dtoverlay=vc4-kms-v3d
raspi-config
Change memory split -> 256MB
mesa-utils (to test OpenGL later)
sudo apt-get install mesa-utils
OpenGL driver
raspi-config -> Advanced Options -> GL Driver
Board Reboot!! "# reboot"
OpenGL test
glxgears

We need additional build dependencies
sudo apt-get build-dep libgl1-mesa-dri
sudo apt-get install \
    automake libtool \
    bison flex \
    gettext \
    libdrm-dev \
    libexpat1-dev \
    libudev-dev \
    libx11-xcb-dev \
    libxcb-dri3-dev \
    libxcb-dri2-0-dev \
    libxcb-glx0-dev \
    libxcb-xfixes0-dev \
    libxcb-present-dev \
    libxcb-sync-dev \
    libxshmfence-dev \
    libxdamage-dev \
    libxext-dev \
    libxfixes-dev \
    python-mako \
    x11proto-present-dev \
    x11proto-dri3-dev \
    x11proto-dri2-dev \
    x11proto-gl-dev

# Fail case: Even though I ran the "wl_install_deps" script, I had to install below packages using apt 
sudo apt-get install build-essential libgtk-3-dev check
# Fail case: wayland package require libxml2-dev package
sudo apt-get install libxml2-dev

# Fail case: I got build error in "libinput" package in "wl_build" script so I fixed it like below
gen libinput --disable-libwacom --disable-debug-gui
compile

# Fail case: I got build error in "pixman" package in "wl_build" script so I fixed it like below
gen pixman  --disable-arm-iwmmxt
compile

# Fail case:  I got build error in "mesa" package in "wl_build" script so I fixed it like below
echo "mesa"
cd $WLROOT/mesa
git clean -xfd
./autogen.sh --prefix=$WLD \
   --enable-gles2 \
   --with-egl-platforms=x11,wayland,drm \
   --enable-gbm --enable-shared-glapi \
   --with-gallium-drivers=vc4 \
   --without-dri-drivers \
   --disable-intel \
   --disable-va \
   --disable-vdpau \
   --disable-xvmc \
   --disable-omx
compile

# All related package clones including wayland

./wl_clone

# Fail case: code of "master" branch is not stable(build error) so I used mesa-11.1.1

cd ~/build/Wayland/mesa

git checkout mesa-11.1.1

# Start build

./wl_build

# Run weston on X11(Xwayland)

./weston --tty=1

# Run weston on DRM backend (without X11)

1) Set Wayland environment variable $XDG_RUNTIME_DIR

vi ~/.profile

# Code to put in .profile
# Need to check if linux environment has XDG_RUNTIME_DIR using "env" command

if test -z "${XDG_RUNTIME_DIR}"; then
    export XDG_RUNTIME_DIR=/tmp/${UID}-runtime-dir
    if ! test -d "${XDG_RUNTIME_DIR}"; then
        mkdir "${XDG_RUNTIME_DIR}"
        chmod 0700 "${XDG_RUNTIME_DIR}"
    fi
fi

#Source from: https://wayland.freedesktop.org/building.html

2) Go to virtual console (go to tty1) & login with "root" account
ctrl + alt + F1

3) weston --tty=1

References:

https://github.com/wayland-project/wayland-build-tools

https://wayland.freedesktop.org/building.html

https://www.raspberrypi.org/forums/viewtopic.php?f=38&t=175981

Package build using Wayland-build-tool

Onionfra — Mon, 19 Jun 2017 20:02:38 +0900

Building Weston on Ubuntu 16.04

# wayland-build-tools clone (Made by Bryce Harrington)

git clone https://github.com/bryceharrington/wayland-build-tools.git

# Set build environment

cp wl_defines.sh ~/bin/

mkdir ~/build

mkdir ~/build/Wayland

# Install wayland build dependencies

./wl_install_deps

# Fail case: I got build error in mesa package in "wl_build" script so I fixed it like below

--with-gallium-drivers=swrast,nouveau,r300,r600

--with-gallium-drivers=swrast,nouveau

# Fail case: I got build error in libinput package in "wl_build" script so I fixed it like below

./autogen.sh --disable-libwacom --disable-debug-gui

# Fail case: Even though I ran the "wl_install_deps" script, I had to install below packages using apt

sudo apt-get install build-essential libgtk-3-dev check

# All related package clones including wayland

./wl_clone

# Start build

./wl_build

# Run weston on X11(Xwayland)

./weston --tty=1

# Run weston on DRM backend (without X11)

1) Set Wayland environment variable $XDG_RUNTIME_DIR

vi ~/.profile

# Code to put in .profile
# Need to check if linux environment has XDG_RUNTIME_DIR using "env" command

if test -z "${XDG_RUNTIME_DIR}"; then
    export XDG_RUNTIME_DIR=/tmp/${UID}-runtime-dir
    if ! test -d "${XDG_RUNTIME_DIR}"; then
        mkdir "${XDG_RUNTIME_DIR}"
        chmod 0700 "${XDG_RUNTIME_DIR}"
    fi
fi

#Source from: https://wayland.freedesktop.org/building.html

2) Go to virtual console (go to tty1) & login with root account
- ctrl + alt + F1

3) weston --tty=1

References:

https://github.com/wayland-project/wayland-build-tools

https://wayland.freedesktop.org/building.html

Useful links

Onionfra — Fri, 16 Jun 2017 16:18:06 +0900

Raspberrypi kernel git

https://github.com/raspberrypi/linux.git

Wayland build tools git

https://github.com/bryceharrington/wayland-build-tools.git

Building Weston image with Yocto for Raspberry pi

http://fabienlahouderepro.blogspot.kr/2017/03/building-weston-image-with-yocto-for.html

My opinion: Working fine, but wayland is too slow... why... I don't know...

AGL for Raspberry Pi

https://wiki.automotivelinux.org/agl-distro/agl-raspberrypi

My opinion: Still trying...

Maynard

Maynard is a desktop environment designed for the Raspberry Pi (but not limited to it) running on Wayland.

https://www.raspberrypi.org/blog/preview-the-upcoming-maynard-desktop/

https://github.com/raspberrypi/maynard/wiki/Develop-on-a-Raspberry-Pi

My status: latest code is not working

Wayland & Mesa

Onionfra — Sun, 11 Jun 2017 23:00:54 +0900

Mesa

-Open-source implementation of the OpenGL specification

-Implements a vendor-independent translation layer between a graphics API
such as OpenGL and the graphics hardware drivers in the operating system kernel

Weston/Wayland IVI Extensions

Onionfra — Sun, 11 Jun 2017 22:55:26 +0900

Weston/Wayland IVI Extensions

•Well-defined interface

•Standardized compositing

•Separation of HMI and Layer Management

•Dynamically Extensions during runtime

•Low integration complexity

- Each application create wayland surface

- Each wayland surface is mapped to ivi surface for being managed by HMI

- HMI manages ivi surface with Layers which group surfaces

Component diagram

ivi-shell.so:

-Implement ivi-client/controller protocols

-Communicate weston by plug-in APIs

-Set name of plug-in in weston.ini

libilmClient.so:

- Wrap ivi-client protocol to be compatible with Genivi LM client APIs

libilmControl.so:

-Wrap ivi-controller protocol to be compatible with Genivi LM control APIs

ivi-controller.so:

-Management of properties of surface/layer/screen

ivi-input.so:

-Management of input focus and device acceptance per surface

Automotive Graphic Requirement

Many screens,

Many devices to be managed by Central HMI controller

출처: http://events.linuxfoundation.org/sites/events/files/slides/ALS_201506_tanibata_weston_ivi_shell_v04.pdf

Managing screen,layer,surface(ivi-shell)

출처: http://events.linuxfoundation.org/sites/events/files/slides/ALS_201506_tanibata_weston_ivi_shell_v04.pdf

참조: http://www.bmw-carit.de/open-source/genivi-layermanagement.php

ivi-share mechanism

Onionfra — Sun, 11 Jun 2017 22:42:13 +0900

1. Shared surface(the surface whose ID is set of simple-ivi-share argument) does eglSwapBuffers

2. The ivi-share catchs attach event and get buffer object by using libgbm.

3. By using libdrm, ivi-share gets drm_gem_flink. The gem is the drm object which represent the buffer.

4. The ivi-share sends drm_gem_flink.name to simple-ivi-share app.

5. The simple-ivi-share app calls EglCreateImageKHR() to get eglImage.

6. The simple-ivi-share app calls GLEglImageTargetTexture2DOES() to create EGLImage target(texture object)
(EGLImage target is referenced object of native image “eglImageOES”

7. The simple-ivi-share app calls eglSwapBuffers

Create an EGLImage from an existing image resource(buffer)

EGLImageKHR eglCreateImageKHR(

EGLDisplay dpy, // EGL display

EGLContext ctx, // EGL client API context

EGLenum target, // Type of resource being used as EGLImage source

EGLClientBuffer buffer, // Name of a resource to be used as EGLImage source

const EGLint *attrib_list // List of attribute-value which is used to select EGLImage source

)

Newly specified texture object will created that “EGLImage target” of the specified eglImageOES

void EGLImageTargetTexture2DOES(

enum target, // Set to TEXTURE_EXTERNAL_OES,

// defines the currently bound external texture object to be a target sibling of image

eglImageOES image // Must be the handle of a valid EGLImage resource

);