From: Tony Lindgren <tony@atomide.com>
To: "H. Nikolaus Schaller" <hns@goldelico.com>
Cc: "Discussions about the Letux Kernel"
<letux-kernel@openphoenux.org>,
"Merlijn Wajer" <merlijn@wizzup.org>,
"Adam Ford" <aford173@gmail.com>,
"Philipp Rossak" <embed3d@gmail.com>,
"Paweł Chmiel" <pawel.mikolaj.chmiel@gmail.com>,
"Tomi Valkeinen" <tomi.valkeinen@ti.com>,
"Filip Matijević" <filip.matijevic.pz@gmail.com>,
"Ivaylo Dimitrov" <ivo.g.dimitrov.75@gmail.com>,
"moaz korena" <moaz@korena.xyz>,
"James Hilliard" <james.hilliard1@gmail.com>,
maemo-leste@lists.dyne.org,
linux-omap <linux-omap@vger.kernel.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
kernel@pyra-handheld.com,
"Robert Nelson" <robertcnelson@gmail.com>
Subject: Re: [Letux-kernel] Lay common foundation to make PVR/SGX work without hacks on OMAP34xx, OMAP36xx, AM335x and potentially OMAP4, OMAP5
Date: Wed, 16 Oct 2019 16:03:18 -0700 [thread overview]
Message-ID: <20191016230318.GK5610@atomide.com> (raw)
In-Reply-To: <1A69DA38-DD6D-4C2B-9F42-D293796AC98A@goldelico.com>
* H. Nikolaus Schaller <hns@goldelico.com> [191014 09:12]:
>
> > Am 12.10.2019 um 15:09 schrieb H. Nikolaus Schaller <hns@goldelico.com>:
> >
> > Hi,
> >
> >> Am 05.10.2019 um 18:58 schrieb H. Nikolaus Schaller <hns@goldelico.com>:
> >
> > I have found the following description, followed all steps, and it works:
> >
> > http://blog.0xpebbles.org/PowerVR-SGX-on-the-beaglebone-black-in-2019
> >
> > So with this, I have got a working user-space setup for BeagleBone and some working
> > pvrsrvkm.ko module (kernel 4.4.155-ti-r155) for evaluation.
>
> > What I don't have yet is the full source code or build recipe for the specific
> > 4.4.155-ti-r155 pvrsrvkm.ko from TI.
> >
> > But even without having this yet, I can start experiments by replacing
> > kernel and pvrsrvkm.ko with mine. This should allow to gain new insights.
>
> Good news:
>
> after making a Hybrid SD image of the setup described above and replacing the
> 4.4.155-ti-r155 kernel with its pvrsrvkm.ko by my own 5.4-rc2 kernel and pvrsrvkm,
> I was able to start the pvrsrv uKernel. And run the gles1test1 on beaglebone
> (without LCD but also without errors).
>
> With this knowledge I could adapt my user-space. There are indeed different
> non-free binaries for sgx530, sgx540, sgx544. And SGX needs enough coherent memory.
> So I could make a completely self-built kernel and rootfs (using the git clone from
> ti for the firmware + make install) run on BeagleBone.
>
> Here is a quickly taken video:
>
> https://youtu.be/jFCPR_EvtjY
Nice :)
> With the same setup, I can now also load the kernel driver and run pvrsrvctl on
> DM3730 without errors, but the gles1test1 reports some error and fails to run.
> Maybe something in the video subsystem or memory mapping is still wrong.
>
> Unfortunately, the same setup does not run on omap5. It looks like there are different
> releases for the non-free binaries and I have to pick the right one.
>
> On BBB the version I could make running is branch ti-img-sgx/1.14.3699939_k4.4 from
> git://git.ti.com/graphics/omap5-sgx-ddk-um-linux.git. Target ti335x works while
> target jacinto6evm fails for OMAP5. A diff on the binaries for e.g. pvrsrvctl shows
> that they are different.
>
> If you want to repeat this setup and my instructions are too imprecise, please
> ask.
>
> So in summary this means:
> * the common foundation (clock, reset, power etc.) setup is working - thanks to Tero, Tony and others
> * I have added device tree nodes for each SoC type to define sgx registers, interrupts, compatible etc.
> * compiling SoC specific kernel module variants from single source tree works
> * the work can already be demoed on BBB and OMAP5 Pyra (using different user-space binaries)
>
> Basically I am now ready to post an RFC for the sgx child device nodes together
> with a bindings document [1]. But I am not sure if I should better wait until
> really all underlaying prm+rtsctl+syscon+idlest-polling patches by Tero and Tony [2]
> have matured in linux-next and have arrived in v5.5-rc1. Would be short before Xmas.
I think you've already proven that we can have a generic binding for the
sgx using standard properties :) So AFAIK, there's nothing stopping you
from posting the binding and dts changes for review for v5.5.
> Independent of low level patches, we all have to discuss how we want to get the GPLed
> kernel driver [3] into mainline drivers/staging. This likely needs more cleanup before
> it can be proposed.
You probably need a shell script using sed or something to get rid of the
crazy directory path for the kernel driver :) Just make it something like:
drivers/staging/pvr
Then if you have a script doing the directory path conversion, you can
still convert and diff against any other prv branches you may find.
And you can get rid of all the LINUX_VERSION_CODE stuff too for the
mainline kernel.
Regards,
Tony
> [1]: https://github.com/openpvrsgx-devgroup/linux_openpvrsgx/commits/letux/omap-pvr-soc-glue-v5
> [2]: https://github.com/openpvrsgx-devgroup/linux_openpvrsgx/commits/letux/omap-sysc-prm-gfx
> [3]: https://github.com/openpvrsgx-devgroup/linux_openpvrsgx/commits/letux/latest-pvr
>
prev parent reply other threads:[~2019-10-16 23:03 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180108214032.GW3872@atomide.com>
[not found] ` <4d99c1ae-7752-949b-7e88-bc8f1dc594a2@wizzup.org>
[not found] ` <0C51EC59-9CDC-4196-ACF9-24596C9E61B6@goldelico.com>
[not found] ` <FA4520D5-62CB-446D-975C-A1C7B9251517@goldelico.com>
[not found] ` <20190212205132.GO5720@atomide.com>
[not found] ` <0b00ce0a-969f-e638-8247-c2da96cf7ce6@gmail.com>
[not found] ` <20190213004143.GP5720@atomide.com>
[not found] ` <480AB632-A544-41E7-95A4-DC354AEBB71A@goldelico.com>
[not found] ` <CAKpie0SigGGsQxSU+X-Mz5boy-Xx=3wRNOcrf+F=ehFr3RBi7Q@mail.gmail.com>
[not found] ` <092210C3-05DE-4AFB-986F-81BD8F990B67@goldelico.com>
[not found] ` <CAKpie0RXM1UC33YFeFy-kAxfGhYGNkw4vUgNTThf-ZCAhPTVXw@mail.gmail.com>
[not found] ` <BE23C1E4-2877-49FA-B230-F9C10691B805@goldelico.com>
[not found] ` <CAKpie0TSo-8gmDm9_Zw4Sd+kjVVEomp8yA9Vu8qY2U2AcrQc=w@mail.gmail.com>
[not found] ` <8A069D96-C65F-43F5-8F54-20019CFB1A8D@goldelico.com>
[not found] ` <d0cbfaaf-813e-8803-f90b-931a38396750@wizzup.org>
[not found] ` <3A03F F16-C203-43ED-AEEF-0260F6B3331A@goldelico.com>
[not found] ` <3b0a5e78-c4c2-1963-bac7-b49496a1e9b9@wizzup.org>
[not found] ` <1F942AAB-1648-46C0-ADD5-90F6898778BE@goldelico.com>
[not found] ` <84cac9b8-0eff-33f8-464d-4f8045d7db19@wizzup.org>
2019-08-14 8:56 ` Lay common foundation to make PVR/SGX work without hacks on OMAP34xx, OMAP36xx, AM335x and potentially OMAP4, OMAP5 H. Nikolaus Schaller
2019-08-14 9:47 ` Tony Lindgren
2019-08-14 10:33 ` H. Nikolaus Schaller
2019-08-14 13:16 ` Tony Lindgren
2019-08-16 23:01 ` Adam Ford
2019-08-17 7:03 ` Tony Lindgren
2019-08-19 19:25 ` Adam Ford
2019-08-21 11:38 ` Tony Lindgren
2019-08-17 9:01 ` H. Nikolaus Schaller
2019-08-19 19:43 ` Adam Ford
2019-08-20 6:48 ` H. Nikolaus Schaller
2019-08-20 7:09 ` Merlijn Wajer
[not found] ` <C3A56737-6187-4B31-8697-3A02DD164429@goldelico.com>
2019-10-07 15:52 ` Tony Lindgren
2019-10-07 15:56 ` H. Nikolaus Schaller
2019-10-07 19:18 ` Tero Kristo
2019-10-07 19:24 ` H. Nikolaus Schaller
2019-10-08 8:00 ` Tero Kristo
2019-10-08 13:49 ` Tony Lindgren
2019-10-08 20:15 ` H. Nikolaus Schaller
2019-10-09 12:53 ` H. Nikolaus Schaller
2019-10-09 13:55 ` Tero Kristo
2019-10-09 14:23 ` H. Nikolaus Schaller
2019-10-09 16:34 ` Tero Kristo
2019-10-09 19:53 ` H. Nikolaus Schaller
2019-10-12 13:09 ` [Letux-kernel] " H. Nikolaus Schaller
2019-10-14 16:11 ` H. Nikolaus Schaller
2019-10-16 23:03 ` Tony Lindgren [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191016230318.GK5610@atomide.com \
--to=tony@atomide.com \
--cc=aford173@gmail.com \
--cc=embed3d@gmail.com \
--cc=filip.matijevic.pz@gmail.com \
--cc=hns@goldelico.com \
--cc=ivo.g.dimitrov.75@gmail.com \
--cc=james.hilliard1@gmail.com \
--cc=kernel@pyra-handheld.com \
--cc=letux-kernel@openphoenux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=maemo-leste@lists.dyne.org \
--cc=merlijn@wizzup.org \
--cc=moaz@korena.xyz \
--cc=pawel.mikolaj.chmiel@gmail.com \
--cc=robertcnelson@gmail.com \
--cc=tomi.valkeinen@ti.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).