Search results

If you like playing detective, start with these photos. If not, look here, but don't be put off by the claimed response time; ED is pleased with the panel's speed. The way you worded that makes me worry. So I'll put this here so you don't embarrass yourself in Toulouse. Please don't mind me...

5:17pm UTC == 17:17 UTC =/= 17:17 in Germany (UTC+2 during daylight savings) So, which is it? f5 f5 f5

Going from an SGX530 at 200Mhz in the gigahertz Pandora to an SGX544MP2 at 532Mhz in the Pyra is a huge step up; in general, you're looking at more like a 5-10x jump in 3d performance. I wonder if that's enough for UE4 games. AFAIK the devboards don't have 3d drivers yet, but you could look at...

The OMAP5 has two fairly independent 32-bit SDRAM controllers, so it's fine to call it "dual channel". The OMAP3 has one 32-bit controller. This is in line with industry trends. Note that a DIMM slot is 64 bits wide, so when PCs went dual channel in the Athlon64 era, their memory bus went from...

Even they may not know yet. In the last audio discussion, they were still undecided between two possible solutions. The TWL6040 has two pairs of DACs and several independent amps. With it you could play sound over both speakers and headphones with independent volume (or even different audio, if...

Since it's SDL 1.3, try using SDL_GL_SwapWindow instead of SwapBuffers. In any case, do tell us when you have a solution.

If it's the graphics that slows it down, one thing you could do is to check the time after each game step and skip the drawing if you're late. Just don't skip more than 3-5 frames in a row, as that would be unplayable.

The i.MX51 only supports a CAS latency of 3 cycles, so there's no corresponding reg.

The DM3730 is meant to be mostly pin-compatible. But, even if it can work with the Pandora's PCB at all (at first sight, MMC1 might be a problem), it would require changing some resistors and upgrading the OS.

Has anybody looked at CONTROL_FUSE_OPP1_VDD1 (physical address 0x4800 2380) yet? The manual says it "differs between devices". It could be the same for chips produced at the same time, though.

To see what's connected to which pin of the OMAP3530, see the official Pandora Hacker Manual v1.00. The keyboard is handled by the companion chip, thus read by the OMAP through I2C. I've heard you need a kernel module to handle interrupts.

It uses display lists and glBegin(), so it won't be a straight recompile. And, the codebase is rather big, so I think it might be better to wait for a wrapper. As for speed, it got choppy at places on my geforce2mx, but that was at 1280x1024, so I think it's going to be fine on the Pandora...

the clear command (in the terminal) :)

d4b11a0eb7e93821959769204b020efc

Thanks, TheGrum, I followed your instructions and built the game successfully. However, you need to run it from the 'built' directory. Then, it works fine. :) Also, try the latest version of PenjinBase from svn: http://penjin.googlecode.com/svn/trunk You need to copy these files from the 7z...