From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keith Packard Subject: Re: Proposal for RandR version 1.6, Leases and EDID-based output grabs Date: Sun, 09 Apr 2017 10:27:31 -0700 Message-ID: <86lgr9xzi4.fsf@hiro.keithp.com> References: <86fuhrka4t.fsf@hiro.keithp.com> <4caa78af-7dc8-fbcf-d2ca-285d4554f5c9@daenzer.net> <86zifsyl6o.fsf@hiro.keithp.com> <20170407105618.200ad289@eldfell> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0992252336==" Return-path: In-Reply-To: <20170407105618.200ad289@eldfell> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: Pekka Paalanen Cc: xorg-devel@lists.freedesktop.org, Michel =?utf-8?Q?D=C3=A4nzer?= , dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============0992252336== Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" --=-=-= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Pekka Paalanen writes: > 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. Yeah, I think you've got some good ideas here. Here are some questions which this raises: * What should we do with an HMD which is in the database but for which no application is installed on the host? * Entries in the database should probably have names an versions, so that clients could have some way to identify whether they support what has been connected. Would providing the manufacturer ID and product codes be sufficient here? * Should the database be visible and managed over X? Or should it be hidden from clients and only visible to the X server? * We want to generate events when the HMD is plugged in; how should clients select for these? > 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. I'm not sure a library is necessary, if the database was a directory full of files. > If there was such a library, maybe it could also handle EDID parsing > once and for all... a libinput for outputs? Yeah, not a terrible idea, but possibly more yak shaving than we really need to get into here. > 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. It'd still get 'hot plugged' in the X server when enabled over USB, so we'll want to hide that from regular clients in some way. =2D-=20 =2Dkeith --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEw4O3eCVWE9/bQJ2R2yIaaQAAABEFAljqbwMACgkQ2yIaaQAA ABEJ5g/+PckAtvlHS0sFKMC57YigsOv40E5MSKuEqMORdH4Si3p6guGkQY0uNTSd 8Yexl/EPItO97AsAynZyHZVdEK41XdMscIQIVEUnRbWLw81Wy3kdaKsFUT7capre hqFFKkhT66Eq+mjn+jksGQ/qd1PD49sUTGRvR2kN3d9T5COQvfY8razHnffBxlOF u323Dx+8NE9po5+2chEyhKbHSjqNbpZnlHPAwozPvfGzYmVeRni8NBYzq4ost+8l qoyzGW5/57HBD+kUK5MOfe68veHax1h0Memgymm5qZJwQwTvziTUJzVpEGhst5Wc 7a3PTIOtZVD+AYv0betemCvGGDvgH908yTrhsIeniakr+iYZ3b35Li26/A+MvcAy 5ycKsPNfXKkEAuGUQEqX8WTDB+19AqmUwFt4NvguydTbexWuJvGLfGTe2CwIdLri Tg/x6YtZHY1LzLZGa7YErU6v1vHaUhJCSCTksVFci7hl4hpx6sbgVhefL+va2gZD +z4wHW8l5Ohg48VM12jbQNL+xBaQO+GjQby8rllgc6ikaq0McEDVpSBounc3EYTk qMIlNT7zUwNDtnL6RLcp6wAfKIIhA4X4tFMQ92UdW9JmBLlM6xYxqnb/17Zz6PH+ IEEVexYZrYWPACnhiv4VrBdTRud6eJuW412yNHmsM7aT8JJ0qVE= =sohs -----END PGP SIGNATURE----- --=-=-=-- --===============0992252336== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg== --===============0992252336==--