Date: Tue, 17 Sep 2013 09:29:47 +0200 From: Matthieu Volat <mazhe@alkumuna.eu> To: ports@freebsd.org, x11@freebsd.org Subject: Re: [CFT] Update of xorg libraries and MESA Message-ID: <3DE81815-D203-44BF-A1C0-BF9921EF57BC@alkumuna.eu> In-Reply-To: <5236F136.5030905@gmail.com> References: <522DC3EB.4060607@freebsd.org> <522DE093.9080504@freebsd.org> <5236C259.3020100@gmail.com> <20130916090354.GW33103@ithaqua.etoilebsd.net> <5236F136.5030905@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] Le 16 sept. 2013 à 13:53, Vitaly Magerya <vmagerya@gmail.com> a écrit : > Baptiste Daroussin wrote: >>> 1) 'usb_id' is always NULL, so 'MatchUSBID' directive in xorg.conf won't >>> work; >>> >>> 2) 'vendor' and 'product' will be determined from 'dev.x.x.%desc' sysctl >>> by splitting on the first space, so for example my USB tablet, which has >>> %desc equal to "WALTOP International Corp. Slim Tablet" will have vendor >>> "WALTOP" and product "International Corp. Slim Tablet" -- so those are >>> the strings I should use in 'MatchVendor' and 'MatchProduct'; >>> >>> 3) if 'devd' is restarted while Xorg is running, further hardware >>> changes will not be reported to Xorg. >>> >>> Can you confirm I'm reading this right? If so, are there any plans to >>> improving these points? >> >> Yes you are totally right about all this points this should be fixed. >> >> I have no time to work on this right now. Anyone volunteering? > > I am, once my flu is gone. > > I'm actually using a devd backend I wrote a few months ago > (which avoids the mentioned issues), but it's rather different > from yours (more intrusive that is): directives are added to > devd config to call a script when devices appropriate for Xorg > are added or removed. That script will maintain a file with the > list of those devices; it will also print add/remove messages > into a special pipe, if it exists. Xorg will read the file with > the list on startup, and will create and listen to the pipe to > see added/removed devices. This way devd restarts are safely > handled, and the script called from devd can invoke 'usbconfig' > to correctly determine vendor name, product name and usb id. > > The open problems here are: > 1) what should happen if multiple X instances are running? > 2) how to clean the file with the list of devices on boot? > > If you're OK with this approach in general, I can clean up my > code, update it and submit a patch. > _______________________________________________ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" Just as a side note : I tested the devd backend and mouse & keyboard were detected. But what would be the best way to set the keyboard layout now? Thanks for the work, it is awesome to see we'll survive HAL deprecation :) -- Mazhe [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Comment: GPGTools - http://gpgtools.org iEYEARECAAYFAlI4BPIACgkQ+ENDeYKZi36cpQCZAcw2NNhuRLjmCJWMOyoZYT7b fkUAnjdwyAPvXPXGS9UNPfE79ujs515m =uP1J -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3DE81815-D203-44BF-A1C0-BF9921EF57BC>