From: "Marcin Niestrój" <m.niestroj@grinn-global.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/3] package/murata-wireless-cyw-fmac-fw: new package
Date: Thu, 09 May 2019 09:44:49 +0200 [thread overview]
Message-ID: <87r298xea6.fsf@grinn-global.com> (raw)
In-Reply-To: <77f579fb-40a9-1063-59a8-f35405c29cf7@mind.be>
Hi Arnout,
Arnout Vandecappelle <arnout@mind.be> writes:
> On 07/05/2019 10:32, Marcin Niestroj wrote:
>> +config BR2_PACKAGE_MURATA_WIRELESS_CYW_FMAC_FW_CYW4339
>> + bool "CYW4339 (1CK/ZP)"
>> + help
>> + Murata Wireless FMAC WiFi CYW4339 (1CK/ZP) module
>> + firmware.
>> +
>> +config BR2_PACKAGE_MURATA_WIRELESS_CYW_FMAC_FW_CYW43430
>> + bool "CYW43430/CYW4343W/CYW43364 (1DX/1FX/1LN)"
>> + help
>> + Murata Wireless FMAC WiFi CYW43430/CYW4343W/CYW43364
>> + (1DX/1FX/1LN) module firmware.
>> +
>> +choice
>> + prompt "CYW43430/CYW4343W/CYW43364 module" if BR2_PACKAGE_MURATA_WIRELESS_CYW_FMAC_FW_CYW43430
>> +
>> +config BR2_PACKAGE_MURATA_WIRELESS_CYW_FMAC_FW_CYW43430_1DX
>> + bool "1DX"
>> +
>> +config BR2_PACKAGE_MURATA_WIRELESS_CYW_FMAC_FW_CYW43430_1FX
>> + bool "1FX"
>> +
>> +config BR2_PACKAGE_MURATA_WIRELESS_CYW_FMAC_FW_CYW43430_1LN
>> + bool "1LN"
>> +
>> +endchoice
>
> I don't understand this. Why is it possible to install firmware for CYW4339 and
> CYW43430 1DX at the same time, but not for CYW43430 IDX and CYW43430 1FX?
This is because 'brcmfmac43430-sdio.1DX.clm_blob' is renamed during
installation step into 'brcmfmac43430-sdio.clm_blob' (using
murata-cyw-fw-strip-model helper). The latter is the firmware name
expected by Linux kernel.
>
> In other words, why a choice and not just separate options like for the rest?
>
> So I think what you want is that the
> BR2_PACKAGE_MURATA_WIRELESS_CYW_FMAC_FW_CYW43430 option becomes a blind option
> and moves out of the choice, and that it gets selected by
> BR2_PACKAGE_MURATA_WIRELESS_CYW_FMAC_FW_CYW43430_1DX etc.
It would be nice to do it that way. However different modules based on
the same chip have conflicting names under /lib/firmware/brcm/
directory.
>
>
>> +ifeq ($(BR2_PACKAGE_MURATA_WIRELESS_CYW_FMAC_FW_CYW43340),y)
>> +MURATA_WIRELESS_CYW_FMAC_FW_FILES += brcmfmac43340-sdio.bin
>> +endif
>
> In most of this type of many-simple-options situations, we use something like
>
> MURATA_WIRELESS_CYW_FMAC_FW_FILES_$(BR2_PACKAGE_MURATA_WIRELESS_CYW_FMAC_FW_CYW43340)
> += brcmfmac43340-sdio.bin
Thanks for hint!
>
> By the way, I think the package name is way too long. With Yann's idea to merge
> the three, I think we could name it e.g. murata-cyw-fw.
Okay, will use proposed name.
>
> Regards,
> Arnout
--
Marcin Niestr?j
next prev parent reply other threads:[~2019-05-09 7:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-07 8:32 [Buildroot] [PATCH v2 0/3] murata-wireless firmware packages Marcin Niestroj
2019-05-07 8:32 ` [Buildroot] [PATCH v2 1/3] package/murata-wireless-cyw-fmac-fw: new package Marcin Niestroj
2019-05-07 23:10 ` Arnout Vandecappelle
2019-05-09 7:44 ` Marcin Niestrój [this message]
2019-05-07 8:32 ` [Buildroot] [PATCH v2 2/3] package/murata-wireless-cyw-fmac-nvram: " Marcin Niestroj
2019-05-07 8:32 ` [Buildroot] [PATCH v2 3/3] package/murata-wireless-cyw-bt-patch: " Marcin Niestroj
2019-05-07 15:41 ` [Buildroot] [PATCH v2 0/3] murata-wireless firmware packages Yann E. MORIN
2019-05-07 23:02 ` Arnout Vandecappelle
2019-05-09 7:52 ` Marcin Niestrój
2019-05-09 18:10 ` Yann E. MORIN
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=87r298xea6.fsf@grinn-global.com \
--to=m.niestroj@grinn-global.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