Date: Wed, 16 Sep 2020 11:22:01 +0200 From: Niclas Zeising <zeising@freebsd.org> To: Grzegorz Junka <list1@gjunka.com>, freebsd-x11@freebsd.org Subject: Re: Is there any performance difference between udev and evdev in xorg? Message-ID: <67ec5f69-218a-e271-6094-6d82d975f9e9@freebsd.org> In-Reply-To: <7c43526f-c88f-c893-9285-8e2cbf1ead17@gjunka.com> References: <CAGBxaX=LvdPgR3sm%2BWL-QXn0%2BQoy1%2BzpvxRgf_1v7Oq4qyNmgA@mail.gmail.com> <20200916040110.GA46039@FreeBSD.org> <9fcf11e9-6466-3660-5322-997ed8cb3ca7@freebsd.org> <20200916073731.GA45977@FreeBSD.org> <7c43526f-c88f-c893-9285-8e2cbf1ead17@gjunka.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2020-09-16 10:07, Grzegorz Junka wrote:
>=20
> On 16/09/2020 07:37, Alexey Dokuchaev wrote:
>> On Wed, Sep 16, 2020 at 08:41:28AM +0200, Niclas Zeising wrote:
>>> On 2020-09-16 06:01, Alexey Dokuchaev wrote:
>>>> On Tue, Sep 15, 2020 at 10:55:31PM -0400, Aryeh Friedman wrote:
>>>>> What if any is the performance difference between udev and evdev wh=
en
>>>>> configuring xorg?=C2=A0 Also do I need to use one or the other cons=
istently
>>>>> or can I intermix them?
>>>> If you don't need them (e.g. because this is desktop system without
>>>> fancy input devices), you'd better off with disabling both of them
>>>> altogether and use good old traditional way, that is, simply install
>>>> xf86-input-{keyboard,mouse} and let X.org handle those peripherals.
>>>>
>>>> Yes, you would still be able to plug and unplug your USB mice and
>>>> they will be detected and working as expected.
>>>>
>>>> TL;DR: DEVD/UDEV support is overrated and usually not needed at all.
>>> This is bad advice.
>> OK, let's see why is it bad. :-)
>>
>>> The DEVD support in xorg-server might go away, since it is a FreeBSD
>>> only solution and the udev/evdev is similar to what is used on Linux.
>> Does this imply that DEVD support in X.org is technically inferior to
>> udev/evdev, or it might get deprecated just because they prefer Linux
>> way, regardless of the actual design and implementation quality?=C2=A0=
Kind
>> of tangentially related question, but this might help to foresee what
>> to expect from future X.org development.
>>
>=20
> Linux way doesn't mean it's a bad way. As a user I don't really care if=
=20
> it's Linux way or not as long as it supports the hardware that I spent=20
> my money on.
>=20
> As a developer I do care about a solution that is simpler to code and=20
> use, but not if it's Linux or not. Can you actually define what you mea=
n=20
> by Linux way?
>=20
> However, the most important thing that I care about is that the code I=20
> am learning and using is copyfree. If someone was kind enough to rewrit=
e=20
> the whole Linux using a FreeBSD license then I wouldn't mind switching=20
> to do that to make a better use of the hardware that I have.
In this case, it is copyfree. We have a udev/evdev compat layer in the=20
FreeBSD kernel that is BSD licensed, since it was developed on and for=20
FreeBSD. For the rest of the stack, which means libinput and the device=20
handling in X and wayland, it is MIT licensed, since upstream code=20
generally is MIT licensed.
Regards
--=20
Niclas Zeising
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?67ec5f69-218a-e271-6094-6d82d975f9e9>