Can the pixel C OpenGL be fixed?

[Nintonito]

With the nexus 9,  I know it was impossible due to the lack of any other devices using that K1 variant,  therefore no source or usable code existed to port the GPU drivers over.  But with the Pixel C,  that has changed.  Both the jetson X1 board and the shield Tv exist.  With that in mind,  is porting over the driver stack possible?

[Sonicadvance1]

Not worth it. It supports openGL ES 3.2 and all the extensions Dolphin requires.
The few things it doesn't support under ES you won't even notice the difference.

[Nintonito]

(01-08-2016, 10:35 AM)Sonicadvance1 Wrote: Not worth it. It supports openGL ES 3.2 and all the extensions Dolphin requires.
The few things it doesn't support under ES you won't even notice the difference.

I was actually thinking beyond Dolphin,  as you wouldn't believe what those subtle context differences wreak upon a number of games. Some of them are just hard coded to expect desktop OpenGL when a Tegra processor appears, and when it isn't there the rendering breaks. Many of them won't be patched for these exceptions due to age.  Figured this and xda would be the best places to ask as you guys are on top of these details.

[Sonicadvance1]

Could potentially be done, but there are things that could break it.
Kind of like how the Pixel C uses Nouveau's kernel DRM driver instead of Nvidia's.

[Nintonito]

(01-08-2016, 10:48 AM)Sonicadvance1 Wrote: Could potentially be done, but there are things that could break it.
Kind of like how the Pixel C uses Nouveau's kernel DRM driver instead of Nvidia's.

Is there even a reason for that?  Feels like Google is making changes for the sake of making changes.  Some of them don't even make sense.  They bother to use Tegra chipsets yet do the very best they can to make standard Tegra behaviors and features non existent. I don't understand them.

[Abz145]

(01-08-2016, 10:35 AM)Sonicadvance1 Wrote: Not worth it. It supports openGL ES 3.2 and all the extensions Dolphin requires.
The few things it doesn't support under ES you won't even notice the difference.

How different will Quallcomm's Opengles 3.2 be, compared to nvidias? because ive seen some additional extensions on gfxbench for the nvidia driver. will there be a noticeable difference between the two in dolphin?

[zxcvbad]

@Nintonito, it's quite hard to understand Google, only conclusion that I have it's all about Google's standardization really. It seems they want their devices to be standardized, if Qualcomm based Nexus devices can't have OpenGL 4xx then it means Google's Nvidia tablets won't get it either. At least that's what I thought before Pixel C came out with Nvidia's v355 GLES 3.2 driver. They've kept Nexus 9 on v343 for a very long time even though v349 was available. Now their standardization looks even more odd since N9 is capable of v355 (unlike their Qualcomm devices) but they haven't updated it with v355.

They might be thinking of Pixel C as a different class device, like it's not from the Nexus line, they might be updating N9 later with GLES 3.2 once Qualcomm will release capable drivers, so they could update all the Nexus line, but overall it looks weird