Date: Mon, 11 Jun 2018 21:29:12 +0300 From: Greg <greg@unrelenting.technology> To: Denis Polygalov <dpolyg@gmail.com> Cc: Jonathan Anderson <jonathan@FreeBSD.org>, Johannes Lundberg <johalun0@gmail.com>, x11@freebsd.org, Niclas Zeising <zeising@freebsd.org> Subject: Re: [CFT] changes and updates to x11 input devices Message-ID: <20180611182855.ddxbxf7nfk7vlyke@unrelenting.technology> In-Reply-To: <5c1632e5-1a7f-eec9-05c0-737e7227d238@gmail.com> References: <dbf6a804-887d-4683-c371-90785b76aa92@freebsd.org> <0dc5db04-736a-9ac9-c515-2b078b1ca74f@nomadlogic.org> <CAECmPwvOV4967Gjk83TftZyWqiskMAk_ww4ot6zueVP10g-ObQ@mail.gmail.com> <2DCAD3A0-1D1A-468B-A881-1DDA25E61A90@FreeBSD.org> <5c1632e5-1a7f-eec9-05c0-737e7227d238@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 06/11, Denis Polygalov wrote: >Enabling EVDEV in GENERIC kernel will also allow to compile weston - >(reference Wayland composer) without re-compiling the kernel. >Unfortunately I can not find link now, but few weeks ago I read >a report stating that using evdev in FreeBSD cause kernel panic >after DIS-connection of some devices.... >I also would like to know - is the evdev is the right way >for FreeBSD or there is (will be) alternative solution? Hi! I think the problem blocking evdev from on-by-default was the keyboard deadlock that could happen when using the debugger: https://reviews.freebsd.org/D15070 And of course evdev is the right way. We even have evdev-only drivers now: wmt(4)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20180611182855.ddxbxf7nfk7vlyke>