salamantecas wrote: ↑Sun Jun 12, 2022 3:41 pm
I have some questions with possible situations
1.- If I have configured a screen with an sd in the Mister and everything has been executed well, if I wanted to do it with the same screen in another different sd, we simply execute the installation of:
https://raw.githubusercontent.com/ojaks ... staller.sh
-O - | bash
which downloads and setup the software (init and daemon).??
Correct and is stated in the documentation
2.- In the event that someone executes a configuration with 2 screens, either tty2oled and tty2tft or even 2 tty2tft, a udev rule is needed, but I have verified how in certain routes it is difficult to write files, I do not know if it is because of the permissions or because of windows or another reason . would it be possible to implement a wget command that streams the 80-ttyusb.rules file to the correct path directly using the ssh command?
this would make the job easier
You can setup a pair of tty2oled and tty2tft without an udev rule, but then you are bound to an USB port order for the appropriate tty* device. For example tty2oled is plugged in to MiSTer's USB hub port #2 and will become ttyUSB0 (1st found device). tty2tft goes to USB port #4 and will become ttyUSB1 (2nd found device). You have to keep that in the way that tty2oled has to be plugged in to an USB port < the next tty device.
The udev rule can be used to differentiate the named devices, e.g. ttyUSB0 (tty2oled) will become ttyMYNAME and ttyUSB1 (tty2tft) will become ttyOTHERNAME. That way you can swap both devices USB ports at MiSTer and are still having your named device at ttyMYNAME and ttyOTHERNAME.
Needless to say, regardless of the solution chosen, this must be taken into account in the appropriate INI files.
For two tty2tft devices (same for two tty2oled) udev doesn't work as there aren't enough different device data udev could read out from the devices - the are practical identical to all devices of the same type.
But remember that these are many (very technical) details we were already talking about by PM. If in doubt, you have to do some research and learn about udev and Linux' devicename scheme.
Also remember that we were already talking about the 80-ttyusb.rules. Create one in the folder /media/fat/tty2tft (you can use 80-ttyusb.rules.example as a template) and run update_tty2tft.sh
. This routine will detect that you want use an udev rule and copies that file to the correct place and also ensures to keep that file there because a more complex MiSTer update could delete your udev rule.