From: Luca Ceresoli <luca@lucaceresoli.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] rtl8188eu: new package
Date: Mon, 06 Jul 2015 15:59:51 +0200 [thread overview]
Message-ID: <559A89D7.5010400@lucaceresoli.net> (raw)
In-Reply-To: <20150706151750.456bbb6c@free-electrons.com>
Dear Thomas,
Thomas Petazzoni wrote:
> Luca,
>
> On Mon, 6 Jul 2015 15:09:35 +0200, Luca Ceresoli wrote:
>
>> diff --git a/package/rtl8188eu/Config.in b/package/rtl8188eu/Config.in
>> new file mode 100644
>> index 0000000..3228c67
>> --- /dev/null
>> +++ b/package/rtl8188eu/Config.in
>> @@ -0,0 +1,18 @@
>> +config BR2_PACKAGE_RTL8188EU
>> + bool "rtl8188eu"
>> + depends on BR2_LINUX_KERNEL && !BR2_ROOTFS_DEVICE_CREATION_DYNAMIC_DEVTMPFS
>
> Even though my understanding of firmware loading is not very deep, I
> believe this is wrong. Since quite some time, the kernel has been able
> to load firmware by itself, without the help of a userspace helper
> program.
Unless I'm wrong, this feature is only available since 3.7
(abb139e75c2: "firmware: teach the kernel to load firmware files
directly from the filesystem").
But your suggestion is applicable for versions 3.7 to 3.11.
So I should drop the dependency on
!BR2_ROOTFS_DEVICE_CREATION_DYNAMIC_DEVTMPFS and clearly point out in
the help text that you must set up some firmware loading mechanism, and
let users discover on their own how they should achieve that.
Overall, the available choices for firmware loading are:
- the kernel-only mechanism (3.7+ only)
- /dev management by mdev ot udev
- static /dev management + BR2_ROOTFS_MDEV_FIRMWARE_LOADING (patch 1
of this series).
Should we add a section to the manual about this? We have a few words
under "/dev management", but they do not encompass the kernel-only
loading.
BTW, my use case here is a 2.6.30 kernel, which has no devtmpfs and no
kernel-only firmware loading. So I must use static /dev management, and
still install mdev as a hotplug helper for firmware loading.
--
Luca
next prev parent reply other threads:[~2015-07-06 13:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-06 13:09 [Buildroot] [PATCH 1/2] system: allow using mdev for firmware loading only Luca Ceresoli
2015-07-06 13:09 ` [Buildroot] [PATCH 2/2] rtl8188eu: new package Luca Ceresoli
2015-07-06 13:17 ` Thomas Petazzoni
2015-07-06 13:59 ` Luca Ceresoli [this message]
2015-07-06 14:36 ` Thomas Petazzoni
2015-07-18 21:30 ` Thomas Petazzoni
2015-07-21 16:26 ` Luca Ceresoli
2015-07-21 20:57 ` Thomas Petazzoni
2015-07-22 10:17 ` Luca Ceresoli
2015-07-22 11:26 ` Thomas Petazzoni
2015-07-06 13:49 ` [Buildroot] [PATCH 1/2] system: allow using mdev for firmware loading only Thomas Petazzoni
2015-07-06 14:08 ` Luca Ceresoli
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=559A89D7.5010400@lucaceresoli.net \
--to=luca@lucaceresoli.net \
--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