When you’ve got an inexpensive laptop computer and also you understand you’ll be able to’t join a second monitor to it, what do you do? Properly, in case you are [Pierre Couy], you seize a Raspberry Pi and put collectively a digital display answer.

Like all good initiatives, this one began with some objectives and necessities:

• Low latency
• Redable textual content
• Not less than 10 frames per second
• Quick catch up if the distant display falls behind
• Low-bitrate encoding; no {hardware} acceleration
• A DHCP server on the Pi to handle the community
• Energy management for the hooked up monitor

Since Linux has such flexibility, it was doable to sew the system collectively utilizing current parts. The versatile ffmpeg dealt with the streaming. There was, nonetheless, a good quantity of troubleshooting essential to trace down some points utilizing Wireshark.

If you wish to strive one thing like this your self, the information are on GitHub. Truthfully, although, the perfect a part of this mission is seeing how the instruments work together and the troubleshooting steps. For many laptops, this isn’t essential and that’s clearly the perfect answer.

When you’ve got the alternative downside of desirous to stream the Pi’s video over the community, you are able to do that or simply leverage X11. Then once more, when you have a Pi, do you even want the laptop computer?