Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

[Feature Request / Question] Feasibility of OpenGL ES 3.2 emulation in gfxstream (especially on ARM Mali hosts)

Aperta
  • Qualcosa non va?
#202 3 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 2 giorni

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
25/100
Tipo di issue
Funzionalità
Chiarezza
Da chiarire
Stato di attività
Attiva
Stack tecnologico
android, cpp, linux
Ambito
backend

Direzione di ricerca

The issue asks about GLES 3.2 support, gfxstream's roadmap, and ARM Mali passthrough, but names no source files or tests. Start by reading the gfxstream documentation and locating its GLES emulation and translation entry points; determine what support is missing before estimating the work. Done would require an agreed implementation scope and GLES 3.2 support validated in the Android VM environment described.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Summary

Currently, gfxstream's GLES emulation supports up to OpenGL ES 3.1. We are evaluating/using gfxstream in an Android virtual machine environment (Automotive/IVI scenario) and would like to inquire about the roadmap and feasibility of adding OpenGL ES 3.2 emulation support.

Motivation & Background

Several modern Android workloads and benchmarks (e.g., AnTuTu Car/Auto Edition, modern 3D titles) require OpenGL ES 3.2.

While we can enable GLES 3.2 in the Android guest by routing GLES through ANGLE (GLES over Vulkan), this introduces severe performance degradation for OpenGL ES workloads. For example, in our Android VM running AnTuTu Car Edition, the GPU benchmark score drops drastically when using ANGLE compared to native/emulated GLES paths. Therefore, direct GLES 3.2 emulation/passthrough in gfxstream is critical for performance-sensitive use cases.

Questions & Discussion

  1. Feasibility / Roadmap for GLES 3.2:
    Is GLES 3.2 emulation currently on the gfxstream roadmap? What are the primary technical hurdles or missing components (e.g., guest encoder/decoder updates, glestranslator, shader extensions/ASTC/tessellation support)?

  2. ARM Mali Host Environment (GLES-to-GLES passthrough):
    In our deployment, the host GPU is an ARM Mali GPU that already provides native support for OpenGL ES 3.2. Does having a native GLES 3.2 host driver simplify the implementation (e.g., leveraging GLES-on-GLES passthrough without desktop GL translation complexities)?

  3. Experimental Patches / Testing:
    Are there any existing experimental branches, WIP PRs, or patches adding GLES 3.2 support? We would be very glad to test any preliminary patches on our ARM Mali hardware and provide benchmark results, logs, and feedback.

Environment Details
  • Host Platform: ARM64 Linux (Host GPU: ARM Mali A78x)
  • Guest: Android VM (Automotive / IVI)
  • gfxstream Source: main branch
Lingua principale
C++
Stelle
60
Fork
41
Merge medio
1g 2h
PR unite (30g)
9

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di google/gfxstream

Tutte le issue di google/gfxstream

Issue simili

Altre issue su C++

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.