From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Towards 2015.05-rc1
Date: Thu, 23 Apr 2015 00:18:15 +0200 [thread overview]
Message-ID: <55381E27.4020502@mind.be> (raw)
In-Reply-To: <20150419230245.64cf1410@free-electrons.com>
On 04/19/15 23:02, Thomas Petazzoni wrote:
> Bernd,
>
> On Sun, 19 Apr 2015 22:14:24 +0200, Bernd Kuhls wrote:
>
>> if possible and time allows for all involved persons I would like to see the
>> libudev series stuff in the next buildroot release.
>
> As far as I remember, someone needs to take over this series, no? I
> believe you originally authored it, then Yann took over, then Peter
> proposed to take over but did not resend it as far as I know.
>
> On my side, I am still a bit concerned by the usefulness of this
> series. The use cases you have are anyway running big things (Kodi,
> etc.) so I'm not sure why running udevd or not makes a big difference.
> It does seem a lot of additional complexity for not such a huge
> benefit.
Since udev rules are IMHO a lot more complicated than mdev rules and you
usually don't need that complexity in embedded systems, I think there really is
a case to be made for avoiding full udev. Of course, it's always possible to
remove the udev start script in a post-build script (which effectively makes
udev dead code), but it is definitely nice to know which packages will work
without udev running. So that's what I would like this libudev stuff to do.
For example, I have one system that used to be based on mdev. Now we have to
add modem-manager to it, and modem-manager depends on udev. So I've enabled
udev, but now I have to replace the mdev rules with udev rules and I probably
also have to get rid of some of the default udev rules which are not appropriate.
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2015-04-22 22:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-19 20:00 [Buildroot] Towards 2015.05-rc1 Thomas Petazzoni
2015-04-19 20:14 ` Bernd Kuhls
2015-04-19 21:02 ` Thomas Petazzoni
2015-04-20 22:04 ` Peter Korsgaard
2015-04-22 21:47 ` Bernd Kuhls
2015-04-22 22:18 ` Arnout Vandecappelle [this message]
2015-04-22 23:09 ` Gustavo Zacarias
2015-04-20 20:31 ` Arnout Vandecappelle
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=55381E27.4020502@mind.be \
--to=arnout@mind.be \
--cc=buildroot@busybox.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