Getting Jiggy with the Latte Panda

Originally I was thinking of using multiple single board computers on a network to perform different tasks. But after buying a 256GB micro-SD card which I had intended to use for a Raspberry Pi, I had a change of heart. The latter panda has 32GB of on board storage which I can use to host the OS, and then with 256GB of extra storage, rather than having a lot of different devices on the network, I can probably install everything to the latter panda.

So what’s the plan? There are a bunch of points I want to hit on this. I guess I should start with the high priority ones and work from there.

1. Access point – I want to be able to host a wifi network and have clients, my laptop and cell phone, connect to this. The advantage of doing this is I can set up a DNS to be able to define name for locations on the network. And not have to remember ip addresses of my network clients, or have to manually define a DNS for each client on the network.

2. KVM – For the most I don’t need to use windows for common tasks. The one thing I find myself using windows for is disk mounting tools like Daemon tools lite. So I want to host a virtual windows machine that I can use to mount a disk image and extract the files from the disk on the network.

3. Samba – This is a pretty simple, samba is a useful utility for hosting files on a network.

4. Nextcloud – I tried hosting this on a Pi and it was slow. So I want to try the latte-panda to see if works better with an intel processor and 2GB of RAM.

Approach:

In terms of approach I want to host the system on the 32 GB of internal storage and then /var on the 256 GB micro-sd card. Next I want to try getting the access point. And from there KVM. For KVM i can probably get away with the NAt interface as I plan on using everything with samba, so I don’t need a bridged network or anything like that. For samba i can host the files on /var/data. And for nextcloud I can store the files on /var/www/apache, or /var/www/nextcloud? I think I want to use apache for nextcloud exclusively and then use nginx as a reverse proxy server.

Hardware Plans

Router Pi – a pi that acts as a router, dns and wifi access point for the rest of the network. To avoid overloading it, not much should be included for the micro-SD card. Nginx can be used for hosting static content for dashgl. (8GB)

Latte Panda – Set this up with CentOS 7, to be used with the FBX SDK, Amazon Kindle SDK, and to host KVM guests on the network. 256GB of micro-SD card should also be included for storing roms and rom files on the network via samba. Nginx can also be used to host static files.

Libreboard – Set this up with Ubuntu or Debian (which ever one works), and set up apache, php and mariadb to host a next cloud server on it, and also host images and media over the network with samba.

PSP – psx and psp. 64GB or 256?

Pi test bench – Raspberry pi 3 with 5″ 800×600 monitor running retro pi for running and testing ports, also Use nes romhacks, classic snes games, gba

Pi screen test 1 – Raspberry pi 3 running 2.4″ 320×240 spi interface

Pi screen test 2 – Raspberry pi 3 running 3.5″ 320×240 hdmi interface

Pi Screen test 3 – Raspberry pi 3 running 3.5″ 800×600 spi interface

Pi Desktop – Raspberry pi 3B+ with i3wm desktop 64GB

——-

Pretty happy with everything except for the redundant devices hosting services on the network. The latte panda is the one device that I definitely need to use because of the KVM host. I wonder if I can install to the 32GB of included eMMC for kvm (hosting windows xp for daemon tools), fbx sdk and kindle. And then I could host the network with a usb wifi adapter (for just my computer and cell phone). And then use a combination of storage for the applications (nextcloud -> micro-sd, samba-> usb), and then use nginx to host multiple domains locally.

Hardware Selection for handheld concept

For the screen we can use: WINGONEER Raspberry Pi 3.5inch 800×480 60fps, which uses the GPIO. I think the documentation for this can be found in the raspi-wiki on this page. Assuming that this is the right display, then we need to write the following into the /boot/config.txt file.

#for raspberry pi 3b+/3b/2b+/b+
dtoverlay=dpi18
overscan_left=0
overscan_right=0
overscan_top=0
overscan_bottom=0
framebuffer_width=800
framebuffer_height=480
enable_dpi_lcd=1
display_default_lcd=1
dpi_group=2
dpi_mode=87
dpi_output_format=0x6f005
hdmi_timings=480 0 16 16 24 800 0 4 2 2 0 0 0 60 0 32000000 6
display_rotate=3

For the Battery I think we can use this UPS hat. Since it stacks, I think that means we can use a Raspberry Pi 3 (and underclock it down to match the Pi Zero), to get wifi and bluetooth. I don’t think we need the Raspberry Pi 3B+ or 4, since we generally don’t need the heat or extra power, since we’re generally going for 2d at 800×480.

Streaming from Framebuffer

https://lists.freedesktop.org/archives/gstreamer-devel/2013-July/041965.html

How to specify 16 bit, 32 bit?
How to specify width and height?
How to create new virtual interface?
How to stream data?

sudo ffmpeg -f fbdev -r 20 -i /dev/fb0 this_test.mpg

https://www.acmesystems.it/ffmpeg
Raspberry Pi Security Camera

Raspberry Pi Case: https://www.tindie.com/products/Ampersand/null-2-kit/
Jsmpeg: https://github.com/phoboslab/jsmpeg
Framebuffer Png: https://github.com/AndrewFromMelbourne/raspi2png