From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eric Anholt Subject: Re: [PATCH] Add second DRI driver name (DRI2DriverVDPAU) Date: Mon, 26 Aug 2013 16:22:49 -0700 Message-ID: <87haecdol2.fsf@eliezer.anholt.net> References: <1376649073.392605286@f12.i.mail.ru> <87y57op4n0.fsf@eliezer.anholt.net> <1377552151.192170899@f62.i.mail.ru> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1706126866==" Return-path: In-Reply-To: <1377552151.192170899@f62.i.mail.ru> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org Errors-To: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org To: Rinat Ibragimov Cc: intel-gfx@lists.freedesktop.org List-Id: intel-gfx@lists.freedesktop.org --===============1706126866== Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Rinat Ibragimov writes: > =D0=9F=D0=BE=D0=BD=D0=B5=D0=B4=D0=B5=D0=BB=D1=8C=D0=BD=D0=B8=D0=BA, 26 = =D0=B0=D0=B2=D0=B3=D1=83=D1=81=D1=82=D0=B0 2013, 13:40 -07:00 =D0=BE=D1=82 = Eric Anholt : >> =D0=98=D0=B1=D1=80=D0=B0=D0=B3=D0=B8=D0=BC=D0=BE=D0=B2 =D0=A0=D0=B8=D0= =BD=D0=B0=D1=82 writes: >>=20 >> > libvdpau uses second DRI driver name to determine which VDPAU driver >> > to use. This patch will allow libvdpau choose libvdpau_i965.so on syst= ems >> > with Intel GPUs, libvdpau_nvidia.so on those with nVidia ones, and so = on. >> > I'm experimenting now with generic vdpau driver using OpenGL/VA-API, >> > it would be convenient to have this driver selection working without m= anual >> > driver selection. >>=20 >> If it's a generic driver, why would it need a "i965" string passed over >> the DRI2 protocol to find it? > > It doesn't actually. It's just to simplify distribution package managemen= t. > If one names driver libvdpau_nvidia.so.1, it will break VDPAU on > nVidia equipped machines. With this patch one can name it > libvdpau_i965.so.1 and driver will be loaded on intel equipped > machines only. > >>=20 >> One of the things I'm planning on doing is removing use of the >> protocol-provided DRI2 driver name from Mesa -- Mesa knows what drivers >> it has built, and it knows how to detect those devices (in the EGL >> code), so why would we pay attention to what the X Server thinks our >> driver's name is? Seems like vdpau could probably do the same. >>=20 > > VDPAU uses entry point library (libvdpau) which loads backend drivers. > libvdpau uses second DRI2 driver name amongst other methods to determine > which driver to load. It can not rely on Mesa's internal knowledge, becau= se > it must work with proprietary nVidia driver too. Right, I meant "couldn't libvdpau have a method to determine which driver to load based on looking at your hardware, like how Mesa's EGL does?", since only libvdpau is likely to know how pieces of hardware map to driver binaries. --=-=-= Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.14 (GNU/Linux) iQIcBAEBCAAGBQJSG+NJAAoJELXWKTbR/J7okGsQALMdlIaxwBQUByT6y+fhyqTK kK9JjN3FP/lTtiesvBEnKSJbyf+erhNwRAUeQXbEFFxH59Bnj/l9euJ6HFUTR9Ne f9stE/FNX7Yx+nq+txtvTfdDRiK21rfG3Xpo7oTnOqhiWB7+6/sicSvhUg/5y1DC PNBS67/x7UJm6ImDf9/DNelTkVAgzKUlKTLrEyx5hKDua7ICun/fKzZxZ4jyE+U7 6dkhunmKNEtuKm6/HBRQkqX9KjSPWR0Ni3t5QEk+mz9eEYeKLRH1+I3ipdfnPh5s WEHeKjr+dfCEgLDW40yIqe9p45nzl0gG7bFMF9OhWFZfE78hqSrCoFe/XFj63ju+ ANmBbcfjVMHo0mApRaZNPoMZJHWQ+Px1I9RJhAAkFnK1w0IHu7uOD0ihHclBtDYe 0ofrjq5XX5Gl2+vrz71H7NMOHhG6bC7aLtXF4OTW8FMw5lfRXUpYUZz0jvaGzZar o5cJs+K+2dVoTXOZmpjzOxkKiD7ouuYEI//5EEnrMBxWKWth/5vpbISiIuCnB5A6 o/riIGs51Y8/FZrtNuJGI2mVre/TdAm97oLWHK/SyD8FaMWixt7r7OPu9QRjLXt8 iuANDDF8+H++6dq7W71GClUz8ed1+Tbe+hl4gkr/Y4/Lg/UwDx5UWYNH1x0hCTdn GsdMLIE9I4sIQZQb3pHu =NIzw -----END PGP SIGNATURE----- --=-=-=-- --===============1706126866== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx --===============1706126866==--