Commit 6b1fd17a authored by Guido Günther's avatar Guido Günther

Consistent i.MX spelling

There were several differen spellings. I went for i.MX6 and i.MX8
(with no space in front of the number)
parent f2ba9097
......@@ -125,7 +125,7 @@ Alternatively, you can click the omnibar in Builder and select the "Export Bundl
When the flatpak creation is finished, a nautilus window will pop up in the directory where the sm.puri.Handy.Example.flatpak is located. In this example, the flatpak can be found here: ~/.var/app/org.gnome.Builder/cache/gnome-builder/projects/libhandy/flatpak/staging/arm-wip-stackablebox/sm.puri.Handy.Example.flatpak
**********************************************************************
Deploying a C/GTK+3 (libhandy) flatpak to Phosh running on iMX 6 board
Deploying a C/GTK+3 (libhandy) flatpak to Phosh running on i.MX6 board
**********************************************************************
To run this flatpak you must first get the flatpak onto the dev board and install it.
......
.. _imx6:
imx6
====
i.MX6
=====
The current development board is the Boundarydevices `Nitrogen board <https://boundarydevices.com/product/nitrogen6_max-i-mx6-quad-plus-4gb-ddr3/>`_ with i.MX6 Quad plus CPU. This page describes how to set it up for development.
......@@ -64,8 +64,8 @@ Unpack the image and dd the image to the device::
Depending on your system, the dd can take a while so grab a cup of coffee and be patient.
Working with the iMX6 Nitrogen board
------------------------------------
Working with the i.MX6 Nitrogen board
-------------------------------------
If this will be your first boot on the iMX6 board, then you will need a u-boot upgrade.
......
.. _imx8:
imx8
====
i.MX8
=====
TBD
......@@ -3,14 +3,14 @@
Plasma Mobile on armhf
======================
For this exercise, the imx6 dev board is used, starting from imx6.img built from the `d0349a9 <https://code.puri.sm/Librem5/image-builder/commit/d0349a93ea43c5497efae69e611aa0d9f4fd8b9d>`_ commit (image-builder repo). All packages were built on this board to get .debs for the native armhf architecture.
For this exercise, the i.MX6 dev board is used, starting from imx6.img built from the `d0349a9 <https://code.puri.sm/Librem5/image-builder/commit/d0349a93ea43c5497efae69e611aa0d9f4fd8b9d>`_ commit (image-builder repo). All packages were built on this board to get .debs for the native armhf architecture.
**********************************
Setting up Development Environment
**********************************
On the imx system, install some initial plasma mobile build dependencies::
On the i.MX6 system, install some initial plasma mobile build dependencies::
purism@pureos:~$ sudo apt-get install plasma-workspace-wayland git dpkg-dev cmake debhelper extra-cmake-modules kwayland-dev libkf5declarative-dev libkf5notifications-dev libkf5people-dev libkf5service-dev libsystemd-dev libtelepathy-qt5-dev pkg-kde-tools plasma-framework-dev qt5-default qtdeclarative5-dev fakeroot
......@@ -116,7 +116,7 @@ Run kwin_wayland from another tty::
Note that to capture the plasma-phone boot logs, you can always add "2> kwin.log" to the end of the kwin_wayland command. Additional plasma logs can be found in /tmp/plasmashell_logs.
At this point plasma mobile should be running on your imx6 board!
At this point plasma mobile should be running on your i.MX6 board!
Note that there is a `known issue <https://bugs.kde.org/show_bug.cgi?id=391412>`_ where the mouse functions but is invisible.
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment