<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"><!--status:success--><channel><link>http://www.mameworld.net/vlinde/</link><title>Ville Linde's blog</title><description>Transformation of Dapp into RSS</description><webMaster>info@dapper.net</webMaster><pubDate>Mon, 06 Oct 2008 21:18:44 -0400</pubDate><item><pubDate>Thu, 31 Jul 2008 00:00:00 -0400</pubDate><title>Unfinished business</title><description>One of the things I worked on about half a year ago, was a driver for Konami Cobra system., Cobra is a very complex system, comprising of 3 boards with a PowerPC CPU on each one. The first board with PPC603, can be considered as the "main" board as it runs the main game program. The second board has a PPC403, and does all the I/O handling, hard disk access and sound. The last board is a graphics board, with a PPC604 running a series of custom graphics chips (possibly designed by IBM...), Cobra doesn't seem to have 2D graphics capabilities at all, so getting something on screen wasn't exactly easy ;-) The screenshot below shows some hex numbers that are a debugging feature built in to Cobra software. Each number represents the "debug state" of the software running on each of the three boards. The numbers themselves are rendered as textured quads, and the whole process is done entirely on the graphics board. This of course required the emulation of the graphics board FIFOs, command buffers and texture uploading... ;-), </description></item></channel></rss>
