nyuuzyou/wikis huggingface dataset:
Raspberry Pi 1 / 2 (raspberry-pi)

== Contributors ==
* drebrez
== Installation ==
1. Follow the steps on Installation_guide#Initialization
2. Choose the raspberry-pi device
3. Select the kernel for your Raspberry Pi version
[10:47:03] Which kernel do you want to use with your device?
[10:47:03] Available kernels (2):
[10:47:03] * rpi: Kernel for the Raspberry Pi 1
[10:47:03] * rpi2: Kernel for the Raspberry Pi 2
4. Start the build process and install the completed image to a sdcard 
$ ./pmbootstrap.py install --sdcard /dev/sdX # Replace /dev/sdX with the device for your sdcard
5. Place the sdcard into the Raspberry Pi and boot it
== See also ==
* The Raspberry Pi has a pre-existing port of Alpine Linux
* It should be possible to convert the pre-existing RPi Alpine install to a pmOS install.
* Testing out Hildon and XFCE4 (other UIs did not work at all?) on Raspberry Pi after converting the Alpine installation
* librerpi - a Free Software firmware for the Pi.
* initial PR
* New device: Raspberry Pi Zero with Ethernet over USB enabled
* Summary of accelerated video status as of August 2021
Category:Devices
Raspberry Pi 3 (raspberry-pi3)

== Contributors ==
* drebrez
== Users owning this device ==
== Installation ==
# Follow the steps on Installation_guide#Initialization
# Choose the raspberry-pi3 device
# Start the build process and install the completed image to a sdcard
#: 
$ pmbootstrap install --sdcard=/dev/sdX
(replace /dev/sdX with the device for your sdcard)
# Place the sdcard into the Raspberry Pi and boot it
== Features ==
=== Audio ===
The audio is configured to be sent to the HDMI port by default.
If you want to use the onboard jack and your UI does not offer the graphical settings to do yo, you can run this commands:
$ amixer cset numid=3 1
(test the output with)
$ speaker-test -c 2
(change output back to HDMI)
$ amixer cset numid=3 2
=== Graphical Interfaces ===
Interface 	Info 	Working
none 	 	Y
fbkeyboard 	 	
GNOME 3 	 	Y
i3wm 	 	
Kodi 	 	Y
MATE 	 	Y
Phosh 	sometimes does not start up, try to reboot your device when you land in console	Y
Plasma-Desktop 	 	Y
Plasma Mobile 	 	
Plasma Bigscreen	runs fine with --no-recommends parameter 	Y
Shelli 	 	
Sway 	 	
Weston 	Does not show up after 5 minutes 	N
Xfce4 	 	Y
== Photos ==
File:Raspberry-pi-xfce1.jpg|thumb|Xfce4
File:Raspberry-pi-xfce2.jpg|thumb|Xfce4
File:DSC 0024.JPG|thumb|Phosh on RPi3
File:Rpi3-plasma-wavetouch7inchhdmi.jpeg|thumb|plasma
== Accessories ==
Accessory 	Info 	Working
NesPi Case+	 	Y
pi-top CEED	power button cannot be used for safe shutdown, shutting down postmarketOS does not shut down the display itself.	Y
== Kernel features ==
The following checks with kconfig succeed:
--apparmor, --iwd, --nftables, --zram
The following check fail currently:
--anbox, --containers
== See also ==
* The Raspberry Pi has a pre-existing port of Alpine Linux
* Testing out Hildon and Xfce4 (other UIs did not work at all?) on Raspberry Pi after converting the Alpine installation
* rpi-open-firmware - a Free Software firmware for the Pi.
* initial PR
* New device: Raspberry Pi Zero with Ethernet over USB enabled
* Branch with experimental Anbox Support
* 
Category:Devices
Raspberry Pi 4 (raspberry-pi4)

