[Openpvrsgx-devgroup] Building the 1.7.862890 branch for x86

[Julius Schwartzenberg]

I forgot to reply to the list.

Hi Nikolaus,

Thank you so much for the fast elaborate response!!

On 25.05.24 12:22, H. Nikolaus Schaller wrote:
 > I've tried to get it compiled but it fails with:
 >
 >    MAKE    drivers/gpu/drm/pvrsgx: cedarview
 > scripts/Makefile.build:41: 
drivers/gpu/drm/pvrsgx/1.7.862890/pvr/Makefile: No such file or directory
 > make[8]: *** No rule to make target 
'drivers/gpu/drm/pvrsgx/1.7.862890/pvr/Makefile'.  Stop.
 > drivers/gpu/drm/pvrsgx/Makefile:64: recipe for target 
'drivers/gpu/drm/pvrsgx/pvr' failed
 > make[7]: *** [drivers/gpu/drm/pvrsgx/pvr] Error 2
 > scripts/Makefile.build:481: recipe for target 
'drivers/gpu/drm/pvrsgx' failed
 >
 > So is drivers/gpu/drm/pvrsgx/1.7.862890/pvr/Makefile missing?

I do not have this file either. I guess we are using different steps to 
compile. What I am doing on Debian:
1. I copied /boot/config-6.1.0-17-686-pae to .config
2. Ran 'make menuconfig'
3. Disabled the GMA500 driver
4. Enabled the CDV driver
5. Save
6. Ran 'make bindeb-pkg'

Note that I'm using a 32-bit system. I have no idea if the driver could 
be compiled for 64-bit too, there were never any AMD64 binaries for the 
userspace part.

This triggers a full build which eventually should reach the CDV/PVR 
driver. Are you trying to only compile the driver itself?


 > So essentially it means to backport the 1.17 code for 
OSTimerCallbackWrapper
 > to make this compile. The trick is to provide a private struct which 
has the
 > struct timer_list as its first element and then using the 
from_timer() macro.
 > Sort of subclassing with additional variables in the subclass.

Alright, I guess it means more copy-pasting of the parts related to 
OSTimerCallbackWrapper? I could try that I support and see where I end up ��
Many thanks for analyzing this!! It will surely help!


 > Hope this helps. And making me able to compile your code would allow 
me to
 > even verify my theory.

Yeah that would be great, let's try figure out why it seems to behave 
differently on your end.

Best regards,
Julius