If gfxstream is the android pipe based transport I think it's a legacy from before the switch to pure VirtIO for the new Cuttlefish models.
On Mon, 13 Mar 2023, 13:27 Dmitry Osipenko, <dmitry.osipe...@collabora.com> wrote: > On 3/13/23 15:58, Marc-André Lureau wrote: > ... > >> 2) Additional context type: gfxstream [i]? > >> > >> One of the major motivations for adding context types in the > >> virtio-gpu spec was supporting gfxstream. gfxstream is used in the > >> Android Studio emulator (a variant of QEMU) [ii], among other places. > >> That would move the Android emulator closer to the goal of using > >> upstream QEMU for everything. > > > > What is the advantage of using gfxstream over virgl? or zink+venus? > > > > Only AOSP can run with virgl perhaps? I am not familiar with Android > > development.. I guess it doesn't make use of Mesa, and thus no virgl > > at all? > > +1 I'm also very interested in getting an overview of gfxstream > advantages over virgl and why Android emulator can't move to use > virgl+venus (shouldn't it just work out-of-the-box already?). Thanks! > > -- > Best regards, > Dmitry > >
