From: Marko Hoyer <mhoyer.oss-devel@freenet.de>
To: Rob Landley <rob@landley.net>,
Marko Hoyer <mhoyer.oss-devel@freenet.de>,
"Bird, Tim" <Tim.Bird@sony.com>, Shankari <beingcap11@gmail.com>,
"linux-embedded@vger.kernel.org" <linux-embedded@vger.kernel.org>
Subject: Re: [boot-time]
Date: Sat, 11 Jan 2025 09:40:06 +0100 [thread overview]
Message-ID: <1b6e380d-000d-420a-b198-ecb68c356d34@freenet.de> (raw)
In-Reply-To: <c70841da-3fe6-4b58-a24f-579dc3cc5dbc@landley.net>
Am 11.01.25 um 00:15 schrieb Rob Landley:
> On 1/10/25 16:46, Marko Hoyer wrote:
>> So I think it is worth talking a bit about udev and options to deal
>> with it but adapting thinks a bit to todays world. I'm currently
>> registering for the wiki, maybe I can setup an initial page at some
>> time ...
>
> busybox mdev is a lot lighter weight, and can do pretty elaborate things.
>
> https://wiki.alpinelinux.org/wiki/Mdev
>
> https://github.com/fff7d1bc/mdev-like-a-boss
>
> The theory these days is you mount devtmpfs and then use mdev to add
> scriptable behavior to device insertion/removal events via netlink
> notifications.
>
> Rob
Hey Rob,
thx for the hint. Sounds good!
How is the enumeration of cold plugged devices realized in mdev? Is it
similar to udev triggering all devices in the complete device tree?
Marko
next prev parent reply other threads:[~2025-01-11 8:40 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAORPcfVRobA+u5q7aPboC=3iY8dibDUB0920Z=Z0VgpQEupKJw@mail.gmail.com>
2025-01-08 18:33 ` [boot-time] Bird, Tim
2025-01-08 20:39 ` [boot-time] Marko Hoyer
2025-01-08 21:19 ` [boot-time] Bird, Tim
2025-01-08 23:26 ` [boot-time] Rob Landley
2025-01-09 13:02 ` [boot-time] Marko Hoyer
2025-01-09 21:10 ` [boot-time] Rob Landley
2025-01-09 21:35 ` [boot-time] Marko Hoyer
2025-01-09 22:31 ` [boot-time] Rob Landley
2025-01-09 12:43 ` [boot-time] Marko Hoyer
2025-01-09 13:27 ` [boot-time] Geert Uytterhoeven
2025-01-08 23:00 ` [boot-time] Rob Landley
2025-01-09 2:23 ` [boot-time] Bird, Tim
2025-01-10 22:46 ` [boot-time] Marko Hoyer
2025-01-10 23:15 ` [boot-time] Rob Landley
2025-01-11 8:40 ` Marko Hoyer [this message]
2025-01-11 17:56 ` [boot-time] Rob Landley
2025-01-11 18:57 ` [boot-time] Bird, Tim
2025-01-12 1:03 ` [boot-time] Rob Landley
2025-01-12 10:11 ` [boot-time] Marko Hoyer
2025-01-12 13:39 ` [boot-time] Francesco Valla
2025-01-12 18:35 ` [boot-time] Rob Landley
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=1b6e380d-000d-420a-b198-ecb68c356d34@freenet.de \
--to=mhoyer.oss-devel@freenet.de \
--cc=Tim.Bird@sony.com \
--cc=beingcap11@gmail.com \
--cc=linux-embedded@vger.kernel.org \
--cc=rob@landley.net \
/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;
as well as URLs for NNTP newsgroup(s).