Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Floris Bos <bos@je-eigen-domein.nl>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] wf111: Add mdev dependency
Date: Thu, 13 Aug 2015 00:54:00 +0200	[thread overview]
Message-ID: <55CBCE88.1000703@je-eigen-domein.nl> (raw)
In-Reply-To: <CAE21AQr13hYAsTkcD2_qRjSHme8aCHPDZDt2CWMeo8Fi4jptHw@mail.gmail.com>

On 08/12/2015 07:16 AM, Charles Manning wrote:
>>> Actually udev would work too.
>> Recent kernels gained the ability to load firmware directly without any help
>> form userspace, so this is probably another option.
> Well not without rewriting the wf111 driver and the associated
> prebuilt "helper" binaries it comes with...

mdev will not launch any of those "prebuild helper binaries" 
automatically, unless you added any explicit rules to tell it to in 
mdev.conf
If you could make it work by just enabling mdev, it is more likely mdev 
only helped by serving files from /lib/firmware to the module, which -as 
mentioned- is not strictly necessary in recent kernels.


Yours sincerely,

Floris Bos

  parent reply	other threads:[~2015-08-12 22:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-11  7:17 [Buildroot] [PATCH] wf111: Add mdev dependency Charles Manning
2015-08-11 11:40 ` Baruch Siach
2015-08-11 20:11   ` Charles Manning
2015-08-12  4:38     ` Baruch Siach
2015-08-12  5:16       ` Charles Manning
2015-08-12  5:38         ` Baruch Siach
2015-08-12  5:56           ` Charles Manning
2015-08-12 22:54         ` Floris Bos [this message]
2015-08-12 10:29 ` Floris Bos
2015-08-12 20:49   ` Charles Manning
2015-08-12 21:47     ` Floris Bos
2015-08-18 20:28     ` Thomas Petazzoni

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=55CBCE88.1000703@je-eigen-domein.nl \
    --to=bos@je-eigen-domein.nl \
    --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