(ADITG/ESB)
> >
> > Tel. +49 5121 49 6921
> > > -Original Message-
> > > From: Peter Hutterer [mailto:peter.hutte...@who-t.net]
> > > Sent: Freitag, 6. April 2018 04:29
> > > To: Friedrich, Eugen (ADITG/ESB)
> > > Cc: Matt Hoosier; Pekka Paal
Hutterer [mailto:peter.hutte...@who-t.net]
> > Sent: Freitag, 6. April 2018 04:29
> > To: Friedrich, Eugen (ADITG/ESB)
> > Cc: Matt Hoosier; Pekka Paalanen; wayland mailing list
> > Subject: Re: [PATCH libinput 0/1] Initialization race against udev
> >
> > On Thu, A
c: Matt Hoosier; Pekka Paalanen; wayland mailing list
> Subject: Re: [PATCH libinput 0/1] Initialization race against udev
>
> On Thu, Apr 05, 2018 at 01:20:51PM +, Friedrich, Eugen (ADITG/ESB) wrote:
> > Hi Peter
> >
> > Best regards
> >
> > Eugen Friedrich
gt; > Tel. +49 5121 49 6921
> >
> > > -Original Message-
> > > From: wayland-devel [mailto:wayland-devel-
> > > boun...@lists.freedesktop.org] On Behalf Of Peter Hutterer
> > > Sent: Donnerstag, 5. April 2018 06:27
> > > To: Matt Hoosier
&
d-devel [mailto:wayland-devel-
> > boun...@lists.freedesktop.org] On Behalf Of Peter Hutterer
> > Sent: Donnerstag, 5. April 2018 06:27
> > To: Matt Hoosier
> > Cc: Pekka Paalanen; wayland mailing list
> > Subject: Re: [PATCH libinput 0/1] Initialization race against udev
> >
om: wayland-devel [mailto:wayland-devel-
> > boun...@lists.freedesktop.org] On Behalf Of Peter Hutterer
> > Sent: Donnerstag, 5. April 2018 06:27
> > To: Matt Hoosier
> > Cc: Pekka Paalanen; wayland mailing list
> > Subject: Re: [PATCH libinput 0/1] Initialization race against udev
&
o: Matt Hoosier
> Cc: Pekka Paalanen; wayland mailing list
> Subject: Re: [PATCH libinput 0/1] Initialization race against udev
>
> On Wed, Apr 04, 2018 at 09:04:32AM -0500, Matt Hoosier wrote:
> > I encounter another "bad" behavior related to multiple firings of the
On Wed, Apr 04, 2018 at 09:04:32AM -0500, Matt Hoosier wrote:
> I encounter another "bad" behavior related to multiple firings of the UDev
> 'add' event for a given input node.
>
> Typically on modest embedded systems, you do not want to run the exhaustive
> 'udevadm trigger' during the main booti
I encounter another "bad" behavior related to multiple firings of the UDev
'add' event for a given input node.
Typically on modest embedded systems, you do not want to run the exhaustive
'udevadm trigger' during the main booting sequence. That causes hundreds or
thousands of UDev nodes to be crawl