== Contributors ==
* MartijnBraam
* drebrez
== Users owning this device ==
== Installation ==
1. Follow the steps on Installation_guide#Initialization
2. Choose the raspberry-pi4 device
3. Start the build process and install the completed image to a sdcard
$ pmbootstrap install --sdcard /dev/sdX
(replace /dev/sdX with the device for your sdcard)
4. Place the sdcard into the Raspberry Pi and boot it
== Display ==
Screens may need to be connected at boot time, otherwise they might only display 1080p or not display anything at all ().
== Bluetooth ==
On the Raspberry Pi 4, the Bluetooth chip uses the hardware UART0 port. In postmarketOS, Bluetooth is enabled by default; this means that the hardware UART port is inaccessible.
If you want to use the hardware UART for other purposes (for example, serial debugging), edit the /boot/usercfg.txt and comment out the following line at the end of the file:
# Automatically enable Bluetooth without having to use btattach
# Note that the Pi's Bluetooth interface is connected via hardware UART;
# if you intend to use it for other purposes (for example, serial debugging)
# comment out the line below.
dtparam=krnbt=on
When this is done, Bluetooth will have to be enabled manually using btattach -B /dev/ttyAMA0 -P bcm -S 115200 -N.
See also: Raspberry Pi 3 - Setting Up Bluetooth on the Alpine Wiki. The contents of this wiki page apply to the Pi 4 as well.
== See also ==
* initial PR
* 
* Kernel package in Alpine (linux-rpi)
* Category:Raspberry on the Alpine Linux wiki
Category:Devices
Raspberry Pi 5 (raspberry-pi5)

