From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] busybox: register mdev as hotplug helper
Date: Sun, 28 Jul 2013 11:01:29 -0300 [thread overview]
Message-ID: <51F52439.4060001@zacarias.com.ar> (raw)
In-Reply-To: <20130728155156.1bc37ffd@skate>
On 07/28/2013 10:51 AM, Thomas Petazzoni wrote:
>> For mdev that can be solved, at worst it'll be an (almost) no-op,
>> devtmpfs is another story.
>
> That's true.
It basically boils down to helping people or not on alternate scenarios.
Some random guy in #pandaboard was having issues loading firmware on a
prebuilt kernel (which sometimes happens to be a sore PITA to build a
working kernel with some vendors/for some people, no point in arguing
that no matter how much we wish everything were upstreamed/vanilla) for
WiFi support and (obviously) mdev wasn't working.
Solution was get your kernel source/config right, or fix the script.
The script was a quick way out without bad side effects.
On a personal level i don't care about the patch, it was just a quick
and painless way of fixing a common problem.
Regards.
next prev parent reply other threads:[~2013-07-28 14:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-11 20:30 [Buildroot] [PATCH] busybox: register mdev as hotplug helper Gustavo Zacarias
2013-07-12 7:01 ` Thomas De Schampheleire
2013-07-12 10:27 ` Gustavo Zacarias
2013-07-28 8:33 ` Thomas De Schampheleire
2013-07-28 11:28 ` Gustavo Zacarias
2013-07-28 11:56 ` Thomas De Schampheleire
2013-07-28 11:57 ` Gustavo Zacarias
2013-07-28 12:09 ` Thomas De Schampheleire
2013-07-28 12:12 ` Gustavo Zacarias
2013-07-28 13:14 ` Thomas Petazzoni
2013-07-28 13:38 ` Gustavo Zacarias
2013-07-28 13:51 ` Thomas Petazzoni
2013-07-28 14:01 ` Gustavo Zacarias [this message]
2013-07-28 14:03 ` Thomas Petazzoni
2013-07-28 14:12 ` Gustavo Zacarias
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=51F52439.4060001@zacarias.com.ar \
--to=gustavo@zacarias.com.ar \
--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