I'm trying to build the TI supplied Linux kernel driver modules for the PowerVR accelerator chip in the OMAP3. I have a GIT tree pulled from the linux-omap-2.6 tree, and a set of cross-compiler tools built and installed. I can build the kernel itself, but when I try to build the TI supplied code: 1) It references "asm/semaphore.h" rather than "linux/semaphore.h" - as asm/semaphore no longer exists in the code the build fails. I can work around that by creating a symlink to linux/semaphore.h. 2) It then references "asm/resources.h", which is ALSO gone. I'm guessing it needs "asm-generic/resources.h". 3) However, at that point the compile REALLY dies, with the code looking for "asm/arch/resources.h". If I link "arch/arm/include/asm" to "asm/arch", then I get a large number of errors: CC [M] /space/src/OMAP35x_Graphics_SDC_3_00_00_06/GFX_Linux_KM/services4/srvkm/env/linux/kbuild/../../../../../services4/system/omap3430/sysconfig.o CC [M] /space/src/OMAP35x_Graphics_SDC_3_00_00_06/GFX_Linux_KM/services4/srvkm/env/linux/kbuild/../../../../../services4/system/omap3430/sysutils.o In file included from /space/src/OMAP35x_Graphics_SDC_3_00_00_06/GFX_Linux_KM/services4/srvkm/env/linux/kbuild/../../../../../services4/system/omap3430/sysutils.c:28: /space/src/OMAP35x_Graphics_SDC_3_00_00_06/GFX_Linux_KM/services4/srvkm/env/linux/kbuild/../../../../../services4/system/omap3430/sysutils_linux.c:154: error: variable 'cnstr_id_vdd2' has initializer but incomplete type /space/src/OMAP35x_Graphics_SDC_3_00_00_06/GFX_Linux_KM/services4/srvkm/env/linux/kbuild/../../../../../services4/system/omap3430/sysutils_linux.c:155: error: unknown field 'type' specified in initializer /space/src/OMAP35x_Graphics_SDC_3_00_00_06/GFX_Linux_KM/services4/srvkm/env/linux/kbuild/../../../../../services4/system/omap3430/sysutils_linux.c:155: error: 'RES_OPP_CO' undeclared here (not in a function) So does anybody have an good advice on this? -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
