[Touch Cruise ROM Development] Chainfire:
Helloes!

I was asked to visit this topic. I did visit it some weeks ago and read up a bit (didn't reply) but I got a headache from people claiming A and B and neither added up. No offense intended, just that I've been very very busy myself lately and didn't feel like correcting them at that moment, but forgot to get back it. Besides, some of the things people said and thought are things we said and thought as well before we got stuff working.

Could somebody be so kind as to post a writeup of exactly where you guys are in the process, what works, what doesn't, which files and versions of these the different attempts use (i.e., from which HTC-CA release).

Note I think you should really focus on the last set (from the 19th) of files as it's the most compatible and fixes some issues (be damned if I recall which ones though).

I did skim the last few pages of the thread, seems there's a lot going on.

I can tell you a few things right now though:

The 'dual' ddi trick somebody was trying will not work. Period.

Changing the DPI (logicalX/Y) settings will not effect anything worthwhile, aside from making the system look weird. You can see the combination of DPI and resolution as sort of an 'effective resolution' - it's used mainly for deciding size of text rendering. For example, VGA devices are 640x480 and have a default DPI setting of 192. This DPI setting gives you exactly the same text size as a 320x240 device with a DPI setting of 96 (default) if the screen is the same physical size. That's what it's for.

You shouldn't be messing around with the registry key where DDI.DLL is also listed (though you probably need to replace the DDI.DLL itself, as I think was done by some folks here) - the 'default' settings are correct.

LocalHook vs RemoteHook as soft- vs hardware driver is not relevant. The D3D driver is not a hardware driver itself - though it uses the OGL driver, which also uses the ahi2dati and ddi drivers, which are hardware drivers. Besides, it is fully possible to use a locally hooked hardware driver, though some technical details should be taken into account.

Furthermore, the 'flickering' issue we had with the HTC-CA drivers was partly a demo issue, partly a driver issue. We couldn't get the screen to update properly, so we used a trick, and that trick caused the flickering. However, the screen update has since been fixed and the flickering causing workaround has since been removed from test apps. So this is not what you are seeing.

However, these things may be related. The hacked drivers use specific memory locations, interrupts etc and these are device specific. They are likely different on the Polaris, and thats ultimately the reason the current drivers only work on the Kaiser. Ofcourse, different versions of the other dependant DLL's can also cause issues.

Anyway, if you guys reply with all the info you got so far, I'll ask the guy who actually got the drivers to work on the Kaiser if he could maybe take a look at it - understand it's hard for him to do without actually having a Polaris, though.

Last but not least, people do complain about not having 2D drivers yet and think we aren't working on it at all anymore. We are, however you must understand building 2D drivers from scratch is a massive and extremely timely operation. We're actually right now looking for drivers from another MSM7x00 based device which does seem to have them (though no ROM dump is yet available), to see if we may be able to adapt those.

</essay>