From: karl@aspodata.se
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] X11 without udev/eudev
Date: Mon, 23 Aug 2021 19:01:33 +0200 (CEST) [thread overview]
Message-ID: <20210823170133.CE04D8517F54@turkos.aspodata.se> (raw)
In-Reply-To: <20210823160738.208C58517F54@turkos.aspodata.se>
Karl Hammar:
> Dr. Canek Peláez Valdés:
...
> > My point is that it's not his call; it's the call of the developers of the
> > software that he decided to use.
>
> Poeple write whatever software they want to or are paid to do.
> It is my call if I want to use that software or not.
For what some people want to work on, here is an alternative api:
https://github.com/idunham/libsysdev
And what Anna <cyber@sysrq.in> gratiosly provided:
https://github.com/illiliti/libudev-zero
...
> > There is no bloat; the developers *need* to handle the dynamic hardware
> > case *and* the static hardware case. With udev, they handle both; otherwise
> > there would be two code routes: one for static and another for dynamic
> > hardware.
As an example of that is:
https://gitlab.freedesktop.org/mesa/drm/-/blob/main/xf86drm.c
The changes nessesary for a non-udev solution is smallish,
and it doesn't have to resort to polling as in the udev case.
A gui's need for pop-up windows when new devices are connected
could just as well be handled separate to the system thing of
/dev nodes, permissions and such. You don't need a daemon for
that, it just that the udev people just merged the use cases.
...
> As a side note,
...
As an actual case, this is a prototype for a three way mouse
to be used on ship bridges
http://aspodata.se/git/openhw/boards_arm_aspo/mouse/
Switching a knob, I can send mouse events to three different
computers, say for radar, maps, etc.
It uses microsoft serial mouse protocol.
This possible for low end mcu's since they contain multiple
serial interfaces.
If I had to use usb, well, not even a high end mcu's like
stm32f4 has more than two usb ports.
Regards,
/Karl Hammar
next prev parent reply other threads:[~2021-08-23 17:01 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-21 20:17 [gentoo-user] X11 without udev/eudev karl
2021-08-21 21:02 ` antlists
2021-08-21 22:34 ` karl
2021-08-21 21:05 ` Anna “CyberTailor”
2021-08-22 20:31 ` karl
2021-08-22 21:59 ` Canek Peláez Valdés
2021-08-22 23:18 ` antlists
2021-08-22 23:30 ` Rich Freeman
2021-08-22 23:37 ` Canek Peláez Valdés
2021-08-23 16:07 ` karl
2021-08-23 17:01 ` karl [this message]
2021-08-23 19:51 ` Canek Peláez Valdés
2021-08-23 22:36 ` karl
2021-08-23 16:14 ` Vitor Hugo Nunes dos Santos
2021-08-21 21:51 ` Vitor Hugo Nunes dos Santos
2021-08-21 22:34 ` karl
2021-08-21 22:45 ` Neil Bothwick
2021-08-22 11:01 ` Mart Raudsepp
2021-08-22 20:31 ` karl
2021-08-22 20:31 ` karl
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210823170133.CE04D8517F54@turkos.aspodata.se \
--to=karl@aspodata.se \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox