[Openpvrsgx-devgroup] openpvrsgx-devgroup Digest, Vol 11, Issue 6

H. Nikolaus Schaller hns at goldelico.com
Thu Oct 15 16:01:06 CEST 2020


Hi Alif,

> Am 14.10.2020 um 17:54 schrieb Alif Ilhan <alifilhan0 at gmail.com>:
> 
> One more question. Which branch to use? I see there are branches like letux-pvrsrvkm-59-rc2 etc. I am currently trying with letux-pvrsrvkm (default). Did I choose the correct branch? I see more fresh activities in letux-pvrsrvkm-5.9-rc2

yes, the letux-pvrsrvkm branch is a little outdated (seems to be v5.6).

letux-pvrsrvkm-5.9-rc2 is the latest one.

Unfortunately this is a little confusing. The reason is that there are several
feature branches which are merged into a single "complete" kernel. These
feature-branches are rebased every now and then, so that we can remove patches
which have arrived upstream or can follow API changes.

For the Letux project this is done almost automatically every week so there
would be a letux-pvrsrvkm-5.9.0.

But this way of rapid rebase+merge gave a non-linear history between e.g.
letux-pvrsrvkm-5.9-rc1 and letux-pvrsrvkm-5.9-rc2. This makes detection of
changes and bisects too difficult.

So the current work-around is to rebase only once every major release. This
will be letux-pvrsrvkm-5.10-rc1 or letux-pvrsrvkm-5.10-rc2 in ca. 2-3 weeks.

Until then please try letux-pvrsrvkm-5.9-rc2 which should also be the (current)
basis if you want to submit patches and fixes to this list.

If you need some bug fixes from upstream kernel (it is still a -rc) and try
with latest linus/master, please do:

	git checkout letux-pvrsrvkm-5.9-rc2
	git merge v5.9

If you fix something, please commit on top of this and do a git-format for
your patches. I can then integrate them into the tree for everyones benefit.

BR and thanks,
Nikolaus


> 
> On Wed, 14 Oct 2020, 4:00 p.m. , <openpvrsgx-devgroup-request at letux.org> wrote:
> Send openpvrsgx-devgroup mailing list submissions to
>         openpvrsgx-devgroup at letux.org
> 
> To subscribe or unsubscribe via the World Wide Web, visit
>         http://lists.goldelico.com/mailman/listinfo.cgi/openpvrsgx-devgroup
> or, via email, send a message with subject or body 'help' to
>         openpvrsgx-devgroup-request at letux.org
> 
> You can reach the person managing the list at
>         openpvrsgx-devgroup-owner at letux.org
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of openpvrsgx-devgroup digest..."
> 
> 
> Today's Topics:
> 
>    1. About PowerVR DDKs (Alif Ilhan)
>    2. Re: About PowerVR DDKs (H. Nikolaus Schaller)
> 
> 
> ----------------------------------------------------------------------
> 
> Message: 1
> Date: Tue, 13 Oct 2020 22:17:58 +0600
> From: Alif Ilhan <alifilhan0 at gmail.com>
> To: openpvrsgx-devgroup at letux.org
> Subject: [Openpvrsgx-devgroup] About PowerVR DDKs
> Message-ID:
>         <CAPfpOrZuci7T6S4VU4x8aE0uOJgfWXTisizsKp3fVF2UkmvQGA at mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
> 
> I want to build this kernel with the PVR module for Intel Atom N2600. But
> which DDK should I select? There are a lot of options like Ti, SUN4i,
> Ingenic Generic. But which is appropiate for the SGX545?
> 
> Thanks,
> Alif
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://lists.goldelico.com/pipermail/openpvrsgx-devgroup/attachments/20201013/23a1c079/attachment.html>
> 
> ------------------------------
> 
> Message: 2
> Date: Tue, 13 Oct 2020 18:38:40 +0200
> From: "H. Nikolaus Schaller" <hns at goldelico.com>
> To: OpenPVRSGX Linux Driver Group <openpvrsgx-devgroup at letux.org>
> Subject: Re: [Openpvrsgx-devgroup] About PowerVR DDKs
> Message-ID: <E7A06234-D3B7-44A6-9839-4DBF27511AB5 at goldelico.com>
> Content-Type: text/plain; charset=us-ascii
> 
> Hi Alif,
> 
> > Am 13.10.2020 um 18:17 schrieb Alif Ilhan <alifilhan0 at gmail.com>:
> > 
> > I want to build this kernel with the PVR module for Intel Atom N2600. But which DDK should I select? There are a lot of options like Ti, SUN4i, Ingenic Generic. But which is appropiate for the SGX545?
> 
> That is a good question :)
> 
> Well, there is no specific option for SGX545 but for different SoC.
> The idea is to make a generic driver handle all SGX5 variants without configuration (only through device tree which describes the hardware).
> 
> Here is my .config for some OMAP processor:
> 
> iMac:master hns$ fgrep SGX .config
> CONFIG_SGX=y
> # CONFIG_PVRSGX_1_9_2188537 is not set
> # CONFIG_PVRSGX_1_9_2253347 is not set
> # CONFIG_PVRSGX_1_10_2359475 is not set
> # CONFIG_PVRSGX_1_13_3341330 is not set
> # CONFIG_PVRSGX_1_14_3699939 is not set
> # CONFIG_PVRSGX_1_14_3759903 is not set
> # CONFIG_PVRSGX_1_14_3841212 is not set
> # CONFIG_PVRSGX_1_15_4564147 is not set
> CONFIG_PVRSGX_1_17_4948957=y
> # CONFIG_SGX_DEBUG is not set
> CONFIG_SGX_DRM=y
> CONFIG_SGX_OMAP=m
> # CONFIG_SGX_GENERIC is not set
> iMac:master hns$ 
> 
> I think your setup should have a CONFIG_SGX_CEDARVIEW for Intel.
> It should become visible if your setup has CONFIG_MATOM=y and CONFIG_SGX=y.
> I hope it has. If not, we have a bug with Makefile and Kconfig.
> 
> Please check with drivers/gpu/drm/pvrsgx/Makefile and Kconfig
> 
> Next is to choose some DDK version.
> 
> iMac:master hns$ find drivers/gpu/drm/pvrsgx/ -name '*cedarview*'
> drivers/gpu/drm/pvrsgx//1.13.3341330/eurasia_km/eurasiacon/build/linux2/pc_i686_cedarview_linux
> drivers/gpu/drm/pvrsgx//1.13.3341330/eurasia_km/services4/system/cedarview_linux
> drivers/gpu/drm/pvrsgx//1.14.3699939/eurasia_km/eurasiacon/build/linux2/pc_i686_cedarview_linux
> drivers/gpu/drm/pvrsgx//1.14.3699939/eurasia_km/services4/system/cedarview_linux
> drivers/gpu/drm/pvrsgx//1.14.3759903/eurasia_km/eurasiacon/build/linux2/pc_i686_cedarview_linux
> drivers/gpu/drm/pvrsgx//1.14.3759903/eurasia_km/services4/system/cedarview_linux
> drivers/gpu/drm/pvrsgx//1.14.3841212/eurasia_km/services4/system/cedarview_linux
> iMac:master hns$ 
> 
> shows which DDKs should compile. Best is to start with CONFIG_PVRSGX_1_14_3699939.
> 
> This will be the first hurdle to jump over...
> Then we will see what problem surfaces next.
> 
> BR and thanks,
> Nikolaus
> 
> 
> 
> ------------------------------
> 
> Subject: Digest Footer
> 
> _______________________________________________
> https://github.com/openpvrsgx-devgroup/linux_openpvrsgx
> openpvrsgx-devgroup mailing list
> openpvrsgx-devgroup at letux.org
> http://lists.goldelico.com/mailman/listinfo.cgi/openpvrsgx-devgroup
> 
> 
> ------------------------------
> 
> End of openpvrsgx-devgroup Digest, Vol 11, Issue 6
> **************************************************
> _______________________________________________
> https://github.com/openpvrsgx-devgroup/linux_openpvrsgx
> openpvrsgx-devgroup mailing list
> openpvrsgx-devgroup at letux.org
> https://lists.goldelico.com/mailman/listinfo.cgi/openpvrsgx-devgroup



More information about the openpvrsgx-devgroup mailing list