Building sgx modules for linux-omap 2.6.32

Steve, we are still working on the 2.6.32 based release. Will respond to you once we have completed the move.

Steve - I have built and verified the Graphics functionality against 2.6.32.  I have used the below components:

Graphics SDK/driver binaries at - http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/gfxsdk/latest/index_FDS.html (with a minor patch for display.h inclusion, and ARCH=arm)

Linux kernel at  http://arago-project.org/git/people/?p=sriram/ti-psp-omap.git;a=summary

This error comes from the function "PVRSRVRegisterDCDeviceKM" in deviceclass.c - if you have the debug build of the drivers, you should see the messages appropriately.

Prabindh Sundareson said:

Steve - I have built and verified the Graphics functionality against 2.6.32.  I have used the below components:

Graphics SDK/driver binaries at - http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/gfxsdk/latest/index_FDS.html (with a minor patch for display.h inclusion, and ARCH=arm)

This is the same SDK that I used.  Can you share the patch that you applied?

Prabindh Sundareson said:

Linux kernel at  http://arago-project.org/git/people/?p=sriram/ti-psp-omap.git;a=summary

Many of us prefer to use the linux-omap repository on kernel.org since it makes it much simpler to prepare patches and track upstream progress.  Have you tried building against the linux-omap 2.6.32 kernel?  This is where I encountered my issue

Prabindh Sundareson said:

This error comes from the function "PVRSRVRegisterDCDeviceKM" in deviceclass.c - if you have the debug build of the drivers, you should see the messages appropriately.

Correct.  How does one enable the debug build?  I tried the obvious approach of :

-export BUILD = release
+export BUILD = debug

in the top level makefile, but this did not enable the debug messages.

Thanks!

Steve

Its a single line patch for omaplfb_linux.c and ARCH=arm. You might have already done that,

-#include <mach/display.h>
+#include <plat/display.h>

----

--- GFX_Linux_KM/services4/3rdparty/dc_omap3430_linux_prev/omaplfb_linux.c 2010-01-25 09:22:33.000000000 +0530
+++ GFX_Linux_KM/services4/3rdparty/dc_omap3430_linux/omaplfb_linux.c 2010-01-25 09:25:55.000000000 +0530
@@ -45,7 +45,7 @@
 #include <asm/io.h>
 
 #if (LINUX_VERSION_CODE > KERNEL_VERSION(2,6,26))
-#include <mach/display.h>
+#include <plat/display.h>
 #else
 #include <asm/arch-omap/display.h>
 #endif
@@ -56,7 +56,7 @@ extern int omap_dispc_request_irq(unsign
 extern void omap_dispc_free_irq(unsigned long, void (*)(void *), void *);
 extern void omap_dispc_set_plane_base(int plane, IMG_UINT32 phys_addr);
 #else
-#include <mach/display.h>
+#include <plat/display.h>
 #include <linux/console.h>
 #include <linux/fb.h>
 static omap_dispc_isr_t *pOMAPLFBVSyncISRHandle = NULL;

Prabindh Sundareson said:

Its a single line patch for omaplfb_linux.c and ARCH=arm. You might have already done that,

-#include <mach/display.h>
+#include <plat/display.h>

Yes, I did apply that patch.  Could you tell me how to enable the debug messages?  As I mentioned in my previous posts, the obvious method didn't seem to work for me.

Any progress in this topic. Get the exact same results....

I too have received the same error and am wondering if anyone has found a solution...

I found two solutiojns.

1. Went back to an older driver version for the PowerVR chipset. Then I could use 2.6.32 with 3.1.0.9 driver

2. Upgraded to kernel 2.6.33 and then I could use the latest drivers.

Thanks ToolTech. When you "upgraded to kernel 2.6.33 are you pulling from linux-omap-2.6 or from linux-omap-dss2? I've got so many versions downloaded now I think I need to wipe out everything and start over and rather than spinning my wheels again I'd like to go down a known path. Any chance you're also integrating Qt into this build too?

Hi Tool Tech

ToolTech said:

1. Went back to an older driver version for the PowerVR chipset. Then I could use 2.6.32 with 3.1.0.9 driver

I have, in vain, tried to find the 3.1.0.9 driver. Could you please share the binary - it you still have it.

You may email it to me at:  m o r t e n @ b u g l e s s . c o . u k

Best,
   Morten