The closed stuff is platform independent and hopefully relatively stable. TI/PowerVR have same code running on other omap2 based devices both with symbian and linux (hopefully).

The tricky part is understand what mbxaccess.ko and omaplcd.ko (main part that needs fixing IMO) is trying to do and adapt it to N810 specific video driver situation which is a bit complex and different from what current omaplcd.ko is expecting. and we have sources for that.

The first thing I would try it to remove everything that touches DISPC (OMAP builtin display controller) registers (vsync flipping code, power management code), IMO our omaplcd.ko implementation should be purely memory based = only giving proper framebuffer memory to rest of powervr code and not touching any hardware directly. It should also not allocate any extra memory if possible (this is what fails now), omapfb already has three allocated planes/buffers, the last one even has space for two 800x480 frames.

Then there should be hook how to schedule display update via current omapfb. Possibly from current omaplcd vsync code (which currently messes with DISPC registers when trying to switch visible buffer with back buffer).

Hopefully that's all for showing MBX output properly.

Then there is mbxaccess which gives access to 3D chip to user space PowerVR libraries. I'm not sure if this one needs to allocate some additional memory too (for textures?) or needs other fixing.