From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] wf111: Add mdev dependency
Date: Wed, 12 Aug 2015 07:38:16 +0300 [thread overview]
Message-ID: <20150812043816.GG25261@tarshish> (raw)
In-Reply-To: <CAE21AQqJwCZMRDj3C+JEHjoNJvprxhZusW6TTfNWVwLaL7UziA@mail.gmail.com>
Hi Charles,
On Wed, Aug 12, 2015 at 08:11:08AM +1200, Charles Manning wrote:
> Are you saying I should explain here or in the commit notice?
In commit log.
> 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.
> The wf111 driver set uses hotpug to perform the firmware patching
> (loading .xbv files).
>
> From what I have experienced, fw patching is required when you first
> fire up a new module and when you change modes (sta only vs ap).
Since there are different ways to load the firmware we generally don't make
firmware or driver packages build depend on any specific firmware loading
mechanism.
baruch
> On Tue, Aug 11, 2015 at 11:40 PM, Baruch Siach <baruch@tkos.co.il> wrote:
> > On Tue, Aug 11, 2015 at 07:17:02PM +1200, Charles Manning wrote:
> >> wf111 really needs mdev
> >
> > Please explain why.
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
next prev parent reply other threads:[~2015-08-12 4:38 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 [this message]
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
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=20150812043816.GG25261@tarshish \
--to=baruch@tkos.co.il \
--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