I've got an iPhone with the NES emulator and the BSD user tools running on it.
My understanding is that they don't have direct access to the graphics hardware working yet. So the picture is being copied to the framebuffer, a pixel at a time. So things that update the screen often, like a game, eat up CPU time quickly, even though producing the image(NES video emulation) can be done on a 386 with hardly any frames dropped.
The processor(s) is fairly powerful in the iphone and there is something like 128 MB of ram in it. It's effectively a pocket MacOSX system underneath it all.
Now that we've thrown 'em off the trail, use the form below to get in touch with the people at Engadget. Please fill in all of the required fields because they're required.
I've got an iPhone with the NES emulator and the BSD user tools running on it.
My understanding is that they don't have direct access to the graphics hardware working yet.
So the picture is being copied to the framebuffer, a pixel at a time. So things that update the screen often, like a game, eat up CPU time quickly, even though producing the image(NES video emulation) can be done on a 386 with hardly any frames dropped.
The processor(s) is fairly powerful in the iphone and there is something like 128 MB of ram in it. It's effectively a pocket MacOSX system underneath it all.
They're working on it, though! I can't get it to build right, I wish they'd release binaries.