I couple years back I got all excited from a couple of press releases from VIA Technologies as I was certain that they were about to build the greatest handheld gaming device ever. A couple years later it’s nothing more then another piece of vaporware, but I think the concept of this system is still quite valid despite it never becoming a reality.
http://www.via.com.tw/en//initiatives/spea.../grace/moma.jsp
The MOMA Mobile Gaming Console is a PC in the shape of a mobile gaming console. It’s as simple as that, and what this gives you is the largest library of software imaginable. No need to port games, you can just run them natively. Now given the “modest” specs of this system you’ll be limited to games of the “pre-millennial” era but that just sounds fine to me. Also given that this is an x86 processor all of those emulators that make heavy use of assembly will run just fine. So given all of this the obvious question is why didn’t this console ever get made? I really don’t have a clue, perhaps it was to ambitious a system to make, a design ahead of it’s time. We’ll a couple years have passed, and a couple more will pass before we’re ready for the GP2X’s successor, and by then maybe this will look reasonable.
I’ll go through the system specs for the MOMA Mobile Gaming Console, and describe how I would change them.
System
» 533 MHz Eden-N Processor
» 133MHz Bus
» SSE and MMX instruction Set support
» 128MB DDR266 SDRAM
» High-Performance 64-bit DDR SDRAM Controller
» 20GB Hard Drive - Data transfer rates of up to 133 MB/s
CPU & RAM look good, but the hard drive seems like an expensive, battery consuming and potentially breakable part. Unfortunately there are several obstacles must be overcome when eliminating the internal hard drive. All currently viable solid-state non-volatile storage media have a finite number of writes that make them unusable with a “stock” operating system that expects to be able to page/swap. MRAM, PRAM, and FRAM are all “neat” but no where near production ready in densities large enough to hold an OS, it’s doubtful that this will change soon enough for them to be a viable option. This unfortunately precludes booting a regular copy of Windows 98 on the device; however it does not eliminate Linux. Luckily with an x86 processor WINE is available, and thus the need to boot windows is greatly reduced. The best bet would be to use a ‘live-cd’ like approach that is not entirely dissimilar from how the GP2X currently works. That is to say you boot off a read-only device, and then load your OS entirely into RAM. However unlike the GP2X I would like to see this done without the use of internal flash memory, simply because this is what leads to bricks. The device should instead have two SD card slots, and it should boot off the first one, and allow the second one to be used as auxiliary storage/SDIO. If the user tries to boot the device without an SD card in it, how to remedy the situation is displayed on the screen. Have the device come with a CD that has an application for Windows, Linux, and OSX that will properly format an SD card and put the OS on it. The booting card itself should be partitioned into two parts. One part should be read-only and thus act as the live-cd, the other part should be read/write, and used to store user preferences, and installed applications. The end result of all of this is that the user decides how much storage they need, and if that storage ever breaks it’s easy to replace. However, because the entire OS will be loaded into RAM, the amount of RAM the system has would need to be increased. 256mb should be plenty, and ideally if this could be done using a SO-DIMM, it could be upgraded later if need be.
Graphics
» VIA CN400 Digital Media Chipset - Integrates S3 Graphics UniChrome Pro Graphics Core
» 200Mhz Graphics Engine Clock
» 128-bit 3D Graphics Engine o Pixel rate up to 200 million pixels per second, 2 textures each
- Triangle rate up to 4.5 million triangles per second
- Microsoft DirectX 7.0, 8.0, and 9.0 compatible
- Microsoft DirectX Texture Compression (DXTC, S3TC)
- OpenGL™ Support
- Z-bias, LOD-bias, Polygon Offset, Edge Anti-aliasing and Alpha Blending
- Specular Lighting
» MPEG2 & MPEG4 Hardware decoding
I see nothing wrong with any of that. UniChrome has good open source drivers, and while not a powerful 3d accelerated by today’s standards it should be fine for a handheld device meet to player older games.OpenGL support is incredibly important as this opens up a lot of games that wouldn’t otherwise be possible. There are plenty of good games for Linux that require OpenGL hardware support. (Neverball, Chromium BSU, and Stepmania for example) For emulation this puts the Playstation and the N64 within striking distance.
Audio
» VIA Vinyl Six-channel Audio
» Full Immerzio™ Gaming support
- EAX® 1.0, EAX® 2.0
- DirectSound3D®
- I3DL2™
- A3D® 1.0
Six Channel Audio… On a handheld… We’ll that’s just a side effect of this being a VIA based platform and Vinyl being the chip that they like to stick on things. Any of VIA’s on-board sound solutions would be fine.
LCD Display
The MOMA Mobile Gaming Console integrates a 4", 640x480 TFT LCD screen. In supporting up to 640x480 resolutions, the MOMA Console can easily play all PC games natively.
640x40 is a necessity. This is the lowest resolution many PC games support, and so this is where we need to be. Running a game designed for 640x480 at 320x200 makes the text look absolutely hideous. Adding a touch screen that could be used to mimic a mouse would be a really nice addition.
Hard Drive
The MOMA Console includes a single 1.8" 20GB hard drive for storing the OS and the game data. This is sufficient to store a large library of games and digital media content. This is transferred to the system either via wireless LAN or by USB2.0 pass-through to a PC.
I’ve already gone over what they need to do about the hard drive – get rid of it.
Batteries
Prismatic Lithium-Ion batteries are the current favorite choice for the console. Two packs of batteries are provided so that the batteries can be hot-swapped for continuous, uninterrupted play.
Lithium-Ion batteries are good, proprietary Lithium-Ion batteries are bad however. I believe the device should use RCR-V3 batteries. (http://en.wikipedia.org/wiki/RCR-V3), and it should ALSO be capable of using AA’s as well. Both NiMH’s and RCR-V3 are good options, and there’s no reason that we can’t have both of them.
Port List
The ports that are user-accessible on the MOMA Console include:
» Power jack (DC barrel type)
» 2x USB 2..0 jacks (Type A host style)
» 1x Compact FLASH type II slot
» 2x battery slots (as specified as handgrips)
» 1x smartcard card slot (15mm x 1mm slot)
» 2x 1/8” stereo jack for headphones out & microphone in
» 1x 1/8” stereo jack for composite video out
» 802.11b wireless LAN
Ditch the smartcard slot, and the Compact FLASH type II. However I’d like to keep the wireless and bump it up to 802.11g. Since we have a microphone jack the device would make for an excellent wifi phone. As I wrote earlier, we’ll need two SD card slots so those will have to be added.
Button List
» D-pad (WASD)
» L/R triggers
» Cluster of 4 action buttons
» Line of 6 auxiliary function buttons
We defiantly need a D-pad, and we’ll need some software that allows us to map the keys/buttons however we want.
So that’s what I want, the MOMA Mobile Gaming Console with a few tweaks made to it.