[Openpvrsgx-devgroup] Building the 1.7.862890 branch for x86

H. Nikolaus Schaller hns at goldelico.com
Mon May 27 20:05:14 CEST 2024


Hi Julius,

> Am 27.05.2024 um 12:59 schrieb H. Nikolaus Schaller <hns at goldelico.com>:
> 
> Some idea to analyse this would be to pile up all DDK revisions in one git branch and use git to detect the
> changes for each one. This is sort of reconstructing the version control system contents where we have
> snapshots from.

I have worked on that and generated a new branch (by a script):

	https://github.com/openpvrsgx-devgroup/linux_openpvrsgx/compare/master...pvrsgx-history
	https://git.goldelico.com/?p=letux-kernel.git;a=shortlog;h=refs/heads/pvrsgx-history

Some notes:
- this branch is based on Linux v6.8-rc4
- DDK subdirectories have been moved from drivers/gpu/drm/pvrsgx/pvr *or* drivers/gpu/drm/pvrsgx/eurasia_km to drivers/gpu/drm/pvrsgx/ddk
- each commit is also tagged with the DDK version number
- to see the versions: git log --oneline -12
- files that have been deleted in a newer version are still included
	- i.e. it piles up for example the drivers/gpu/drm/pvrsgx/ddk/pvr/services4/system files)
	- so that the head of this branch is not the same as letux/pvrsrvkm-1.17.4948957 but contains a lot of intermediate stuff
	- to view: git diff --stat ddk-1.17.4948957 letux/pvrsrvkm-1.17.4948957 drivers/gpu/drm/pvrsgx/
- this way of reconstructing the commits allows to check for diffs between version
	- e.g.: git diff --stat ddk-1.9.2188537 ddk-1.9.2253347
		shows which files have been touched between DDK 1.9.2188537 and 1.9.2253347 code
- sometimes changes only involve SoC integration in drivers/gpu/drm/pvrsgx/ddk/pvr/services4/system/
- sometimes they include Linux API changes in drivers/gpu/drm/pvrsgx/ddk/pvr/services4/srvkm/env
- to see changes of single files
	- e.g.: git diff ddk-1.7.862890 ddk-1.17.4948957 drivers/gpu/drm/pvrsgx/ddk/pvr/include4/pvrversion.h drivers/gpu/drm/pvrsgx/ddk/pvr/include4/sgxapi_km.h 

Hope this helps to better understand how the DDK releases are related and what the code is really doing...

What I already learned is that sgxapi_km.h has changed every now and then.
And that there are often only cosmetic changes (white space lines removed, comments added).

BR,
Nikolaus



More information about the openpvrsgx-devgroup mailing list