Sonoko, About

PostPosted: Sun Dec 23, 2018 11:11 am
by madame

(System Diagram)

Sonoko is a big x11-terminal able to manage up to 3 physical LCDs and 5 virtual screens (with/out Xinerama), all made with embedded Linux boards.

About motivation

PostPosted: Tue Jan 08, 2019 11:30 am
by madame
The metalworking effort looks painful on the fingers, and boards do crash, we are still on it :say-yee:

Code: Select all
  _______________________           
< Have you mooed today? >         
  -----------------------           
     \   ^__^                       
      \  (oo)\_______               
         (__)\       )\/\           
             ||----w |             
             ||     ||             
                                   
Kernel panic, Rebooting..         


We neither have a CNC, nor a 3D printer, but we got a lot of industrial waste. Plastic frames, metal chassis, and polycarbonate frames. It would be a shame trashing them so we are recycling. That in and of itself does not make what we're doing bad or a waste of time, we're having fun (other than injuries :asd: ... I can assure IveLegacy's finger is now fine, like brand new), learning, reducing e-waste by reusing things we have

cool, ain't it? :say-clapclap:

More to come...

About Motivation. This Xterminal doesn't really make any noise. Even the noisiest machine can be comfortably used in remote, and everything is fine.

Except ... ops, the new firmware still has some issue with Xinerama :asd:

About Motivation

PostPosted: Tue Jan 08, 2019 8:57 pm
by LordCrimson
madame wrote:About Motivation.


Definitely, you wouldn't see the ups "cool factor" of any developer's computer.
Can you still use mypaint or inkskape with a graphics tablet?
so what's the point of using an x11 terminal? :say-sticazzi:

About Motivation

PostPosted: Wed Jan 09, 2019 8:38 am
by ivelegacy
Apps like mypaint, inkskape on graphics tablet require xf86-input-xxxxx or xf86-edev; we have Waltop tablets and xf86-input-wacom is intended that Waltop tablets be supported by the Wacom X driver. However, things have been in a state of flux both in the kernel and with the Wacom and evdev X drivers, and it is possible that the Waltop tablet might be better supported by the evdev driver. The advantage the Wacom driver offers is stylus pressure on a Bezier curve rather than the simple linear curve of the evdev driver. This enables setting the stylus to firmer or softer feel. In addition, the Wacom driver has a pressure threshold setting, while the evdev driver currently lacks it. With evdev, minimum pressure is always set to 0 and there is no option to vary that. If the stylus is too sensitive you can decrease the pressure sensitivity with the “Threshold” parameter, and a third benefit is the availability of the MapToOutput parameter on a multi-monitor setup.

This stuff is not neat and works better on a Linux/PC, and exporting/importing functionalities from X-server (mypaint, inkskape)to the X-client (Sonoko) is a complete challenge.

We haven't started implementing yet... work is not progressing steadily, but Ive and I have worked on it enough so that we know what we are dealing with.

an interesting similarity

PostPosted: Wed May 08, 2019 5:09 am
by madame
.. an embedded Linux workstation running off an image unpacked from storage for each new user, is both easier to maintain and more cost-effective. You can do this relatively simply using PXE boot on any machine you can secure the BIOS/EFI/OF for. Funnily enough, in these use cases, a LOT of RAM (say, 32 GByte) would make it possible to run a full desktop system off a RAMdisk without any customization work or any kind of local storage, with reimaging taking only seconds (assuming GbE Ethernet networking, or faster) -- the entire filesystem is transferred as a single XZ-compressed image, or as a few trees depending on the user logging in. Unfortunately, most embedded machines are limited to 4 GiB or less, which is not really enough for a full-fledged GUI Linux distribution.

Many Xterminals made in the 90s ran only the X server on the terminal, and the applications themselves on bigger iron (i.e, as "thin clients"). The difference is that the machine runs everything locally, from a ramdisk. Nothing new. It's just that having big-mem embedded machines would make that so much better. The CPUs are easily powerful enough already.