== Contributors ==
* Winbo-yml-exe
== Users owning this device ==
== Installation ==
Make your own installation image with pmbootstrap:
$ pmbootstrap init
$ pmbootstrap install --sdcard=/dev/sdX (Replace /dev/sdX with your SD card's device path)
 
== See also ==
* initial MR
* 
* Kernel package in Alpine (linux-rpi)
* Category:Raspberry on the Alpine Linux wiki
Category:Devices
Raspberry Pi Compute Module 4 (raspberry-picm4)

Raspberry Pi Compute Module 4 is a System-on-Module (SoM) by Raspberry Pi Foundation. It features the same SoC as Raspberry Pi 4 (raspberry-pi4) and various configurations of the on-board capacities.
== Contributors ==
* MasanoriOgino
== Users owning this device ==
== Installation ==
== Part number ==
The part number is CM4XYYZZZ where X represents on-board wireless connectivity (0: no WLAN/BT chip, 1: Cypress CYW43455), YY represents the capacity of on-board LPDDR4 RAM (01: 1 GB, 02: 2 GB, 04: 4 GB, 08: 8 GB), and ZZZ represents the capacity of on-board eMMC storage (000: no eMMC chip, 008: 8 GB, 016: 16 GB, 032: 32 GB). The versions without eMMC storage (the part numbers ending with 000) is especially called Compute Module 4 Lite.
For instance, CM4001000 is no wireless, 1 GB RAM, no eMMC storage (Lite) version.
== Complementary devices ==
* ClockworkPi uConsole (clockworkpi-uconsole-cm4)
* CutiePi Tablet (cutiepi-tablet)
* Raspberry Pi Compute Module 4 IO Board (raspberry-picm4ioboard)
== See also ==
* The product page of Raspberry Pi Compute Module 4
Raspberry Pi Compute Module 4 IO Board (raspberry-picm4ioboard)

Raspberry Pi Compute Module 4 IO Board is an I/O board for Raspberry Pi Compute Module 4 (raspberry-picm4) by Raspberry Pi Foundation.
== Contributors ==
* MasanoriOgino
== Users owning this device ==
== Compatible SoMs ==
* Raspberry Pi Compute Module 4 (raspberry-picm4)
== See also ==
* The product page of Raspberry Pi Compute Module 4 IO Board
Raspberry Pi Zero (raspberry-pi0)

== Users owning this device ==
== Contributors ==
* drebrez
== Installation ==
1. Follow the steps on Installation_guide#Initialization
2. Choose the raspberry-pi0 device
3. Start the build process and install the completed image to a sdcard (replace /dev/sdX with the device for your sdcard)
$ ./pmbootstrap.py install --sdcard /dev/sdX
4. Place the sdcard into the Raspberry Pi and boot it
5. Connect a microUSB cable to the central microUSB port (with the USB label)
6. Let the RPI boot and then you should be able to connect using SSH
$ ssh user@172.16.42.1
== Issues ==
=== 3D Acceleration (GPU) ===
The vc4 module fails to load:
# dmesg | grep vc
[ 0.000000] Kernel command line: 8250.nr_uarts=1 cma=256M bcm2708_fb.fbwidth=640 bcm2708_fb.fbheight=480 bcm2708_fb.fbswap=1 smsc95xx.macaddr=B8:27:EB:3D:4B:57 vc_mem.mem_base=0x1ec00000 vc_mem.mem_size=0x20000000 dwc_otg.lpm_enable=0 console=tty1 console=ttyS0,115200
[ 0.674097] vc-mem: phys_addr:0x00000000 mem_base=0x1ec00000 mem_size:0x20000000(512 MiB)
[ 0.675232] vc-sm: Videocore shared memory driver
[ 0.716056] vchiq: vchiq_init_state: slot_zero = (ptrval), is_master = 0
[ 0.717968] [vc_sm_connected_init]: start
[ 1.300516] [vc_sm_connected_init]: end - returning 0
[ 2.594391] vc4-drm soc:gpu: failed to bind 20902000.hdmi (ops vc4_hdmi_ops [vc4]): -517
[ 2.602801] vc4-drm soc:gpu: master bind failed: -517
[ 2.992957] vc4-drm soc:gpu: failed to bind 20902000.hdmi (ops vc4_hdmi_ops [vc4]): -517
[ 3.013847] vc4-drm soc:gpu: master bind failed: -517
[ 3.021189] vc4-drm soc:gpu: failed to bind 20902000.hdmi (ops vc4_hdmi_ops [vc4]): -517
[ 3.048315] vc4-drm soc:gpu: master bind failed: -517
Same result with both dtoverlay=vc4-kms-v3d and dtoverlay=vc4-fkms-v3d overlarys using gpu_mem=256
== Photos ==
File:RaspberryPiZeroDebugShell.jpg|thumb|left|debug-shell
File:RaspberryPiZeroMate.jpg|thumb|MATE
File:RaspberryPiZeroXFCE.jpg|thumb|XFCE4
File:RaspberryPiZeroWeston.jpeg|thumb|Weston
== See also ==
* The Raspberry Pi has a pre-existing port of Alpine Linux
* It should be possible to convert the pre-existing RPi Alpine install to a pmOS install.
* Testing out Hildon and XFCE4 (other UIs did not work at all?) on Raspberry Pi after converting the Alpine installation
* rpi-open-firmware - a Free Software firmware for the Pi.
* initial PR
* New device: Raspberry Pi Zero with Ethernet over USB enabled
* Hyper-pi - Project to make a handheld device w/ a RPi Zero and a HyperPixel 4" capacitive touch screen
* Ruha.cam A Pi zero based camera
Category:Devices
Realme 3 Pro (realme-rmx1851)

== Contributors ==
* Joseph Glynn (josephnglynn)
== Users owning this device ==
== How to enter flash mode ==
Hold all the buttons at the same time until the screen shows.
== Installation ==
Use pmbootstrap to build your own installation image.
$ pmbootstrap init
$ pmbootstrap install
$ pmbootstrap flasher flash_rootfs
$ pmbootstrap flasher flash_dtbo # If your using the branch below with dtbo img (Note: try using if you get ssh issues)
$ pmbootstrap flasher flash_kernel
== Downstream ==
There is a branch in my fork of pmaports which contains some dtc hacks to enable simplefb (note: it only shows for a few seconds, with no text - but there are some colourful penguins). It also contains modified firmware and device APKBUIlDs which use F07 firmware and builds a dtbo image. 
The downstream kernel is pretty broken, so I am now focusing on mainlining this device.
NOTE: All the branches above where meant as throwaways, as such they are not maintained and commits are messy.
== Mainlining ==
Currently the phone refuses to boot a mainline kernel.
== Notes ==
In order to connect to the device via usb (and ssh) use:
$ ip link set dev interface address 12:12:12:12:12:12 # You might need to set a mac address if not already set
$ dhcpcd interface --nohook ipv6
Make sure your coming from a C18 (RUI1) based ROM, as that is what I am testing on. 
RUI1 seems to modify the bootloader, making booting not possible.
== See also ==
 Initial merge request
Realme GT Master (realme-lunaa)

== Contributors ==
* WorryNori
== Users owning this device ==
== Mainline kernel ==
There's a fork of mainline kernel which contains sm7325 dtsi, but there's no dts for the phone yet. 
== Status ==
Kernel compiles with downstream dts, but the phone won't boot.
== How to enter flash mode ==
* Bootloader: Power on the device with both and buttons
* EDL: Power on the device with and with buttons
* Recovery: Boot the phone into bootloader and select Recovery Mode
== Installation ==
== See also ==
* Kernel source with 7325 support
* Device Info HW database entry
Realme GT Neo5 150W (realme-senna-b)

The Realme GT Neo5, just like Nothing Phone 2, has an underclocked Snapdragon 8+ Gen 1, with prime core capped at 3.0GHz, big cluster cores at 2.5GHz and little cluster cores at 1.8GHz.
== Contributors ==
== Users owning this device ==
== How to enter flash mode ==
== Installation ==
Use pmbootstrap to build your own installation image.
$ pmbootstrap init
$ pmbootstrap install --fde
== See also ==
Realme GT Neo 3T/Q5 Pro (realme-rmx3371)

== Contributors ==
DragoPayras
== Users owning this device ==
DragoPayras
== How to enter flash mode ==
Unlock the bootloader according to the instructions on this 4PDA.
Turn off the phone and press the volume down and power buttons.
== Installation ==
I will provide an opportunity to see how the display, touchscreen, battery and CPU
== See also ==
Realme X3 (realme-x3)

== Contributors ==
* Patriot06
== Users owning this device ==
== How to enter flash mode ==
=== Fastboot ===
* Shutdown the device completely.
* Hold the and button simultaneously.
== Backup ==
Backup super, dtbo & boot partition's by using a recovery program such as TWRP.
=== Team Win Recovery Project ===
Use TWRP:
Download and flash TWRP via bootloader
 $ fastboot flash recovery recovery.img
 $ adb shell
 # dd if=/dev/block/by-name/super of=/sdcard/super.img
 # dd if=/dev/block/by-name/dtbo of=/sdcard/dtbo.img
 # dd if=/dev/block/by-name/boot of=/sdcard/boot.img
 # exit
 $ adb pull /sdcard/super.img
 $ adb pull /sdcard/dtbo.img
 $ adb pull /sdcard/boot.img
== Installation ==
Install pmbootstrap and execute:
 $ pmbootstrap init
 $ pmbootstrap install
===Before installing rootfs, please erase dtbo===
$ fastboot erase dtbo
===Flash rootfs to the super partition:===
* This method does not erase your Android user data
* The super partition is rather limited in size
 $ pmbootstrap flasher flash_rootfs --partition super
 $ pmbootstrap flasher flash_kernel --partition boot
 $ fastboot reboot
== See also ==
* Mainline kernel for Realme X3 (SM8150)
Recovery

The stock recovery used on Android is a Linux kernel with an initramfs that can usually be controlled with volume buttons. It was previously commonly replaced with ClockWorkMod and nowadays mostly TWRP. TWRP is based on the vendor kernel and makes use of the Android build system, which is complicated. It also uses a tool from Google to create a framebuffer, which is not needed on mainline kernels. It is also build against the bionic libc, which is different from musl used in Alpine.
Using pmbootstrap, it can be possible to create a more simplified recovery that is also more suitable for pmOS, instead of only Android. Writing a new GUI from scratch is likely easier than using the TWRP code on top of mainline.
== Notes ==
* Installation_from_recovery_mode gives brief tutorial to install pmOS by android recovery
* Possible GUI framework, might require hardware acceleration
== See also ==
* Android Recovery: general tips and tricks for postmarketOS and the recovery system
Releases

postmarketOS releases are created roughly every six months, following the release cycle of Alpine Linux. With every postmarketOS release, pmaports master is branched into a new release branch. The release branches receives security upgrades as necessary (from both Alpine and postmarketOS). In postmarketOS, we also provide service packs for the latest release to ship fixes and feature updates.
=== Introduction ===
==== What's the difference between releases? ====
The "edge" channel is a rolling release where all packages are kept at their newest version. This offers faster access to software at the expense of less user testing. In practice, issues on edge are relatively uncommon, and are documented here when found.
The versioned releases are initially a snapshot of edge, from which stable changes are backported. Updates to packages in a versioned release will usually only contain bug fixes. This means that newer features take longer to appear (if at all).
In essence, a stable release will give you more a more tried and tested, solid experience, while edge gives you the latest features.
==== Which should I choose? ====
If you're interested in hacking on your device and don't care so much about stability, edge is right for you. On the other hand if you'd prefer to have a more stable experience, with backported security patches and avoiding major feature changes, use a versioned release.
=== Releases ===
==== Active ====
Title 	Channel	Branch pmaports	Branch aports	Milestone	Announcement	Planned EOL
Edge 	edge 	master 	master 	- 	- 	
The One With Androids & Cameras, But It's Mainline Linux	v24.12 	v24.12 	3.21-stable 	 	2024-12-23 	(one month after next release)
==== Planned ====
Title	Channel	Branch pmaports	Branch aports	Milestone	Announcement
- 	v25.06 	v25.06 	3.22-stable 	 	-
==== Old ====
Title 	Channel	Branch pmaports	Branch aports	Milestone	Announcement
The One With Over 250 Devices 	v24.06 	v24.06 	3.20-stable 	 	2024-06-16
The One We Asked The Community To Name 	v23.12 	v23.12 	3.19-stable 	 	2023-12-18
From the GNOME Mobile 2023 Hackfest 	v23.06 	v23.06 	3.18-stable 	 	2023-06-07
The One With Napali Calling 	v22.12 	v22.12 	3.17-stable 	 	2022-12-18
The One Where We Started Using Release Titles	v22.06 	v22.06 	3.16-stable 	 	2022-06-12
- 	v21.12 	v21.12 	3.15-stable 	 	2021-12-29
- 	v21.06 	v21.06 	3.14-stable 	 	2021-07-04
Beta 2 	v21.03 	v21.03 	3.13-stable 	 	2021-03-31
Beta 1 	v20.05 	v20.05 	3.12-stable 	 	2020-05-31
=== See also ===
* https://postmarketos.org/blog/: has posts for each release and service pack
* Alpine releases
* Channels.cfg reference
* Creating a service pack
* Creating a release branch
__NOTOC__
Category:Technical Reference
Renamed Devices

Please keep the lists sorted alphabetically.
== Renamed ==
Old Name 	New Name 	Merge Request
apple-iphone6 	apple-n61 	
asus-grouper 	nvidia-tegra-armv7 	
asus-tf101 	nvidia-tegra-armv7 	
asus-tf201 	nvidia-tegra-armv7 	
asus-tf300t 	nvidia-tegra-armv7 	
asus-tf300tg 	nvidia-tegra-armv7 	
asus-tf700t 	nvidia-tegra-armv7 	
asus-tilapia 	nvidia-tegra-armv7 	
bq-picmt 	bq-paella-downstream 	
fujitsu-m532 	pegatron-chagall 	
google-bob 	google-gru 	
google-burnet 	google-kukui 	
google-cerise 	google-kukui 	
google-cozmo 	google-kukui 	
google-damu 	google-kukui 	
google-dru 	google-gru 	
google-druwl 	google-gru 	
google-dumo 	google-gru 	
google-elm 	google-oak 	
google-fennel14 	google-kukui 	
google-fennel 	google-kukui 	
google-hana 	google-oak 	
google-juniper 	google-kukui 	
google-kakadu 	google-kukui 	
google-kappa 	google-kukui 	
google-katsu 	google-kukui 	
google-kenzo 	google-kukui 	
google-kevin 	google-gru 	
google-kodama 	google-kukui 	
google-krane 	google-kukui 	
google-makomo 	google-kukui 	
google-stern 	google-kukui 	
google-veyron-fievel 	google-veyron 	
google-veyron-jaq 	google-veyron 	
google-veyron-jerry 	google-veyron 	
google-veyron-mickey 	google-veyron 	
google-veyron-mighty 	google-veyron 	
google-veyron-minnie 	google-veyron 	
google-veyron-speedy 	google-veyron 	
google-veyron-tiger 	google-veyron 	
google-willow 	google-kukui 	
lg-p880 	nvidia-tegra-armv7 	
lg-p895 	nvidia-tegra-armv7 	
mozilla-flame 	t2m-flame 	
nokia-rm-696 	nokia-n9 	
nokia-rm846 	nokia-sand 	
nokia-rx51 	nokia-n900 	
pegatron-chagall 	nvidia-tegra-armv7 	
pine-a64lts 	pine64-a64lts 	
pine-dontbeevil 	pine64-dontbeevil 	
pine-pinephone 	pine64-pinephone 	
pine-pinetab 	pine64-pinetab 	
samsung-a3lte 	samsung-a3 	
samsung-a3ulte 	samsung-a3 	
samsung-a5lte 	samsung-a5 	
samsung-a5ulte 	samsung-a5 	
samsung-cprime 	samsung-rossa 	
samsung-espresso3g 	samsung-espresso7 	
samsung-fortuna3g 	samsung-fortuna 	
samsung-gprime 	samsung-gprimeltecan 	
samsung-gprimeltecan 	samsung-gprime 	
samsung-gprimeltecan 	samsung-fortuna 	
samsung-gprimeltexx 	samsung-fortuna 	
samsung-gt58lte 	samsung-gt58 	
samsung-gt510wifi 	samsung-gt510 	
samsung-i8190 	samsung-golden 	
samsung-i9070 	samsung-janice 	
samsung-i9195 	samsung-serranolte 	
samsung-i9300 	samsung-m0, samsung-m3	
samsung-i9305 	samsung-i9300 	
samsung-i9505 	samsung-jflte 	
samsung-j3nxlte 	samsung-j3xnlte 	
samsung-j53g 	samsung-j5 	
samsung-j5nlte 	samsung-j5 	
samsung-lt01wifi 	samsung-lt01 	
samsung-matissevewifi	samsung-matisseve 	
samsung-n7100 	samsung-t03g 	
samsung-serranovelte 	samsung-serranove 	
sony-castor-windy 	sony-castor 	
tablet-x64uefi 	generic-x86_64 	
tablet-x86uefi 	generic-x86_64 	
wingtech-wt88047 	xiaomi-wt88047 	
== Removed ==
Name 	Merge Request
chuwi-hi10plus	
huawei-lua-u22	
oppo-a51f 	
teclast-x80pro	
== See also ==
* Use codename instead of model number
* Check if device was renamed
Repository maintenance

This page is about maintaining the official binary package repository of postmarketOS. It does not relate to the local package repository that pmbootstrap creates when compiling packages. So most people will not need this.
== Qt upgrade ==
There are KDE packages, which need to be rebuilt after each Qt upgrade:
$ pmbootstrap pkgrel_bump kwayland kwin plasma-framework kdeclarative
See for an idea to automatize this and for more information.
== Fixing upstream incompatibilities with Alpine's repository ==
The following script checks out the master branch of pmbootstrap and pmaports, automatically bumps the pkgrels that need to be bumped because of soname bumps, and regenerates all aports that are based on Alpine's aports.
Finally it executes the upstream compatibility test case again, which should run through again with the changes it made.
After the script ran, manually check the diff in the pmaports.git repository. Then make reasonable patches and commit messages from the changes.
#!/bin/sh -ex
# make sure we don't get an outdated mirror
mirror="http://dl-cdn.alpinelinux.org/alpine/"
git -C ~/code/pmbootstrap checkout master
git -C ~/code/pmbootstrap/aports checkout master
git -C ~/.local/var/pmbootstrap/cache_git/aports_upstream pull
pmbootstrap --mirror-alpine="$mirror" -y zap
pmbootstrap --mirror-alpine="$mirror" pkgrel_bump --auto
pmbootstrap --mirror-alpine="$mirror" aportgen \
 busybox-static-armhf busybox-static-aarch64 busybox-static-armv7 \
 gcc6-armhf gcc6-aarch64 gcc6-armv7 \
 gcc-armhf gcc-aarch64 gcc-armv7 \
 musl-armhf musl-aarch64 musl-armv7 \
 grub-efi-x86
cd ~/code/pmbootstrap/aports
pytest .gitlab-ci/testcases/test_upstream_compatibility.py
git diff --name-only
== See also ==
* How to merge git commits on the command line
* pmOS-repo-scripts
* Fixing the repo after QT upgrade to 5.10.1
* Add a new architecture to postmarketOS
Reticulum

== Reticulum ==
Reticulum is a cryptography-based networking stack for building local and wide-area networks with readily available hardware. Reticulum can continue to operate even in adverse conditions with very high latency and extremely low bandwidth.
== Setup and Usage ==
=== Meshchat ===
Meshchat is a simple mesh network communications app powered by the Reticulum Network Stack.
Install instructions:
sudo apk add py3-aiohttp \
py3-cx_freeze \
py3-peewee \
py3-websockets \
py3-pip \
py3-pyserial\
npm 
pip install rns --break-system-packages
pip install lxmf --break-system-packages
git clone https://github.com/liamcottle/reticulum-meshchat.git
cd reticulum-meshchat
git fetch
git pull
npm install
npm run build
python ./meshchat.py --generate-identity-file ~/reticulum-meshchat/storage/my_identity
python meshchat.py --identity-file ~/reticulum-meshchat/storage/my_identity
If you skip the identity generation, everytime you launch you will get a new identity...
Now you are able to access meshchat via browser on localhost:8000.
In the webinterface click on interfaces, edit the Default Interface, select TCPClientInterface and add the testserver reticulum.betweentheborders.com:4242
You have to stop and start it again to recognize your set networking interface.
=== Nomadnet ===
Off-grid, resilient mesh communication with strong encryption, forward secrecy and extreme privacy.
Install Instructions
Follow the install instructions on the official repo. 
For the pip commands you will have to to add --break-system-packages
like:
pip install nomadnet --break-system-packages
== See Also ==
* Official Website
* Reticulum Repo
* Nomadnet Repo
* 38c3 Talk
Rockchip RK3126/RK3128/RK3188

RK3188 is a Rockchip SoC released in 2013. There are two lower-performance variants of RK3188 named RK3128 and RK3126 released in 2014.
== Mainlining ==
This basic support for the SoC family has been mainlined and further improvement is discussed on the linux-rockchip mailing list (archive, patchwork).
== Devices ==
=== RK3188 ===
=== RK3128 ===
=== RK3126 ===
== Tree ==
== See also ==