On Sun, Sep 7, 2025 at 9:55 AM Vladimir Kondratyev <w...@freebsd.org> wrote:
>
> On 9/7/25 09:41, Oleg Nauman wrote:
> > On Fri, Sep 5, 2025 at 12:08 AM Vladimir Kondratyev <w...@freebsd.org> 
> > wrote:
> >>
> >> The branch main has been updated by wulf:
> >>
> >> URL: 
> >> https://cgit.FreeBSD.org/src/commit/?id=aef807876c305587c60f73e2cd914115d22a53fd
> >>
> >> commit aef807876c305587c60f73e2cd914115d22a53fd
> >> Author:     Vladimir Kondratyev <w...@freebsd.org>
> >> AuthorDate: 2025-09-04 21:07:25 +0000
> >> Commit:     Vladimir Kondratyev <w...@freebsd.org>
> >> CommitDate: 2025-09-04 21:07:25 +0000
> >>
> >>      moused(8): Add support for evdev protocol
> >>
> >>      The new daemon have following properties as compared with previous
> >>      incarnation:
> >>      - evdev protocol support for mices and touchpads. Additionally to
> >>        relative PS/2 and USB devices it enables console support for I2C/USB
> >>        touchpads and bluetooth mices.
> >>      - Other aged protocols like COM, raw PS/2 and X10 are dropped with 
> >> only
> >>        exception of sysmouse. For those who still use them there is an
> >>        utility called msconvd(8).
> >>      - single daemon per system where hotplug is processed via devd socket.
> >>        Per device mode still supported too.
> >>      - Configuration and quirks files in libinput-compatible format.
> >>        Actually, the new moused config parser is taken from libinput.
> >>
> >>      The moused(8) can work in 2 modes:
> >>      1. Evdev support mode. It enables all previously mentioned devices.
> >>         It is enabled by deault.
> >
> >   I think it is require hms driver corresponding entries to be added to
> > /etc/devd/moused.conf otherwise it breaks existing installations and
> > require
> > moused_enable="YES" to be set as workaround of this issue
>
>
> hms is loaded with devmatch entry in devd.conf rather than with moused one.
> moused entries are legacy and disabled by default with
> moused_nondefault_enable="NO" in /etc/defaults/rc.conf
> And moused_enable="YES" is not a workaround. It is how things supposed to be.

 Well, sorry I was not clear so I think it is some misunderstanding
devmatch supposed to load mouse support driver ( hms or ums ) while
devd entry supposed to unattended load moused if device supported by
ums driver was  attached, so moused_enable="YES" was not required

Thank you

>
> --
> WBR
> Vladimir Kondratyev

Reply via email to