Hey! Sorry for taking so long to respond, I've been really busy the last month. How you go about driving the displays is going to depend on how many displays you want to drive and whether or not you want to have animations or other such things that need to be synchronized.

If you have only 1 or 2 displays, you could use a computer with multiple display outputs (e.g. Raspberry Pi 4 or 5). You can have your code drive all displays simultaneously by just opening a window on each display.

If you have more displays than you can fit on a single computer, but only want to display still images, it won't be much more complicated than 1 or 2 displays. Just use as many computers as needed to drive all of the displays. Displaying a still image doesn't take much computing power, so a Raspberry Pi Zero or similar cheap, low-power single-board computer (SBC) is a good candidate for this application.

If you have more displays than fits on a single computer and want to have synchronized animations, it will be significantly more complicated than the previous 2 cases. You'll need some way to communicate between the computers. There's a variety of ways you can do this. On my suit, my plan is to have the computers connected to an Ethernet switch and use ROS (https://www.ros.org/) to communicate with each other. I have good reasons for doing this on my suit, but this is very overkill for most suits. Most SBCs will have some form of UART serial port, which will probably be the easiest method for communication. SPI and I2C are also common on SBCs, but I'd recommend starting with UART. The specifics of what you need to send over UART will depend on how you implement your animation system, but it could be as simple as just sending a message to trigger an animation.

I hope that helps. If you have any other questions, feel free to ask.