From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keith Packard Subject: Re: [PATCH] Don't use libudev for glx/dri3 Date: Mon, 18 Nov 2013 22:46:55 -0800 Message-ID: <868uwk3n34.fsf@miki.keithp.com> References: <1384736112-6023-1-git-send-email-keithp@keithp.com> <1384736916-25285-1-git-send-email-keithp@keithp.com> <528A7F6B.3020905@gmail.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============2070406173==" Return-path: In-Reply-To: <528A7F6B.3020905@gmail.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: mesa-dev-bounces@lists.freedesktop.org Errors-To: mesa-dev-bounces@lists.freedesktop.org To: mesa-dev@lists.freedesktop.org Cc: emil.l.velikov@gmail.com, dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============2070406173== Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" --=-=-= Content-Transfer-Encoding: quoted-printable Emil Velikov writes: > On 18/11/13 01:08, Keith Packard wrote: >> libudev doesn't have a stable API/ABI, and if the application wants to u= se one >> version, we'd best not load another into libGL. >>=20 >> Signed-off-by: Keith Packard >> --- >>=20 > Hi Keith, > > Did you had the chance to look at src/gallium/targets/egl-static/egl.c? > It has a different implementation of drm_fd_get_pci_id, whenever udev is > not available. Yeah, it's ugly in a different way from the udev technique... > AFAICS it goes back to the kernel via the relevant ioctl to retrieve the > deviceid/chipid. Currently all but nouveau provide such information. I'm > thinking that this approach might be more reasonable for those concerned > with portability of the udev bits (think on *BSD). I'd encourage some kind of standard IOCTL from DRM that returns the PCI-ID of the underlying device, rather than relying on the level of kludge present in either the udev (or my fake udev) method or the non-udev path in the egl code... > I'm not nitpicking, just thought you might find this interesting. Definitely interesting; it's almost what we want -- the kernel knows the information, there just isn't a clean way of getting it (and no way at all for some devices). =2D-=20 keith.packard@intel.com --=-=-= Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.15 (GNU/Linux) iQIVAwUBUosJYNsiGmkAAAARAQg2pxAAkmLwD3VloKD3e0I6LLcSbhEIfQaAH7ld PyeFaIdGtXG9yzt+sOsoCjIUbxIsJ/Fro+Ay1N57gYRF3+3gUQHUv0u3Vw4Ycoek He+/pgxOYijBTXCfWS8o4tFw9NLJvxs8qzfsWzpSajJAERy4eK0NFLNdesi1xd9z 6MNCWk9A4CC4FbsaGA7WZJabBY+Or95Dnr311mJ7RDbMODn2eTfNv91UXlaSYZCw GXmKPpB64XA8yUYLZL7HIsgpeTvNuo5XXy8iCnJrdBrj8E3IPeUqzWQmtiKsJhw8 Zq3u9eXadE87HW8NKY9BGC4HjQTZNEEqwA3hJXpyaMnSQY/GfnTst6Yh5CkFdPVq F8/lYDA6vqfKRqifMM6Fq1zyN/vbRo75qXhCjg8TFAkcOdMj1xKqBhAM4NVLfHy3 hWdldfHbe0bFTdWM/s2EVE/FrTJazZoRZstH0zLjXo7zcLpeB//bUuhvGZe6nyMq 0lIzqATQoCQdSVVvnuV0v5/OCTBO09f93COC5z4nzj5om5nfJ7vQTymNS6G7MaLu 2IBFlmD2vNwc5AfbMfMyixgWlpxx5f7p+jazbqu69fiVGugYtC21szFE9zxj38Rd RJ0HOfd/pgUGCzFvXwtoYrLf/UoelCS7aHPrO5wAbFpvx7OZAakZAMr9ai+QHLff HesDWy7QeC4= =r7I6 -----END PGP SIGNATURE----- --=-=-=-- --===============2070406173== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev --===============2070406173==--