https://github.com/o-marshmallow/Pong-UEFI

See also:
There’s one UEFI-based game I have not mentioned: Maze, by Tim Lewis. He’s got multiple blog posts on how the code works. He just relicensed it to BSD:
https://uefi.blogspot.com/2017/04/maze-game-source-code.html
https://uefi.blogspot.com/search/label/Maze
https://svn.code.sf.net/p/syslibforuefi/code/trunk/
Look at the game/games tags for other UEFI-based games.
There’s a CHIP-8 emulator written for most platforms, now including UEFI. The executable uc8.efi is built using the GNU-EFI toolchain, not the Tianocore toolchain.
“CHIP-8 emulator as an UEFI application”
Usage: uc8 FILE [ROM]
Follow the instructions on your screen. In case of trouble, press Z.
About CHIP-8, Wikipedia says: ”
There are a number of classic video games ported to CHIP-8, such as Pong, Space Invaders, Tetris, and Pac-Man. There’s also a random maze generator available. These programs are reportedly placed in the public domain, and can be easily found on the Internet.”
https://github.com/Reisse/uefi-chip8
https://en.wikipedia.org/wiki/CHIP-8
“Flappy Bird for UEFI written in x86 Assembly”
Fabian Mastenbroek has written Boot2Flappy, a UEFI port of the game “Flappy Bird”. It is a new project on Github, less than a week old, “FreshMeat”, as they used to say.
Nikolaj points out that there’s a UEFI port of the game Tetris …but I can’t find the source, only the binary:
As mentioned in the below Defiant UEFI game engine post below, there’s a Tetris for UEFI on Github with source, unclear if this is a different one than above:
https://github.com/swmicro/Tetris
If someone has some spare time, please port MAME to UEFI. Please!
There’s a Github project with a UEFI maze game on it, called Firmware-Maze:
https://github.com/liute62/Firmware-Maze
Appears to be mostly a single-file game:
https://github.com/liute62/Firmware-Maze/blob/master/src/final3.c
I’ve not built it yet, I’ll try that later, I still have to read CodeRush’s latest UEFI SecureBoot tutorial…
Some other UEFI games:
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Discover the Desktop
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
News from coreboot world
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Just another WordPress.com site
Hastily-written news/info on the firmware security/development communities, sorry for the typos.