On 23/01/18 19:56, Tony Lindgren wrote:
We really need some coordinated effort to get the driver kernel parts to usable state though. And considering the number of people involved I think staging is the best place to do it. Then what happens after that is of course up in the air as always. In the worst case it will get just dropped lik the TI dsp stuff based on zero effort :)
Yes, I have nothing against the idea. My fear is that it'll be difficult to have a single SGX kernel driver which works for all the SGX userspace binaries. As the kernel and userspace parts are always shipped as a pair, my guess is that there has never been any attempt to keep the UAPI stable. But I'm basing my guess on no actual knowledge, so I'm happy to be proven wrong =).
And there finally seems to some effort going on by the chromeos guys.
FYI again if it was not mentioned earlier, here's the thread for upstreaming Roque support?
"[POC 00/16] Chromebook R13 GPU driver port":
https://lists.freedesktop.org/archives/dri-devel/2017-November/157737.html
No idea how much of that will be usable for SGX though.
If I understood right, it's not about upstreaming. It was about getting the Rogue userspace binaries work on top of mainline, i.e. porting the kernel driver on top of mainline.
And, again, my understanding of the "DRM philosophy" is that having kernel drivers like these is explicitly forbidden in the mainline. Which is why e.g. there's no nvidia kernel driver.
Tomi