Porting OEM

---

A little help from the cookers out there.. I've seen XIP porting and SYS porting, but what about OEM porting?

I'm not pertaining to the packages in the OEM folders, that one is easy

I'm pertaining to the files in the OEMDrivers folder. Can someone verify my observations/questions/assumptions?

- The OEMDrivers has the same file folder structure from porting XIP (i.e., has imageinfo.bin, imageinfo.txt, S001, S002, etc.) so porting it needs to have some sort of g'reloc. If that's the case, how is it done? (I'm thinking changing the directory to SYS for the meantime and do a g'reloc)
- in reverse to the above assumption you can't port OEMDrivers because it's device specific (some threads I've read this one, but I'm skeptical about this). If so, this thread is useless and don't waste time replying

You are partially right - you can't use all drivers but some of them - e.g. you can use bluetoothsetting.dll from TouchHD in Toch Pro OEM. It's not so easy - you have to check every driver step by step to avoid no boot

qsqa ia right. Also just to add, Greloc works with the .VM module inside the SYS. So renaming the OEM to SYS is not going to achieve anything

Greloc is used to realloc all the modules based on the information in your .VM module

Originally Posted by ababrekar

qsqa ia right. Also just to add, Greloc works with the .VM module inside the SYS. So renaming the OEM to SYS is not going to achieve anything

Greloc is used to realloc all the modules based on the information in your .VM module

BTW - I think that g'reloc is also doing its job in OEM - when I put new XIP module in OEM I can see that number of modules in g'realoc window is increased (but maybe I'm paranoid )

From which device do you want port OEMDrivers (I'm guessing that you're porting to TP?)

Originally Posted by qsqa

BTW - I think that g'reloc is also doing its job in OEM - when I put new XIP module in OEM I can see that number of modules in g'realoc window is increased (but maybe I'm paranoid )

From which device do you want port OEMDrivers (I'm guessing that you're porting to TP?)

lalala...

Yeah I'm porting to TP, just like you are Well when I've tried putting some of the OEM files (the one in the folder) in blackstone but then it's not easy as it seems primarily because I thought you need to reloc also the files, which I would know how to do.

Anyway, if that's the case then I'm not going to bother at all Still happily tweaking OEM package files over and over... btw qsqa you haven't answered my question to your ROM thread-- have you successfully ported the Facebook functionality yet?

I forgot, sorry - still fighting with 1.03

I didn't touch apps which are dedicated fro Touch HD (resolution), first of all I want to port drivers then will look for apps

Originally Posted by qsqa

I forgot, sorry - still fighting with 1.03

I didn't touch apps which are dedicated fro Touch HD (resolution), first of all I want to port drivers then will look for apps

It's not resolution specific but good choice on porting 20757 it's really fast even on stock!

Honestly saying - if you are looking for a stable base, 20757 is better than newer builds like 20931