[Openpvrsgx-devgroup] New version of letux-pvrsrvkm rebased on v5.5.0-rc5 available

H. Nikolaus Schaller hns at goldelico.com
Mon Jan 6 17:45:07 CET 2020


> Am 06.01.2020 um 17:38 schrieb Tony Lindgren <tony at atomide.com>:
> * H. Nikolaus Schaller <hns at goldelico.com> [200106 11:06]:
>>> Am 06.01.2020 um 11:53 schrieb H. Nikolaus Schaller <hns at goldelico.com>:
>>> A new version of our holistic PVR/SGX driver is available
>>> Kernel: v5.5.0-rc5
>>> Result: letux-pvrsrvkm
>>> Github: https://github.com/openpvrsgx-devgroup/linux_openpvrsgx/branches
>>> Components:
>>> letux/omap-sysc-prm-gfx
>> ^^^ this branch is melting down by material merged into upstream
>> https://github.com/openpvrsgx-devgroup/linux_openpvrsgx/commits/letux/omap-sysc-prm-gfx
>> We only have left over the following:
>> a0e781c12f7b8 ARM: DTS: am33xx: add sgx gpu child node
>> 8fad18716f338 ARM: dts: Configure rstctrl reset for SGX
>> 4673b1037808c ARM: dts: omap5: convert IOMMUs to use ti-sysc
>> dd5ecd5613fe7 ARM: dts: omap4: convert IOMMUs to use ti-sysc
>> d9c58108a5c66 ARM: dts: dra74x: convert IOMMUs to use ti-sysc
>> 6b10142b63f67 ARM: dts: dra7: convert IOMMUs to use ti-sysc
>> 2ea51723bcf3c ARM: dts: omap5: add IVA clkctrl nodes
>> dd864e246b1d7 ARM: OMAP2+: pdata-quirks: add PRM data for reset support
>> I am not sure if we need all of them but they were in Tero's and Tony's trees.
>> The first two seem to be necessary for am335x and may have been forgotten to merge to linux-next.
>> IOMMU may not be related to SGX.
>> The last one may be needed for am33xx rstctrl.
> I think sgx has no iommu on the SoC, it just the sgx internal mmu, so
> those changes should not be needed.
> Anyways, the branches should not be rebased as that makes it a moving
> target for anybody trying to develop against them. It's better to
> set up a new branch for something that needs rebasing.
> So could you please update your scripts to start building kernel
> version based branches for example?

Yes, that is the scheme used to build LetuxOS kernel versions.

> I suggest we have pvr-v5.4 branch and pvr-v5.5 branch, then pvr-v5.6
> branch after -rc1 and so on. For most part I can see the old branches
> just get forgotten, but I can see folks wanting to backport
> some patches to the pvr-v5.4 branch as that a lts kernel.

Unfortunately we have to wait for v5.9 for the next LTS...
So indeed backporting is important.

For the moment it should suffice to cherry-pick the new patches, since
IMHO they indeed have no (big) dependency on the base.

> If you want to keep merging things together into some master branch,
> then that can be done after building a temporary new branch, and
> doing git merge -s ours. That way the old branch need no rebasing ;)

I'll think about how to best do it.


More information about the openpvrsgx-devgroup mailing list