Doom On A Picture Key Chain


Alright, so Doom isn’t actually running on the key chain itself, but rather a BifferBoard: a small 150MHz x86 containing ethernet, serial, and even USB with only one watt of power consumption! The project is to show how easy it is to program the BifferBoard and getting it talking to other hackable items – such as the picture key chain for a display. Doom does appear a bit slow, but [Biff] figures its do to how haphazardly it grabs keyboard input over SSH.

16 thoughts on “Doom On A Picture Key Chain

  1. The project makes use of the ST2205 picture frame hacking project I started: . It’s a shame that the guy who did this hack kept the remood licensing blurb intact, but ripped away my credits (probably by accident, but still.)

    Other than that, nice hack! I hadn’t thought about porting games to the picture frame yet. Though it may have been a better idea to actualli incorporate the code to talk to the display into SDL instead of just the Remood-code.

  2. Please note, this was not my hack, I just submitted it because it looked neat.

    To Sprite: It’s not like people give credit to Linus every time they mention Linux so maybe people feel it’s just common knowledge that you hacked the frames and don’t need to mention it? Anyhow, I’m sure if you drop Noshbar an email he’ll change his write-up – I’ve had a few email exchanges with him and he seems like a really nice chap – I’m sure he’d not want to offend.

  3. I’ve always wanted to open one of these babies up, but I haven’t gotten one yet. I really need a LCD Screen for my projects.

    Has anyone done a “tear down” of picture key chain?…

  4. Bifferos: It’s not the text I’m concerned at, it’s the source he posts that hacks interoperability with remood that misses the credits (and the GPL3-license too, by the way, which got ‘downgraded’ to gplv2.) My first idea was to mail him to notify him about the problem, but unfortunately I couldn’t find a mail-address. I kinda hoped he’d contact me via my post here and we could resolve the problem that way.

    Sorry for the license/credits-nitpicking, but after reading about tivo’ization etc, I kinda see things like this as a Big Deal, perhaps too much so.

  5. Bifferos: Ofcourse not; hacking should be encouraged! And in this case, because my code is GPL too, it shouldn’t take more than copypasting a few more lines from the original sources and he should be fine.

    IANAL and I’m not planning on acting like one ;)

  6. Oh man, it’s quite cool to be mentioned on a site I read daily :D

    Sprite, I am terribly sorry about the credits being torn out, that was by NO means intentional.

    The whole thing is in insanely quick and dirty hack, and not really for consumption yet, as I’m quite embarassed by it all (hence, it doesn’t have a direct link from the lame-inosity that is my “front page”).

    I’ll gladly fix it up tonight, I am truly sorry about the hassle I’ve caused.

  7. > The whole thing is in insanely quick and
    > dirty hack, and not really for consumption
    > yet, as I’m quite embarassed by it all

    Well, you did post to the Bifferboard group,
    which has 136 members :)… I guess I
    misinterpreted this to mean it was OK to
    post it on, looks like I should have
    asked first (sorry). Can’t wait to try this
    myself though!

  8. I suppose you have a point there Biff :)
    I see the Google Group more as a support group :P

    I just didn’t anticipate people caring about this, but I’ve learnt several things today!

    Anyway, I’ve added the credits in for now, and will separate the files later.

    Making a change to SDL is quite a good idea, but one that would perhaps require a lot more thought and planning than my usual random misfirings of lucky successful compiles…

  9. cptfalcon: There’s the LeopardBoard, has a 10/100mbit ethernet port (plus a bunch of other ports), ARM9-based (so not x86), 216MHz I believe. 256MB flash storage, 128MB RAM, SD card slot. $84 by itself if you buy it direct (the $99 quote includes a camera, the board was designed to show image processing, but can be used for general purpose too)

  10. cptfalcon: Why would you want to avoid x86? I can understand you want low power and low cost, which are usually attributed to ARM/MIPS, however this isn’t a problem with many of the x86 compatible SoCs. You get the benefit of not needing to cross-compile, being able to test your applications on an x86 desktop machine (if it’s not x64!) before deploying to an embedded device, ability to (easily) run stuff like Qemu, and to run distributions like Gentoo, Debian and Slackware without compiling them from source. I know this is all changing and distros are slowly adding support for ARM, but having played around with OpenWrt for some time (my only option for running Linux on MIPS embedded devices), I’m now sold on x86 unless really fast IO is needed.

    Incidentally, depending on your definition of ‘cheap’, the cheapest ethernet-enabled Linux devices are almost certainly hacked routers (see, plenty to chose from). Pity they discontinued the Edimax BR-6104K which used to be available for just 15 uk pounds!

Leave a Reply

Please be kind and respectful to help make the comments section excellent. (Comment Policy)

This site uses Akismet to reduce spam. Learn how your comment data is processed.