On Thu, 06 Apr 2017 20:02:23 -0700 Keith Packard <kei...@keithp.com> wrote:
> Michel Dänzer <mic...@daenzer.net> writes: > > > When no such special client (Steam?) is running, the desktop environment > > will try to use the HMD anyway, right? So the expected use case would be > > for the user to start a special client first and only plug in the HMD > > afterwards? That seems a bit inconvenient. > > I'd love a better alternative, but this is the best I've come up > with. > > Of course, it needn't be the actual VR client, it could be a stub > application that popped open a 'which app would you like to run on the > HMD' chooser of some kind, or even hooks in the desktop system that > managed that. > > Suggestions very much encouraged. Hi, we need some kind of a database to recognize HMDs in any case, right? It would be best if the database was shared, so that everyone could recognize all HMDs, at least as far as one can do that based on EDID. If we had such a database, perhaps interfaced with a library, when how about Xorg using that library to automatically recognize and hide HMDs? That library would of course be also used by all HMD-supporting Wayland servers. If there was such a library, maybe it could also handle EDID parsing once and for all... a libinput for outputs? Btw. I was also told at #openhmd that some HMDs do not appear as connected outputs until you specifically turn it on via USB. So there is going to be a hotplug, and you'd want to avoid sending that to normal X11 clients so that they won't race with the special VR client grabbing it. Thanks, pq
pgp0d8hnkEigz.pgp
Description: OpenPGP digital signature
_______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
