From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] Towards 2015.05-rc1
Date: Tue, 21 Apr 2015 00:04:53 +0200 [thread overview]
Message-ID: <87sibutq0q.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20150419230245.64cf1410@free-electrons.com> (Thomas Petazzoni's message of "Sun, 19 Apr 2015 23:02:45 +0200")
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
> 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.
Yes, sorry - I haven't forgotten about it, but I haven't been able to
find time for it yet. Realisticly seen, I probably won't be able to make
it within the next 10 days.
> 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.
I agree that it is a tradeoff. In the worst case it can be handled in a
post-build script.
My own usecase was to use libinput for some keyboard/mouse/touchscreen
handling on a small system and disliking the udevd dependency.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2015-04-20 22:04 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 [this message]
2015-04-22 21:47 ` Bernd Kuhls
2015-04-22 22:18 ` Arnout Vandecappelle
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=87sibutq0q.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--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