From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] wf111: Add mdev dependency
Date: Tue, 18 Aug 2015 22:28:51 +0200 [thread overview]
Message-ID: <20150818222851.64d36ea6@free-electrons.com> (raw)
In-Reply-To: <CAE21AQqpiDz0BEA4ruKVGA28k8b4+-NWAkCjKUqX+b=Qta1yrA@mail.gmail.com>
Dear Charles Manning,
On Thu, 13 Aug 2015 08:49:26 +1200, Charles Manning wrote:
> It seems the only way forward here is one of:
> * Convince Bluegiga to change their architecture/drivers to not use
> mdev/udev and release a new tarball.
> * Fix mdev so it works properly.
> * Run mdev in a way that just does the fw loading requests and not
> anything else.
* Use udev
* Use the in-kernel firmware loader
There is currently no way in Buildroot to say "this package requires a
firmware loading capability". And actually implementing that is not so
easy since the in-kernel firmware loader is only available since (say)
3.7, and Buildroot does not know at configure time the kernel version
you're using, nor whether the in-kernel firmware loader is enabled or
not.
So I believe the right thing to do here is simply to update the wf111
Config.in help text to indicate that this package requires a firmware
loading mechanism to be enabled.
My colleague Antoine T?nart (who wrote the package) is successfully
using wf111, probably with udev (I haven't checked). I've Cc'ed Antoine.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2015-08-18 20:28 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
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 [this message]
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=20150818222851.64d36ea6@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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