Re: What is evdev and autoloading?

On 02/18/19 10:50, Rodney W. Grimes wrote:
>> On Mon, Feb 18, 2019 at 9:12 AM Rodney W. Grimes <
>> freebsd-rwg_at_pdx.rh.cn85.dnsmgr.net> wrote:
>>
>>>> On Mon, Feb 18, 2019 at 07:12:24AM -0800, Rodney W. Grimes wrote:
>>>>>> On 2/18/19 12:06 PM, Stefan Blachmann wrote:
>>>>>>> On 2/18/19, Vladimir Kondratyev <vladimir_at_kondratyev.su> wrote:
>>>>>>>> On 2019-02-17 21:03, Steve Kargl wrote:
>>>>>>>>> Anyone have insight into what evdev is?
>>>>>>>> evdev.ko is a small in-kernel library that makes all your input
>>> events
>>>>>>>> like keyboard presses libinput-compatible.


That's... wrong.

evdev has nothing to do with libinput.  Rather, it can be used by
libinput, but I never once used libinput on FreeBSD/X11.  I used
xf86-input-evdev.

evdev is a generic event device subsystem originated in the Linux kernel.


> But it DOES work, I am pretty sure we have 1000's of users on that 5 year
> old hardware that are totally happy with the intree DRM2 that is in stable/12,
> and some of whom have ventured into head/13 are having issues with the
> "new" model (ie kmod broken by a base commit).
> 
> I think one serious problem here is the summary dismissal of things
> simply on the "5 year old" basis.  Not everyone, and infact few now
> a days other than corporate buyers, can afford new hardware, 
> giving the minimal performance increase in systems over the last 5
> years the cost/benifit factor of a new computer is just too low.


That's the primary reason I don't focus on FreeBSD any more, and the
primary reason when I have sudden time crunches, FreeBSD stuff is the
first to go out the window.

It's not that I don't like FreeBSD any more, it's that it just doesn't
fit in with my ideas on how a system project should be run, or how it
should prioritise.  And that isn't really a comment on FreeBSD, nor me,
it's just a statement.  Everyone's different.

Perhaps all the people who are upset at FreeBSD becoming the next OS X
(you must have hardware *this* *new* to run!) should start putting more
effort in to keeping the old hardware alive and working in the processes
defined by FreeBSD.  Make proposals, participate and communicate on MLs
(instead of just complain), etc.

This is all just observations I've made over the last few months of
reading -current and not really contributing much.  Apologies if I'm off
the mark on any of this.

Best to you and yours,
--arw

-- 
A. Wilcox (awilfox)
Open-source programmer (C, C++, Python)
https://code.foxkit.us/u/awilfox/